RunHuddleWhat you need
RunHuddle currently has built-in integrations for three agents: Codex CLI, Claude Code, and GitHub Copilot CLI.
Other CLIs can run as commands in standalone shell terminals. Launching a CLI is only one part of an integration: session discovery, live status, resume behavior, and supported checklist or handoff features need provider-specific support. Running another CLI does not automatically make it a tracked RunHuddle agent.
Install and authenticate each CLI you want to use. RunHuddle connects to Codex CLI, Claude Code and GitHub Copilot CLI; it does not provide their accounts, model access or permissions.
Open Settings → Connections to inspect discovery and tracking status. Tracking and launching are different: a visible history does not guarantee a live connection. Integration behavior depends on your installed CLI version and account policy.
Codex
RunHuddle uses the compatible local shared app server for status, history and session operations. The default control socket is:
~/.codex/app-server-control/app-server-control.sock
The bridge honors CODEX_HOME when it is available in the app’s environment. Apps launched from Finder may not inherit shell variables.
If the connection is missing, check the installed CLI and shared daemon:
codex app-server daemon version
codex app-server daemon start
These commands depend on your CLI version. A passive status connection does not start or resume conversations. Use New session or Resume this session explicitly for that.
Claude Code
Supported versions expose existing sessions through Claude’s live session list. Older versions may need Connections → Connection details → Enable Claude compatibility hooks.
Compatibility setup merges RunHuddle’s observational hooks into ~/.claude/settings.json or the configured Claude directory, preserving unrelated settings and saving a backup. Fully exit and relaunch an existing Claude process after a hook-path change; /resume inside the same process can retain old hooks.
History comes from local transcripts. Live status requires supporting session, hook or process evidence. RunHuddle does not infer a Claude context percentage from transcript length or guess shared/team checklist stores from project names.
GitHub Copilot CLI
Tracking is configured after Copilot is detected. Check Connections for errors or a retry action. Hooks live under ~/.copilot/hooks/agent-session-manager.json, or the configured Copilot home, and point to RunHuddle’s bundled collector.
Restart or resume already-open Copilot sessions after initial hook setup. New sessions can report activity automatically. Hooks observe events; they do not grant permission or inject prompts. RunHuddle preserves unrelated hook files and backs up its own configuration when repairing an old app path.
Use the embedded terminal for work and approvals. Older instructions about reply extensions, experimental reply flags and development channels do not apply to this workspace.
Existing external sessions
External conversations may be discovered and searched, but remain read-only in RunHuddle while running elsewhere. Exit the original agent, wait for its status to reconcile and then resume it here. Do not launch another copy of the same conversation while its original process is still active.
Refresh and compatibility
Agent events update the affected provider. A fallback check about every 30 seconds reconciles missed events and process exits; use View → Refresh session data for a manual check. Brief transitions can be missed.
Unknown or unsupported formats can limit discovery, context estimates or checklists. Account restrictions must be resolved with the provider or administrator. RunHuddle does not bypass them. See Troubleshooting before reconnecting repeatedly.