Visible sessions
Agent sessions are shown as terminal tabs rather than invisible background jobs.
Why a multi-agent launcher exists
Developers increasingly use more than one coding agent: one terminal for Codex, another for Claude Code, another for Gemini, and a browser window for the app being changed. SharkBay turns that scattered workflow into a project-centered desktop workbench.
The launcher keeps agent sessions visible inside the selected local repository. You can see which project each session belongs to, switch between projects, and keep the surrounding Git, browser, service, and task context nearby.
Supported agent CLIs
SharkBay supports the agent CLIs developers already run locally: Claude Code, Codex, Gemini, Kiro, CodeWhale, Qwen, OpenCode, and Cursor CLI.
The app does not hide those tools behind a remote service. Agent sessions run in visible terminal tabs, so the user can inspect output, approvals, shell context, and failures directly.
Project-scoped context
Sessions launch from the selected repository, keeping cwd, instructions, dev services, and Git state aligned.
Status and recovery
SharkBay surfaces hook-based agent status such as working, idle, attention, approval, and stopped states. That status appears in the project workspace so you can see progress without switching through terminal windows.
For long-running work, session entries help identify and restore the right thread later instead of starting from a blank terminal.
More than an agent menu
The multi-agent launcher sits inside a broader macOS workbench: project list, terminal tabs, embedded browser tabs, dev service launchers, Git awareness, files, quick editing, artifacts, sharing, and Task Protocol records.
That context matters because agent work is only useful when it can be verified, reviewed, handed off, and connected back to the project.
FAQ
Can SharkBay run multiple coding agents at once?
Yes. SharkBay is designed to launch and manage multiple supported agent CLIs from one local project workspace.
Does SharkBay replace the agent CLI?
No. SharkBay launches supported local CLIs and keeps them visible in terminal tabs. The underlying agent tools and accounts remain the user's own.
Why use SharkBay instead of separate terminal windows?
SharkBay keeps projects, agent sessions, browser previews, dev services, Git state, files, and task records in one workspace so the surrounding context stays visible.