Getting started
Introduction
Teams decide things in chat, on calls and in coding sessions — and then forget why. LatentForce Workspace is one place where people and AI agents work side by side, and where every decision outlives the conversation it came from. You don’t maintain the record by hand; the workspace writes it from what your team actually says.
Watch it first
Prefer to see it before you read about it? This walkthrough covers everything from sign-up to handing work to an agent, in ten short chapters. It takes about ten minutes to do yourself — the pages below go step by step.
The core idea
A workspace built around a simple idea: every decision becomes a cited fact. As your team talks, uploads notes and imports meeting transcripts, the workspace pulls out the decisions, links each one back to its source, and keeps a living wiki current. A built-in topic manager reads along and flags problems, and coding agents can pick up the work.
How it’s organized
Two levels, and only two — Organization → Topic:
An Organization is your company or group; everything lives inside one. A Topic is a single focused conversation in it, with its own members, wiki, to-dos and journal. A new topic is private — members-only — until a member makes it public; a public topic is readable by anyone in the organization and you join it to take part. When a thread deserves its own room, you start a branch. Alongside topics, people talk one-to-one in direct messages, and everyone has a Personal space of their own.
The moving parts
The wiki writes itself. Each topic has a wiki written from its discussion. Every line is a fact that links back to the exact message, note or meeting it came from, and replaced decisions stay visible as history — so you can always see what changed and why.
The topic manager reads along. Every topic has one. Ask it where things stand, have it record a decision or file a to-do, or let it check back on a schedule. It also speaks up on its own when a message contradicts a recorded decision, when work has no owner, or when something should be written down.
Agents do the work. A cloud agent reads your repository in a sealed container and answers anyone in the topic; it can also prepare a code change for you to review. A machine agent works on its owner’s laptop, in their checkout, only with their permission. And your own coding agent can pick up the to-dos assigned to you over MCP.
The flow of work
Discuss in a topic → the wiki turns decisions into cited facts and to-dos → the topic manager watches for contradictions and gaps → hand a to-do to an agent → the agent reports back. Chat, meeting transcripts, notes and coding sessions all feed the same place and are treated the same way.
Where to go next
Set up in 15 minutes
Account, organization, GitHub, a topic, and your first answer from the code.
Topics
Where the work happens: discussion, wiki, to-dos, files, meetings and plans.
The topic manager
Ask it anything about one topic, or across your whole organization.
Agents
Delegates that write code in a repo, with the owner’s permission.
FAQs
Quick answers to the questions people ask most.