One shared project, no tool standardisation
Everyone keeps the AI they work best in. The record is shared.
The Problem
Teams used to standardise on one tool so that everyone shared context. That is a lot to ask when one person lives in a research tool, another in a writing tool and a third in a coding agent.
So context splits along tool lines. A colleague worked something out last week, in a chat you cannot see, in a tool you do not use. A newcomer relies on whoever has time to explain. Someone back from leave cannot tell what has changed.
How Stompy Helps
Put the work in a shared project. Each person carries on with whichever AI suits them.
A teammate in a different AI sees what you decided without you having to tell them, because the decision is in the project. A newcomer starts from the record, not from whoever is free. Someone returning from leave opens the project, reads the brief and the project history, and sees where things stand and what has happened while they were away.
The record becomes the team's own account of why things are the way they are. As with a personal project, people decide what goes in; Stompy keeps it, finds it again and flags a clash. Nothing is captured that somebody did not lock.
Our own shared projects have carried hundreds of sessions of real work, with more than one person working in them at the same time.
Limits, plainly. Only what you lock is kept, so a decision is in the record only if somebody locked it. Nothing here is automatic: you read the record when you open the project. It does not replace the reporting in a tracker.
Integration Walkthrough
Create the project and invite people
In the web app, create the project as a shared project, then use Invite to generate a link. You can restrict it to one email address and choose whether the person joins as a contributor or a viewer. They open the link, sign in and accept.
# nothing to run: this step is in the web app# Project > Invite > choose contributor or viewer > send the link
Each person connects their own AI
Everyone adds Stompy to their own tool and signs in with their own account. They do not need to use the same tool.
project_info(name="team-project")project_brief(project="team-project")
Lock decisions where the team can see them
Record the decision and the reason, so a colleague in another tool does not have to ask.
lock_context(project="team-project",topic="release_checklist",content="""Agreed: ...Reason: ...Owner: ...""")
Hand work over on the board
A ticket is a request someone can pick up later, with what they need already on it.
ticket(action="create",project="team-project",title="Update the checklist after the review",description="Where: ... Exact change: ... Why: ... Must not change: ...")ticket_board(project="team-project")
Catch up after time away
The brief says where things stand. The history lists lifecycle changes and the milestones people logged.
project_brief(project="team-project")project_history(project="team-project", since="2026-09-01")
What You Get
- No tool standardisation: each person keeps the AI they work best in
- Newcomers and returners start from the record, not from a meeting
- Decisions carry their reasons, so a colleague in another tool does not undo them by accident
- Nothing is automatic: people decide what is kept, and tickets wait until someone opens the project
Start your own record
Join the waitlist and we will tell you when your place is ready.
Related guides
Handing work between AI sessions
Things you can do
Work stops living in a chat window that is about to close
Using several AI tools without starting over
Things you can do
You stop being the clipboard between your AI tools
Claude Code
AI Coding Assistants
One record your terminal sessions start from