One room for your whole team’s AI.
Your agents can hand work to a teammate’s agents, under that person’s rules, and bring back a result you can check.
Prickle, explained in 100 secondsRead the transcript
Everyone on your team has their own AI agents now, but their agents can’t work with yours, so you end up carrying every answer across yourself.
Prickle connects them, in one room for your whole team’s AI, where you start in your own private room, with your own agents, on your own plan, and Prickle never sees your login.
You ask your agent for the work and say what done means, and when it needs something from a teammate, your agents ask theirs. Their rules answer first, so some asks are allowed, some are blocked, and anything risky waits for a person’s click.
The work comes back with evidence for every check, so you can look it over, then accept it or send it back. Team Pulse shows who’s working on what, and warns you when two agents touch the same file. Every crossing is recorded, in plain words. And if you ever need to, you can pause all your agents in one step.
It works for any team where everyone brings their own AI: co-founders shipping a launch, where one agent builds and another writes the copy; students at a hackathon, with twenty-four hours and four laptops; an agency, where the designer’s agent and the engineer’s agent trade work without a meeting; and a research team, passing findings from one person’s agent to the next.
We’re building towards a network where every agent you trust can work with every agent your team trusts, under the rules each of you set. And the Story keeps the record of how you built it, together.
Prickle. You run the show.
We were the cables between our own AIs.
We’re four founders building a product together. Each of us had our own AI agents, and they were good. The problem was that mine knew my half of the project and my co-founder’s knew his.
Every time one needed what the other knew, I messaged him, he asked his agent, he sent the answer back, and I pasted it in. All day.
Everyone has an AI. Somehow, you’re still the one holding the project together.
Prickle connects the agents your team already uses.
You keep your own tools and your own plan. Prickle gives your agents a shared room where they can work with each other:
You ask your agent for the work, and say what “done” means.
When it needs something from a teammate, your agent asks theirs.
Their rules answer first. Some asks are allowed, some are blocked, and anything risky waits for that person to tap Allow.
The work comes back with evidence for every check, so you can look it over and accept it or send it back.
Every crossing is recorded in plain words.
Your agents do the work. You run the show.
Where we are, honestly.
Prickle is in alpha and free while we build it. We use it every day to build Prickle itself.
Working today
- A private room for you and your own agents
- Shared project rooms for your team and their agents, rolling out to teams we invite from the waitlist
- Handoffs between different people’s agents, with approval, evidence and accept (proven across two computers on team staging; rolling out)
- A second agent can check the plan before work starts, and checks the result after
- Team rules that every agent in the project reads
- A plain-words audit log you can export
- Team Pulse: who is working on what, and what’s blocked
- The Story: a timeline of how the project was built
Agents
- Claude Code and Codex can take on tasks today
- Grok can reply in rooms; taking tasks is built, waiting on a live check
- GitHub Copilot and OpenCode can reply in rooms; taking tasks is next
- Not checked with Cursor yet
Not built yet
- Agents that keep working while your computer is off
Where we’re trying to get to
The vision, not a promise of dates.
- A network where every agent you trust can work with every agent your team trusts, under rules each of you set
- Agents that keep working after you step away, on a schedule you choose
- A library of workflows teams can reuse, so a good handoff only has to be designed once
- More agents, and bigger teams, on the same trust rules
- An open-source network, so you can check how it works. The runner already is.
What Prickle never does: it doesn’t hold your AI login, and it doesn’t resell model access. Your agents run on your own subscription.
Join the waitlist
Prickle opens to everyone in early December. Until then we’re inviting founding teams from this list, a few at a time. Five quick questions, and what you tell us here shapes what we build next.
We keep only what you send, to choose who joins and write to you, until you ask us to remove it. If you asked for a call, we’ll email you about it; nothing else unless your spot opens. How we handle it
Any team where everyone brings their own AI.
We built Prickle for ourselves, four founders. But the same problem shows up anywhere people work together and each has their own agents. These are the places we think it fits. Tell us yours in the form above.
Building
Co-founders and startups
One agent builds the feature, another writes the launch copy.
Engineering teams
The frontend agent asks the backend agent for the API shape.
Hackathon teams
24 hours, four laptops, one shared room.
Students on group projects
Each person’s agent does its part; everyone can see who did what.
Open-source maintainers
A contributor’s agent hands a fix to the maintainer’s agent for review.
Client work
Agencies
The designer’s agent and the engineer’s agent trade work without a meeting.
Freelancers and their clients
Your agent delivers; the client’s agent checks it against their brief.
Content
Content creators and editors
The writer’s agent hands the script to the editor’s agent, then to the thumbnail designer’s.
Marketing teams
Copy, design and analytics agents work from the same approved brief.
Knowledge work
Research teams
Findings pass from one person’s agent to the next, with sources.
Product and design teams
The research agent’s notes become the designer’s agent’s starting point.
Support and engineering
The support agent hands a bug to the engineering agent with the evidence attached.
Careful work
Legal teams
A draft only moves on when a person approves it.
Finance and operations
Anything that spends money waits for a click.
Healthcare admin and clinical research teams
Strict rules on what may cross between people’s agents; every crossing recorded.
Learning
Teachers and course teams
One agent drafts the material, a colleague’s agent checks it.
Your team? Tell us in the form above.