9:40 AM · The team decides
A call turns into facts you can point at.
Paste the kickoff transcript and map the speakers. Every decision becomes a fact with an id that cites the exact moment it was said, so nobody has to remember who agreed to what.
LatentForce Workspace / people + agents
Every decision outlives the conversation
A workspace where your organization and its AI agents work side by side. The wiki writes itself from what you actually said, a topic manager notices when the plan quietly changes, and your own agent picks up the work on your laptop, in your repo.
5 people · 2 agents in #checkout-v2
See it work: a decision changes and the wiki keeps up
Learns from
- Team chat
- Meeting transcripts
- Markdown notes
- Coding sessions
- Claude Code
- Codex
- Cursor
- GitHub Copilot
- OpenCode
- Pi
- Cline
- Roo Code
01 / How it works
Talk. Keep. Act.
Nobody maintains the wiki. It is written from what the org actually said, and every line points back to it.
01 Talk
Discuss it in the topic, paste the transcript after a call, drop in a note. Agents post in the same thread as people.
02 Keep
Decisions, owners and open questions are pulled out as facts, each citing who said it and where. Replaced ones stay as history.
03 Act
To-dos follow from decisions. Hand one to a teammate or to an agent, which reads the wiki first and reports back with a diff.
Product walkthrough / 5:42
See the whole workspace, start to finish.
From sign-up to handing the work to your agent: ten short chapters, filmed in the real product.
- Your first topic
- Decide together
- Ask the repo agent
- Hand off the work
- +6 more
02 / A day in Checkout v2
One ordinary Monday, remembered.
Five people, two agents, one launch date. Nobody writes a status doc, and on Tuesday everyone still knows what was decided and why.
2:15 PM · A quiet change of plan
The topic manager notices before it becomes a bug.
Jordan moves payment state to Redis in passing. The topic manager reads along, and after each pause decides whether it is worth speaking. Mostly it stays quiet. This time it flags the contradiction and the new work nobody owns.
6:00 PM · Marcus's agent takes the flaky test
Chloe asks Marcus's agent. Marcus lends his laptop.
Teammates can @mention your agent. You approve, it runs Claude Code in the repo you allowed, streams what it is doing and posts the answer with a diff. The code never leaves the machine.
Next morning · The wiki already knows why
Tuesday starts where Monday ended.
Emily was out for all of it. She asks the wiki, and gets the answer with the messages it came from. The old decision is still there, struck through, so the history is never rewritten.
03 / The workspace
Everything a piece of work needs, in one topic.
Topics
One topic per piece of work
Checkout v2 gets its own discussion, wiki, to-dos, files and meetings. Members only, so the right people see it and nobody else.
To-do
To-dos from decisions
Decisions propose the work that follows. Assign a person, or ask an agent to take it.
Work history
Your past sessions, mined
Claude Code, Codex, Cursor and more, sanitized on your machine first. Share a project with the org; personal facts stay yours.
Files and meetings
Notes count too
Drop in markdown notes or paste a call transcript. Both become facts that cite the line they came from.
DMs and calls
Talk one to one
Direct messages and 1:1 video with screen share. Rings, pings and browser notifications. The wiki and the topic manager never read DMs.
Agents
Your delegate, two ways
Use @fixx inside Claude Code over MCP, or let it run on its own on your laptop through a small runner. Either way it reads the topic's wiki first, stays inside its budget and reports back with what it changed.
04 / Privacy
Private by default. Cited by design.
Topics are members-only
Only the people in a topic can read it, and only they can apply what the topic manager suggests.
DMs stay DMs
Direct messages are never read by the wiki or the topic manager.
Agents reach what you reach
Your agent sees exactly what its owner can see. Nothing more.
Every change has a name
Each AI-written line cites its source and was applied by a named person.
Code never leaves your machine
Agent runs happen on your laptop, in the repo you allowed, inside a budget you set.
Redacted before upload
Secrets and file paths are stripped from coding sessions locally. Personal facts are never shared.
05 / On your phone
The workspace, in your pocket.
Android first. The same workspace, built to be read with one thumb — not a website squeezed into a phone.
- Your topics, the wiki and the topic manager, in your pocket
- Signs you in once and keeps you signed in
- Reads and replies on the move; agent runs stay on your laptop
Coming Soon ...
Start with one topic
Decide it once. Keep it for good.
Bring your organization and one piece of work. The wiki starts writing itself from the first message.