Skip to content
Esc
navigateopen⌘Jpreview
On this page

Agent Integrations

Connect Claude Code and Codex to PonyMux for live status, session history, usage indicators, and notifications when an agent needs you.

PonyMux works as a normal terminal without an integration. Connecting Claude Code and Codex adds the agent-aware parts of the product while leaving each agent’s own terminal interface intact.

AGENT INTEGRATIONS
Claude Code2 active · last event just now
Codex1 active · last event just now
Agent Integrations Integrations observe supported local agent sessions; they do not replace the agents' terminal interfaces.

What an integration enables

For agent sessions started in a regular PonyMux Terminal, integrations provide:

  • Live agent states such as Running, Waiting for you, and Standing by.
  • Session history in the Sessions panel.
  • Resume and Fork actions when the agent transcript supports them.
  • Notifications for completed turns, permission requests, input requests, and errors.
  • Provider usage windows and reset times when that information is available.

Connect a provider

Install the provider

Install Claude Code or Codex first. If PonyMux cannot find a provider’s configuration directory, the integration panel offers a link to its setup page.

Open Agent Integrations

Select the link button at the bottom of the PonyMux sidebar. The panel shows a separate card for Claude Code and Codex.

Connect

Select Connect for each provider. PonyMux asks for confirmation before it adds its hook entries to the provider configuration.

Start a new agent session

Run the provider normally in a regular PonyMux Terminal. Its status and session history begin updating after the hooks report activity.

PonyMux writes its Claude Code hooks to ~/.claude/settings.json and its Codex hooks to ~/.codex/hooks.json. It checks its owned entries again on launch and adds missing supported events without requiring a manual reinstall.

Connection states

  • Connected means PonyMux’s hooks are installed and enabled.
  • Reconnect means older forwarding entries are present but the current integration is incomplete.
  • Hooks disabled in config means the provider configuration explicitly disables hooks.
  • Not set up means the provider configuration directory is not available yet.

Use Settings → Integrations for detailed management or to disconnect a provider. Disconnecting removes PonyMux’s owned hook entries; it does not uninstall Claude Code or Codex.

Quick Terminal exception

Agent integrations intentionally do not track sessions started inside a Quick Terminal. Quick Terminals are temporary and do not receive a PonyMux Terminal identity, so they cannot create session history or agent status on the host Terminal.

Last updated on Sep 12, 2026