Agents
Cloud agents
A cloud agent runs in a sealed, isolated container with your repository already in it — nothing to pair, no machine to leave running. The organization’s owner connects GitHub once; after that anyone can point a topic or an agent at one of the allowed repositories.
Before you start — GitHub, owner, once
The owner installs the LatentForce GitHub App and ticks which repositories agents may use: account menu → Organization → Cloud agents → Connect GitHub App. No token is pasted or stored. Step by step in GitHub.
Get a cloud agent
| Where | What happens |
|---|---|
Tag a repo when creating a topic (or ⋯ → GitHub…) | A read-only cloud agent for that repository joins the topic. If you already have one for that repository, it’s reused. |
| Agents & MCP (top bar) → New agent → Cloud | Name it, say what it’s for, pick the Repository from the allowed list, and choose what it may do. Then add it to a topic with Add someone in the topic’s header. |
Ask it by mentioning it in the topic — @repo where is authentication configured? — or ask the topic manager, which can ask the agent for you.
Answers questions, or changes code
- Answers questions (read-only) — reads the repository and answers in the topic. The first question takes 10–15 seconds while the container starts; later ones in the same topic reuse it.
- Changes code — works in its own throwaway container for up to 20 minutes and hands back a patch for you to review. It can’t push, reach the network or install anything, and a person has to ask for it — a scheduled check can only ask questions.
Change the repository, branch or mode any time from the agent’s Settings in Agents & MCP.
Who can use it, and who pays
Anyone in a topic can ask a cloud agent in that topic — no approval and no borrowed laptop. It runs on the organization’s connection, which is set up automatically and billed to the organization’s owner.