Debugging the agent
Troubleshooting a stuck or misbehaving agent: read the timeline, interrupt and retry, check logs.
When the agent is stuck, misbehaving, or you just want to see what it's doing, use these techniques.
See what it's doing
- Live timeline — the conversation stream (center panel on desktop, inline in the CLI) shows the agent's thinking, each tool call, and its result as they happen.
- Expand tool cards — click into any tool call to see what it executed and what came back.
When the agent is stuck
- Add a note — type a message and press Enter while it runs; it is queued and sent when the current turn ends (in the CLI, ↑ pulls back the last queued message).
- Interrupt — press
Escto stop the current turn, then restate what you want. - Switch model / lower thinking — try a faster combination with
/modeland/thinking.
Logs
Logs live under ~/.neox/logs/, one file per day (the CLI writes cli-<date>.log). Attach them when reporting an issue.
Set NEOX_DEBUG=1 before starting the CLI for more verbose debug output.
Reporting issues
Submit it on the feedback page or email support@neox-dev.com. Including the log from ~/.neox/logs/ covering the relevant time makes diagnosis much faster.

