I have seen this happen two times in the last week with agy 1.1.7 (the console client).
Agy proposes a diff
I add some comments to it
press “y” to send comments to bot.
then agy proposes to implement the exact same diff without responding to the comments.
I ask agy to address the comments, then it spends 10-15 turns searching through the codebase and conversation history to find the comments, with no avail.
I have to restart the comments before it will action them.
Hi @wtfrank, Welcome to the Forum!
I tried to reproduce it but wasn’t able to so far. Could you please provide a bit more information?
Which operating system are you using (macOS, Linux, or Windows)?
Could you share the exact prompts you used to generate the diff and the review comments?
If possible, could you provide a screen recording showing the complete workflow from generating the diff to the comments being lost?
Were there any error messages or logs when AGY failed to find the comments?
Linux, agy console.
wall of text coming up:
viewing full proposed diff, adding a comment at line 192:
```
189 + ### GET /api/game/{game_id}/replay/100
190 +
191 + Returns tick snapshot data for a game. The 100 parameter is a page/offset
192 + value;
/replay/100returns the objects present around tick 1.
// this also contains ticks 2-100. we don’t have the exact tick 0 object state however tick 1 is the closest we can get.
193 +
194 + Response: A raw JSON array (not an{ok:1}wrapper):
195 +json 196 + [ 197 + { 198 + "gameTime": 1, 199 + "objects": [ 200 + { 201 + "_id": 121, 202 + "type": "spawn", 203 + "prototypeName": "StructureSpawn", 204 + "x": 49, "y": 4, 205 + "hits": 3000, "hitsMax": 3000, 206 + "store": { "energy": 1 }, 207 + "storeCapacityResource": { "energy": 1000 }, 208 + "user": "player1", 209 + "origin": true, 210 + "actionLog": {}, 211 + "spawning": { "id": 335, "needTime": 48, "spawnTime": 49 } 212 + } 213 + ] 214 + } 215 + ] 216 +
… 45 more lines (↓ to scroll)
↑/↓ scroll · n/N next/prev diff · pgup/pgdn page · ←/→/j/k cycle file · c comment · d delete comment · esc back
```
sending the comment as i leave the diff view
`Unsent Comments
You have unsent comments. Ready to send?
screeps_arena_protocol/README.md
L192: this also contains ticks 2-100. we don’t have the exact tick 0 object state however tick 1 is the closest we can get.
y send and exit · n exit without sending · esc cancel
esc to cancel Claude Sonnet 4.6 (Thinking)``
```
after sending comment goes back to diff:
29 + Returns all seasons (historical and current).
30 +
… 231 more lines (f for full diff)
Allow creation of this file?
> 1. Yes, allow creation
2. No, deny creation
↑/↓ Navigate · tab Amend · f full diff · ctrl+r Review
esc to cancel
press f to view full diff and go to the commented line
` 189 + ### `GET /api/game/{game_id}/replay/100`
190 +
191 + Returns tick snapshot data for a game. The `100` parameter is a page/offset
192 + value; `/replay/100` returns the objects present around tick 1.
193 +
194 + **Response:** A raw JSON array (not an `{ok:1}` wrapper):
195 + ```json
196 + [
197 + {
198 + "gameTime": 1,
199 + "objects": [
200 + {
201 + "_id": 121,
202 + "type": "spawn",
203 + "prototypeName": "StructureSpawn",
204 + "x": 49, "y": 4,
205 + "hits": 3000, "hitsMax": 3000,
206 + "store": { "energy": 1 },
… 55 more lines (↓ to scroll)
↑/↓ scroll · n/N next/prev diff · pgup/pgdn page · ←/→/j/k cycle file · c comment · d delete comment · esc back
esc to cancel
refuse the proposed change
189 + ### `GET /api/game/{game_id}/replay/100`
190 +
191 + Returns tick snapshot data for a game. The `100` parameter is a page/offset
> 192 + value; `/replay/100` returns the objects present around tick 1.
// this also contains ticks 2-100. we don't have the exact tick 0 object state however tick 1 is the closest we can get.
193 +
194 + **Response:** A raw JSON array (not an `{ok:1}` wrapper):
195 + ```json
196 + [
197 + {
198 + "gameTime": 1,
199 + "objects": [
200 + {
201 + "_id": 121,
202 + "type": "spawn",
203 + "prototypeName": "StructureSpawn",
204 + "x": 49, "y": 4,
205 + "hits": 3000, "hitsMax": 3000,
206 + "store": { "energy": 1 },
207 + "storeCapacityResource": { "energy": 1000 },
208 + "user": "player1",
209 + "origin": true,
210 + "actionLog": {},
211 + "spawning": { "id": 335, "needTime": 48, "spawnTime": 49 }
212 + }
213 + ]
214 + }
215 + ]
216 + ```
… 45 more lines (↓ to scroll)
↑/↓ scroll · n/N next/prev diff · pgup/pgdn page · ←/→/j/k cycle file · c comment · d delete comment · esc back
agy having no clue about the comment and trying to guess what I might have put in the comment that it’s lost track off. at this point you can go on for many turns and it will not be able to recover the comment or act on it, unless you tell it what the comment was.
Create file
⎿ User declined the tool call
────────────────────────────────────────────────────────────
> you have not update the diff based on the comment I fed back about tick range.
▾ Thought for 15s
The user is referring to a comment about the tick range for the `/api/game/{game_id}/replay/100` endpoint. Looking at what I wrote, I described `100` as a "page/offset value"
and said `/replay/100` "returns the objects present around tick 1".
But I think the user's feedback (which I may have missed or not incorporated) was that `100` is actually a tick range or something else. Let me think about this more carefully.
Looking at the ticks.json file, the first entry has `"gameTime": 1`. The endpoint is `/replay/100`. So what does the `100` represent?
Actually, looking at the data more carefully - the response contains tick data. The `100` in the URL is likely the number of ticks to return or an end tick.
The user mentioned I didn't update the diff based on their feedback about the tick range, which suggests they already explained how this parameter works. I'm realizing I may
have misunderstood what `/replay/100` actually does—it's probably not about pagination or offsets at all, but rather specifying a tick range or limit. The `100` parameter could
mean the starting tick, the number of ticks to return, or something else entirely—but the sample data showing `gameTime: 1` doesn't clearly align with any of these
interpretations. I should ask the user to clarify what the correct description should be, since I'm missing the specific feedback they mentioned earlier.
I don't have that feedback in my current context — it was in the portion of the conversation that was truncated. Could you re-state what the correct description of the 100
parameter (or tick range behaviour) for /api/game/{game_id}/replay/100 is? I'll incorporate it into the README before writing it.
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
>
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
? for shortcuts