The shared AI workspace for teams.

See everyone’s AI threads. Plan together. Share the context.

Project brief
MMaya added context

One issue tracker.
One hackathon.

React + Supabase.
One shared API contract.

Shared API contractIssue: title, priority, status
Shared architectureShared chat
AAlex

Define the issue API, then split frontend, backend, and tests into parallel tasks.

BRANCH Example answer

One contract. Three workstreams.

Use the same Issue type across the React UI, Supabase API, and tests. Each branch keeps this context.

MMaya

I’ll take the backend. Keep the field names aligned.

Project brief ·Shared API contract

Keep thinking together…↑

Frontend · React
SSam · frontend

Build the issue list.

const { data: issues } = useIssues();
return <IssueList issues={issues} />;
Shared brief + API contract
MMaya · backend

Add the Supabase query.

const { data: issues } = await supabase
  .from("issues")
  .select("title, priority, status");
Same contract. Parallel work.
AAlex · testing

Check the contract.

expect(issue.status)
  .toBe("open");
Same context. Separate conversation.

Maya adds the project brief and shared API contract.

Illustrative example

See what everyone is working on.See everyone’s work.

Keep your team’s AI threads visible on one canvas. Follow the decisions, see the work in progress, and pick up where a teammate left off.

Everyone in their own ChatGPT chatSeparate chats

Maya’s chatHere’s our brief…Alex’s chatHere’s our brief…Sam’s chatHere’s our brief…MayaBriefAlexBriefSamBrief

Repeat the brief, copy the answer, and catch everyone up whenever the project changes.

Your team, on Branch

Shared project briefMaya’s threadBackendAlex’s threadTestingSam’s threadFrontendShared briefMayaBackendAlexTestingSamFrontend

See each person’s thread alongside the shared brief. Work in parallel while keeping the team’s decisions in view.

Plan together.
Build from shared context.One plan.
Shared context.

Put the brief, decisions, and next steps beside the work. Connect the sources each chat needs, then explore different parts of the project in parallel.

A shared idea becomes three focused conversationsPulse branches into React frontend, Supabase backend, and contract tests. Each branch keeps the shared API contract.Pulse · shared API contractSAM / FRONTENDBuild the React UIMAYA / BACKENDWrite the Supabase APIALEX / TESTINGTest the contract

Sam builds the React interface with the shared brief and API contract already in context.

Your team brings the thinking.
Branch keeps it connected.Built for shared thinking.

Everyone’s threads, in view

Ask the next question in the same chat, see who is working where, and build on your teammates’ thinking.

A shared plan and context

Keep goals and decisions in shared notes. Connect files, links, and references to the conversations that need them.

Branching

Explore an answer or excerpt in a separate conversation, carrying the relevant background with you.

Research

Give an agent a question, then explore its cited findings and connected sources on the board.

Team workspaces

Organize personal and team boards so each project has a place for its sources, conversations, and next steps.

Access controls

Invite editors or viewers, or share a revocable link with named guests. Owners decide who can join.

A few answers.

Can several people work in the same chat?

Yes. Teammates share the conversation and draft, and responses sync to the board. People can work in different chats at once. If someone else is editing a chat, Send waits so their changes are not missed.

What carries over when I branch?

The conversation up to that point and its connected context. Other branches stay separate until you connect them. Attached source snapshots stay fixed until you choose to refresh them.

What can I add?

Notes, PDFs, images, website links, and public YouTube captions. Websites are looked up when you send; private or blocked pages may be unavailable.

Who can access my board?

Owners manage editors, viewers, and revocable guest links. Team members can edit their team’s boards. You can also keep a board in your personal workspace and invite collaborators when you’re ready.