Skip to content
Roy Padina edited this page Oct 23, 2026 · 7 revisions

FAQ & Troubleshooting

How is this different from tmux / claude --resume?

claude --resume resumes by id from memory — you still have to know which session and which folder. Agentctl finds the right one: fuzzy-search every past session by name/path/transcript text, preview the conversation, then resume it in its original cwd. The New side adds a frecency-sorted, fuzzy launcher across all your projects. tmux organizes windows; this organizes agent sessions.

Is it safe? Does it phone home?

  • Open source (MIT) — read or build every line.
  • Local-only. It reads ~/.claude/ and your configured project folders and launches your terminal. No network calls of its own, no analytics, no accounts.
  • Permissions: Claude runs in auto permission mode by default (--permission-mode auto). Opt into bypass with permission_mode = "bypassPermissions" in your config.

A session shows a ⚠ — what does it mean?

The working directory couldn't be decoded with certainty (a - in a folder name is ambiguous — see Architecture → cwd decoding). Resuming into the wrong directory is bad, so it asks first: press ↵ twice to resume anyway, or run agentctl resume <id> --cwd /the/right/path.

Where did cdx go? How do I launch Codex?

There's no standalone cdx command anymore — Codex is a tool inside the menu. Run agentctl and press ⇧⇥ to cycle the tool to Codex, then ↵. Want a dedicated command? Add your own alias, e.g. alias cdx='agentctl'.

Why did my old commands disappear?

v0.2.0 replaced the three separate commands with a single agentctl. brew upgrade --cask agentctl removes the old links. See the CHANGELOG.

Does it work on Linux / Windows?

Linux is best-effort: the same Node code runs there (clipboard via wl-copy/xclip/xsel, ^f uses xdg-open) and CI runs the tests on Ubuntu, but it is tested daily only on macOS. Windows is not supported (kill -0/ps status and the ~/.claude layout assume POSIX). Issues welcome at https://github.com/roypadina/agentctl/issues.