Troubleshooting

Common situations and how to resolve them.

The CLI says it cannot reach chronosd

The chronos command is a thin client of the daemon. If it reports that it cannot reach chronosd, the daemon isn’t running — start it with chronosd and try again.

The agent doesn’t seem to do anything

The most common cause is that your coding agent isn’t signed in. Make sure you’ve signed in to the agent your organization uses (your administrator can help). Then try the session again.

The agent made a plan but didn’t change anything

You’re likely in plan mode — that’s by design: plan mode proposes an approach without making changes. Send a normal instruction (or turn Plan off) to have the agent carry it out. See Prompting and plan mode.

A command says “approval required”

The command is something sensitive (like deleting a lot of data or installing software). Someone with the right permission needs to approve it before it runs. This is intentional — Chronos won’t run high-impact actions silently. From the command line, re-run with --approve once you have that permission.

I can’t merge

A merge needs all of: your checks green, the required approvals in place, and merge permission. Chronos shows you exactly which of these is missing. Run your checks, get the approval, and confirm you have permission to merge. See Pull requests, approvals and merge.

A tool or capability I need isn’t available

Available tools, agents and capabilities are managed centrally by your organization. If something you need isn’t there, request it from your Chronos administrator — it can’t be added locally by design.

My session disappeared

It shouldn’t — sessions are saved and survive restarts. Make sure you’ve connected the same repository (the workspace it belongs to). If it’s still missing, contact your administrator.

Something else

If you hit a problem this guide doesn’t cover, contact your Chronos administrator or support contact. They can see the central activity record and help diagnose what happened.