Allbase

ALLBASE FOR TEAMS · PRIVATE BETA

Allbase your project.
Bring your team’s agents into the work.

Give the work a home: decisions, source material, and next steps your teammates can share with their own agents. Choose the people, the knowledge, and the access. Keep using the tools you prefer.

  • Shared folders for teams
  • Named, revocable agents
  • Project invitations and roles
  • Private personal workspace
  • Governed access

THE PROBLEM

Shared chat is not shared context.

Work gets fragmented across teammates, models, chats, and coding agents. Decisions go stale, parallel agents duplicate effort, and every handoff starts with another explanation.

Put a decision in the project’s shared notes once. An authorized teammate or agent can retrieve the current source when they need it.

HOW TEAMS WORK TODAY

One project. Many people, agents, and workstreams.

Start with one project folder and explicit roles in the private beta today.

  1. 01

    Create the project

    Give it a name, a purpose, and its own folder. Invite teammates by @handle or email as viewers, contributors, or managers. You don't need to be contacts first.

  2. 02

    Choose the shared knowledge

    Work in the project's folder, or attach other folders and notes you own. Before anything is attached, you see which members will gain access.

  3. 03

    Accept once

    One acceptance brings a teammate the project's folders, task board, and checkpoint history, at their role, for them and their authorized agents.

  4. 04

    Put the next step in reach

    Keep the current decision in the project's notes and open work on its task board. Ask an authorized agent to retrieve it and cite the source before continuing.

BUILT FOR MULTIPLAYER AI

Coordinate the work, not the conversation.

A project's Activity in Allbase: the latest checkpoint from the codex and claude-code agents, with blockers and next actions, above the project's task board

Projects and history

Keep decisions, progress, and next steps in one place

Each project page shows its Activity, Knowledge, and People. Open the checkpoint history to see what each member’s agents recorded, when, and what comes next.

Handoffs

Move work between your agents

Each agent saves progress in its own lane and can read the other agents’ checkpoints. Accepted project members and their authorized agents can pick up the work across workspaces.

Tasks and asks

Make ownership visible

Each project has a task board where members and their agents add tasks, questions, and suggestions, then claim, answer, or finish them. Anything that needs a person lands in their Home inbox. Agents still need instructions to use these tools.

Private workspace

Share the project without sharing everything

Joining a project grants access to its folders, task board, and full checkpoint history. Unrelated personal notes, memories, and tasks remain private. A note you share with one person stays a separate grant.

AVAILABLE TODAY · DIRECTION AHEAD

From shared knowledge to shared continuity.

“Allbase a project” is the experience we are building toward: the right people and agents can pick up the work with its context intact.

Shipped

Projects as shared folders

Create a project with its own folder, invite people by @handle or email, set viewer, contributor, or manager roles, and attach the folders and notes that support the work.

Shipped

Ownership and organization controls

Offer and accept ownership transfers for projects, teams, and shares. Organization admins have member offboarding controls, including access revocation and reassignment, with confirmation for destructive steps.

Shipped

Continuity across people’s workspaces

Accepted project members and their authorized agents can read the full checkpoint history. Agents with write access save progress in their own lanes, preserving each other's work and attribution. Each project also has a task board and a page for its activity, knowledge, and people.

WAYS TO COLLABORATE

A common context layer for real team workflows.

Product + engineering

Carry decisions from roadmap to release

Record the rationale and implementation state in shared notes for authorized coding and review agents to retrieve.

Research + strategy

Build on findings across the team

Parallel researchers contribute cited conclusions while later agents retrieve the current synthesis note, not every raw thread.

Operations

Coordinate recurring work and handoffs

Keep a current handoff note in the team’s shared folder so the next person and their agent can see owners, blockers, and next actions.

GOVERNED BY DESIGN

Clear access. Clear ownership. Clear history.

Collaboration stays useful only when every person and agent sees exactly what they are allowed to see—and every important change remains attributable.

Explicit shares

You see who gains access before you share, and recipients choose whether to accept. The Share sheet lists who can see each note or folder. Revocation blocks future requests through that grant; it cannot recall copies already downloaded or sent to an AI client.

Named agents

Each agent has its own identity, grant, activity trail, and revocation boundary. Revoking one agent never touches another.

Attributed decisions

Checkpoints identify the agent, runtime, and time behind recorded decisions. They are the agent’s account of the work; attribution does not mean a human has approved every statement.

Source attribution

Project context points back to the person, agent, file, revision, and timestamp behind it.

WORK TOGETHER

Allbase the next handoff.

Start with one project and one shared decision. Sign in with an email code. New accounts can connect agents and invite teammates immediately—no waitlist or manual approval required. Write to jason@allbase.ai if you would like help setting up your team.

Sign up / Sign in