Indent completes tasks by executing real tool calls — shell commands, file edits, database queries, browser actions — on a real computer, then reports what it did and how it verified the result.
A session
You work with Indent in a session. You give it a task, it does the work and reports back, and you keep going from there. A session retains its full context, so you and your teammates can pick up where the last message left off.
Organization-visible sessions are multiplayer. Teammates join with full context, and Indent knows who’s on the team. Sessions are visible to your organization by default. If you created a session, you can make it private from the share control in the session header. Making a session private is permanent. See Multiplayer sessions and Private sessions.
The computer a session runs on
Every session runs on a real computer, where Indent runs commands and edits files the way you would at a terminal.
- Cloud sandbox — by default a session runs in a clean cloud sandbox. Point it at a development environment to start with your app built, its services running, and its tests ready.
- Local computer — the desktop app runs a session on your own computer, in a folder you choose, for work with local files and tools. A desktop local session is always private.
How Indent verifies its work
Indent doesn’t assume a change worked — it checks. It runs the tests, reruns the query, reads the logs, or opens the running app in a real browser and clicks through the flow. When it reports back, it tells you what it verified and how, so you can trust the result or see exactly where it stopped short.
What Indent can access
Indent acts only through the tools you connect and within the access you grant.
- Connected integrations only — Indent works with the integrations you’ve connected and the ones you select for a session, nothing else.
- Database permissions — PostgreSQL and ClickHouse enforce read-only queries. BigQuery uses the connected service account’s IAM permissions, so connect a read-only account to prevent writes.
- Secrets provided through the app — saved values are masked after entry. Runtime variables are available to commands and background processes on the session’s computer.
- Organization or personal scope — organization connections are shared with the team; personal connections are owned by one person. Personal integration tools run only in private sessions. A connected personal GitHub account can also author pull requests requested by its owner in any session where they participate.
For the full picture, see Permissions and data.