Repository navigation
Troubleshooting and Recovery
Applies to: Agent PBX 2.2.x Last reviewed: 2026-10-10
Start with read-only posture and preserve runtime evidence:
agent-pbx mcp status
agent-pbx doctor
agent-pbx migrate verifyDo not restart or move a healthy pane merely because the embedded surface is blank. Check the entity's mapping, tmux server/socket, process evidence, Codex session, and writer lease first.
Attach directly to the recorded local runtime:
agent-pbx runtime attach --entity codex-agent-pbxUse --read-only for diagnosis. Detaching this client leaves the managed
runtime running. On another host, generate an SSH attachment with
agent-pbx remote ssh-attach.
Check:
- native tmux and embedded-terminal settings are enabled;
- the selected entity has a verified v2 mapping;
- its recorded tmux binary and socket are available;
- no stale client owns the writer lease;
- the current right tab is Latest;
- terminal engine diagnostics do not report an unsupported sequence.
Disabling native mode must detach the embedded PTY, clear selected terminal state, and release the lease. If that evidence is stale, repair through a previewed lifecycle action rather than deleting the mapping manually.
The recorded runtime tmux executable must be used for resize and copy-mode
operations. Page Up should enter history; /tmux scrollback is the explicit
fallback. Confirm the managed Codex terminal profile uses tmux-owned scrollback
and that a read-only observer is not controlling authoritative size.
Run /pbx keymap and use the interactive key probe. Plain F keys belong to PBX;
Shift+F keys belong to Codex. Ctrl+P opens the PBX palette. Printable Agent and
Operator shortcuts are disabled while a writable embedded terminal owns focus,
preventing typed characters from triggering lifecycle actions.
Encrypted content must appear locked. Check the dedicated profile, Data API, profile-owner mode, sync job, and E2EE status. Unlock/decrypt with a supported Joplin client; do not paste a master password into Agent PBX configuration or a note. A verified plaintext target can remain successful while unrelated locked items are reported separately.
Compare the PBX host cwd, WorkerBee-visible path, repository root, backend provenance, and mount translation. Distinguish path mismatch from an omitted tool allowlist or an unavailable/older endpoint.
Rollback requires a reviewed backup and a stopped managed daemon:
agent-pbx mcp stop
agent-pbx migrate rollback \
--backup /path/to/reviewed-backup \
--confirm RESTORE
agent-pbx mcp start
agent-pbx doctorAdd --restore-config only when the matching configuration must also be
restored. Rollback creates a safety backup first and does not delete later
project work, transcripts, Joplin notes, or trash entries.
- Agent PBX Home
- Getting Started
- Concepts and Architecture
- TUI and Keymap
- Agents Operators and Runtimes
- Runtime and Tmux Operations
- Models Profiles and Codex
- WorkerBee Integration
- Joplin Notes
- Security and Remote Access
- Troubleshooting and Recovery
- Packaging Releases and Upgrades
- Interactive Browser Demo