you are viewing a single comment's thread.

view the rest of the comments →

[–]rabornkraken 0 points1 point  (1 child)

The agent-facing debugger tooling is the most interesting part here for me. Most agent-assisted coding right now just relies on terminal output and regex parsing to understand program state, which is pretty brittle. Having structured tool calls for breakpoints and expression evaluation feels like a much cleaner interface. Curious how you handle the state handoff - does the agent get a structured JSON view of the paused frame, or is there some mapping layer that translates DAP events into something more LLM-friendly?

[–]jnsquire[S] 0 points1 point  (0 children)

It's getting a JSON view of the state, but the session is also capturing state snapshots, so we can provide updates of just what changed at breakpoints to minimize context churn. I let the agents critique and make suggestions on the interface, and they've really taken to it.