When an Agent Looks Stuck: Diagnose Before Killing
When an Agent Looks Stuck: Diagnose Before Killing. Status says working but nothing moves: stdout buffering, waiting-on-input states, and safe interrupt patterns. Claims map to Ferryx docs and cited sources only.
False-busy signals
Terminal tooling fails in confusing ways because several layers (OS, WebView, PTY, daemon, renderer) can each produce similar symptoms. A structured triage path saves you from restarting blindly and killing sessions that were fine. In the specific case of “When an Agent Looks Stuck: Diagnose Before Killing”, the Ferryx angle is straightforward: status says working but nothing moves: stdout buffering, waiting-on-input states, and safe interrupt patterns. claims map to ferryx docs and cited sources only. Teams evaluating this often arrive from a shared-checkout pain story or from tooling that treats the terminal as a disposable window. Ferryx takes the opposite stance—sessions are daemon-owned, isolation is a first-class action, and everything you need to verify sits behind documented surfaces.
Waiting for input
Most Ferryx issues cluster into install/platform quirks, IME and rendering oddities, daemon socket permissions, and overlay states like Shell exited. The product facts page and architecture doc are the first places to confirm expected behavior before changing anything. Applied to “agent stuck diagnose terminal”, that context matters because the failure modes people search for are almost always failures of ownership or visibility rather than of raw rendering. When the process outlives the window, when the buffer can prove what it missed, and when each agent’s files live in a jailed worktree, the same task that used to require three clones and a spreadsheet becomes a pane layout you can read at a glance.
Practical steps
- Reproduce once and note the exact surface: desktop GUI, remote client, one platform, all platforms.
- Confirm expected behavior against docs/facts and the architecture page before assuming a bug.
- Check the cheapest layer first: permissions, socket paths, package choice, display scaling.
- Capture evidence (error text, overlay copy, screenshot) before restarting the daemon.
- If a session must be recovered, respawn the pane rather than killing the daemon that owns other live PTYs.
| Checkpoint | What good looks like |
|---|---|
| Isolation | Each parallel actor has its own worktree or a documented reason not to |
| Visibility | Status badges or attention counters answer “who needs me?” without polling |
| Persistence | Closing the window does not end agent processes |
| Evidence | Claims map to product facts or a linked source |
How this fits Ferryx today
Ferryx ships calendar-versioned releases for macOS (universal DMG), Windows (x64 installer), and Linux (AppImage and .deb). The desktop shell, daemon, and optional ferryx-cli headless binary are described with sources on the product facts page. If you are new to the workspace model, start with the introduction; if you want the mechanical details of sessions and replay, read technical architecture.
Related reading:
FAQ
Should I restart the daemon first?
Usually not. Daemon-owned sessions are precious; inspect logs and pane state before killing processes other work depends on.
Where do I report a bug?
GitHub issues on Indosaram/ferryx with platform, release version, and reproduction steps get the fastest useful replies.
Why does documentation differ from what I see?
Ferryx ships calendar-versioned releases quickly; check that your version matches the facts page date before digging deeper.
Limits and non-goals
Ferryx is early software: core flows work, but expect rough edges and breaking changes between calendar-versioned releases. Some OS integrations remain platform-specific (Dock badge counters and launchd supervision are macOS-only today), Windows builds are not code-signed yet so SmartScreen warns on first run, and remote features assume you control the host and pairing grants. None of that changes the core claim of this post—daemon-owned sessions, managed worktrees, and visible multi-agent workflows—but it is the honest boundary of what has shipped. Verify anything version-sensitive against the facts page and the release notes before you standardise a team workflow on it. If something in this guide disagrees with your build, trust the repository sources linked from product facts and open an issue with your version string attached.
How to verify these claims
Every concrete statement in this post ties back to a checkable surface: package names and license terms live on product facts, session and buffer behaviour is described in technical architecture, and keyboard bindings are listed under shortcuts. Where a third-party tool is mentioned, treat vendor docs as authoritative for that tool and re-check dates before quoting them in a decision document. That discipline is why this site does not publish performance benchmarks it has not measured: reproducible architecture facts age better than marketing numbers.
Checklist before you ship this habit
Confirm three things after a week of running this loop: isolation is still one worktree (or documented shared-checkout) per actor, attention reaches you through status badges rather than manual pane polling, and every external claim in your notes maps to a dated source you would still trust next quarter. If any check fails, fix that layer before adding more agents to the workflow; parallelism amplifies both good structure and debt.