The-Vibe-Company / companion
Web & Mobile UI for Claude Code & Codex . Launch sessions, stream responses, approve tools. All from your browser / mobile
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing The-Vibe-Company/companion in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewThe Companion Web UI for Claude Code and Codex sessions. Run multiple agents, inspect every tool call, and gate risky actions with explicit approvals. Quick start **Requirements:** Bun + Claude Code and/or Codex CLI. Try it instantly Open http://localhost:3456. Install globally Open http://localhost:3456. The server runs in the background and survives reboots. CLI commands | Command | Description | |---|---| | | Start server in foreground (default) | | | Start server in foreground (explicit) | | | Register as a background service (launchd/systemd) | | | Start the background service | | | Stop the background service | | | Restart the background service | | | Remove the background service | | | Show service status | | | Tail service log files | **Options:** overrides the default port (3456). Why this is useful • **Parallel sessions**: work on multiple tasks without juggling terminals. • **Full visibility**: see streaming output, tool calls, and tool results in one timeline. • **Permission control**: approve/deny sensitive operations from the UI. • **Session recovery**: restore work after process/server restarts. • **Dual-engine support**: designed for both Claude Code and Codex-backed flows. Screenshots | Chat + tool timeline | Permission flow | |---|---| | | | Architecture (simple) The bridge uses the CLI websocket path and NDJSON events. Authentication The server auto-generates an auth token on first start, stored at . You can also manage tokens manually: Or set a token via environment variable (takes priority over the file): Development Manual: Checks: Preview / Prerelease Every push to publishes a preview artifact: | Artifact | Tag / dist-tag | Example | |---|---|---| | Docker image (moving) | | | | Docker image (immutable) | | | | npm package | | | Preview builds use a patch-core bump (e.g. when stable is ) so the in-app update checker can detect them as semver-ahead of the current stable release. They are **not** production-stable — use / semver tags for stable releases. Tracking prerelease updates in-app In **Settings > Updates**, switch the update channel to **Prerelease** to receive preview builds. The default channel is **Stable** (semver releases only). Switching channels takes effect immediately on the next update check. Docs • **Full documentation**: (Mintlify — run to preview locally) • Protocol reverse engineering: • Contributor and architecture guide: License MIT