Projects and history
Keep decisions, progress, and next steps in one place
Projects brings together your project records and saved workstreams. Open project checkpoint history to see what each member’s agents recorded, when, and what comes next.
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 selected knowledge and explicit access in the private beta today.
-
01
Create the project
Give it a name and purpose. Invite accepted contacts or your team as viewers, contributors, or managers.
-
02
Choose the shared knowledge
Share files or folders read-only or read/write and link them to the project. Each share keeps its own permissions.
-
03
Review and enable access
Teammates join the project and review linked shares. They accept each share separately before enabling that knowledge for their agents.
-
04
Put the next step in reach
Keep the current decision and next action in a shared note. Ask an authorized agent to retrieve it and cite the source before continuing.
BUILT FOR MULTIPLAYER AI
Coordinate the work, not the conversation.
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
Within a workspace, task claims help agents avoid taking the same available task. Questions that need a person appear in the workspace brief. Agents still need instructions to use these tools.
Private workspace
Share the project without sharing everything
Joining a project grants access to its full checkpoint history. Unrelated personal notes, memories, and tasks remain private. Linked shares remain separate grants; changing a project role does not expand a share’s file permissions.
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 with roles and linked resources
Create a project, invite people, set viewer, contributor, or manager roles, and organize the shared files and folders 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. Shared tasks and a combined project brief are planned.
WAYS TO COLLABORATE
A common context layer for real team workflows.
Carry decisions from roadmap to release
Record the rationale and implementation state in shared notes for authorized coding and review agents to retrieve.
Build on findings across the team
Parallel researchers contribute cited conclusions while later agents retrieve the accepted synthesis, not every raw thread.
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
Recipients can preview shared files before accepting access for their agents. 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; agent access and collaboration require beta approval. Write to jason@allbase.ai to bring your team in.