Build with your AI tools,
not around them.

Your coding agents, accounts and projects. One place to move the work forward.

Try free for 3 days For eligible new Monthly, Yearly and Business subscriptions. A card is required; cancel before the trial ends to avoid a charge. Otherwise your selected plan starts at its listed price.

BETALocal workspace

Fix the mobile menuIn progress

Keep keyboard focus inside the mobile menu, then check the fix.

LeadPlan & delegate

Read project context

Message your team…

Agent teamCodex · High

Your agents. One connected workspace.Open full screen

Works with

Claude CodeCodexGoogle AntigravityKimiopencodeCommand CodeCursorClineGrokKiro CLI

01 · Agents & plans

One brief. Visible handoffs.

Build a team around the work. Keep each role, decision and result in view, from the first question to the final review.

checkout / upload-retryIllustrated workflow

01 / 04 Define the outcome

Make failed uploads recoverable.

Keep the existing API. Add a bounded retry, test the failure path and review the interface.

src/upload.ts+tests/upload.test.js

→One project brief, shared by the team.

Lead

Analyst

Developer

Designer

How teams work

02 Chat and terminal

A conversation on one side. The work on the other.

Both run inside the project you already opened — same repository, same engines, same memory. Chat holds the thread and the context; the terminal gives you a real shell. Moving between them costs you no re-explaining.

Download for Windows View plans

An illustrated workflow. Your terminal runs real commands.

chatClaude

Add a retry to the upload. Keep the existing API.

I’ll update the upload client and add retry tests.

Keep the retry limit configurable.

Got it — steering the running turn now.

steered mid-turn

CONTEXT IN · EVIDENCE OUT

terminalproject · PowerShell

$npm test

> node --test upload.test.js

upload.test.js

retry cases passed

$git diff --stat

src/upload.ts · tests/upload.test.js

Talk while it works

Supported chat engines can receive a message during a turn; other engines queue it. Resume supported agent sessions with their context, and inspect handoffs in Summary or Details.

Real shells, not a transcript

Terminal panes are actual PTYs: scroll back, resume, run whatever the shell runs.

Memory travels with you

Enable project memory for chats and supported terminal engines. Resumed agent sessions retain context without repeating the full conversation.

03 Around the agent

What happens before, during and after a run.

The modes are in 01–02. These controls reuse context, track reported usage, apply limits and keep the results.

Before load

Project memory

Pro and up

Review agent notes in Bots → Brain: search, approve, edit or archive them. Project notes and the optional global library share the existing memory store; only approved notes enter context.

Skills

Experimental

Review curated instruction packs with original authors and licenses, import SKILL.md files, and assign skills to team roles. Public ecosystem counts are dated source data, not Firstbeam installs.

Task board

One kanban.json in the repo. A card opens a chat with itself already in the composer, or is pushed into a terminal pane.

Notepad

Notes and freehand sketches beside the code in notes.json. Send to chat and add to terminal move the page into work.

During control

Approval

Choose each agent’s access and whether supported engines can approve tool actions automatically. The planner stays read-only; this switch does not widen its access.

Mid-run messages

In normal chat, supported engines accept steering during a turn; other messages queue. Active plan phases keep their own question and approval flow.

Browser panel

Open local previews and documentation beside the conversation, navigate the panel yourself and save page screenshots into the project on Windows.

Plan mode

Beta

Prepare a phase graph, answer questions and edit each team, model and permission before Run. Independent readers can overlap; shared-folder writers wait.

After keep

Memory writes back

Pro and up

A second switch lets agents write notes themselves. The panel searches the vault, graphs how notes link, and reports an estimated token saving from reuse.

Task status

Follow active conversations, phases and terminals in the workspace. Project chats and agent threads retain their outputs locally. A separate Today activity ledger and autonomous bot supervision are not included.

Plugins

The catalog states what a plugin will be allowed to do — run commands, read project files, write into the project — before it installs.

Where data lives

Project chats, agent threads, plans, team manifests, board and memory are stored under .firstbeam/. Global preferences and provider CLI histories are separate. Choose which project records to commit.

Engines, side by side

Claude CodeCodexGoogle AntigravityKimiopencodeCommand CodeCursorClineGrokKiro CLI

Each engine uses its configured CLI account and session history. Firstbeam’s account and optional dictation key are separate; provider subscriptions and usage are not included in the desktop license.

Before you start

Frequently asked questions

A few things worth knowing about your workspace.Need a hand?

What is Firstbeam?

Firstbeam brings your coding agents, conversations, terminal and project context into one workspace. Use your existing provider accounts, work with one agent or build a team, and review the work before shipping.

Is Firstbeam free?

Creating an account and downloading the installer are free. Workspace access requires a plan. Eligible new Monthly, Yearly and Business subscriptions offer a 3-day trial with a card; cancel before it ends to avoid a charge. AI provider subscriptions and usage are separate.

Which engines can I use?

Codex, Claude Code and OpenCode support structured agent tasks. Other supported coding CLIs run interactively in the terminal. Available models, limits and permissions depend on the provider account you connect.

Which platforms are available?

Desktop and CLI are available for Windows x64. Desktop includes the CLI; you can also install it separately. macOS, Linux and mobile are coming soon.

Where does my project data live?

Project conversations, plans, team records and memory live locally under .firstbeam/. Global preferences and provider histories are separate. AI requests are processed by the provider you choose under that provider’s data policies.

How do I get started?

Download Firstbeam, sign in to your Firstbeam account and connect your coding engines through their CLI sign-in. Open a project folder, choose your engine and start a conversation or agent team.

Start here