Repository navigation
Commit ee326eb
committed
Let the interface's memory flag follow the kernel, not the wish
MEMORY_WIRED becomes true because it now is: AgentOptions.history landed
in de6889a, the session's turns are passed to runAgent, and the decision
frames carry a bounded `earlier`. The note the interface shows while the
agent cannot remember therefore disappears on its own.
The flag stays a value rather than a comment. It is the one place this
server states a capability, and the point of stating it in data is that it
has to move when the capability moves -- including backwards, if the
kernel ever stops accepting history.
`history` is read from the session before runAgent, not after. The turn
being run is appended on run:end, so reading first is what keeps a run
from being handed its own answer as context.
Verification (commands actually run):
npx tsc --noEmit -> 0 errors
GET /api/session -> memory=true
two turns in one session, the second asking "what arguments does that
function take?" -> the answer cites the first turn's list_dir output,
which it could only know from the history1 parent 1316b05 commit ee326eb
1 file changed
Lines changed: 11 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
100 | 100 | | |
101 | 101 | | |
102 | 102 | | |
103 | | - | |
104 | | - | |
| 103 | + | |
105 | 104 | | |
106 | | - | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
107 | 110 | | |
108 | | - | |
| 111 | + | |
109 | 112 | | |
110 | 113 | | |
111 | 114 | | |
| |||
286 | 289 | | |
287 | 290 | | |
288 | 291 | | |
289 | | - | |
290 | | - | |
| 292 | + | |
| 293 | + | |
| 294 | + | |
291 | 295 | | |
292 | 296 | | |
293 | 297 | | |
| 298 | + | |
294 | 299 | | |
295 | 300 | | |
296 | 301 | | |
| |||
0 commit comments