Bring your own agents
SharkBay launches supported local agent CLIs in visible terminal tabs. It does not replace your Claude Code, Codex, Gemini, Kiro, Qwen, OpenCode, CodeWhale, or Cursor CLI accounts.
Requirements
SharkBay is a local-first macOS desktop app. It works with repositories that already live on your machine and with the agent CLIs you have installed separately.
The product source lists macOS, Node.js 20.11 or newer, Git, and the GitHub CLI as the main requirements. The GitHub CLI is only needed for team context sync through the Task Protocol.
Local projects stay local
Projects are exact directories selected by the user. SharkBay reads local state and only syncs data when a feature explicitly requires it.
Add your first project
Open SharkBay and add the repository directory you want to work in. The project appears in the workspace sidebar with repository status, dirty state, terminal activity, and running service hints.
Selecting the project keeps terminals, browser tabs, task records, Git details, and file browsing attached to the same workspace context.
SharkBay only removes the workspace entry when you remove a project from the app. It does not delete the repository directory.
Launch agent sessions
Use the terminal workspace to start supported coding agents inside the selected project. SharkBay keeps the session visible as a terminal tab and surfaces status so you can see whether an agent is working, waiting for approval, stopped, or idle.
Because sessions stay attached to the project, you can move between repositories without losing the terminal context for each one.
If Task Protocol is installed for the project, supported agent launches include a first-message bootstrap that tells the agent to read .sharkbay/harness/protocol.md before project-changing work.
Verify and hand off work
For web-facing work, open embedded browser tabs beside the terminal. For project state, inspect the Git tab and changed files. For shared agent context, install Task Protocol so work summaries and verification notes live in repo-local Markdown records.
When an artifact is ready to review outside the machine, SharkBay can publish a snapshot share link without exposing the whole repository.
Before handing work off, check the relevant terminal output, browser preview, Git dirty files, and task record verification notes.
FAQ
Is SharkBay a cloud coding workspace?
No. SharkBay is a local-first macOS desktop workbench. It operates on user-configured local projects and launches local tools in visible terminal tabs.
Do I need to change my agent instruction files?
No. SharkBay works alongside files such as AGENTS.md and CLAUDE.md. Task Protocol adds its own .sharkbay harness when installed, but it does not replace existing project instructions.
Which coding agents can SharkBay launch?
The current product supports Claude Code, Codex, Gemini, Kiro, CodeWhale, Qwen, OpenCode, and Cursor CLI as local agent CLIs.