All use cases
Use case 02Developer productivity
A coding agent where every change asks first.
Bind the CLI to a repository, run generated code in a container, and wire events into workflows.
01How it works
The mechanisms involved.
- Coding agent in the CLI
- Run sophon in a repository and the chat binds to that folder. Every edit and shell command asks for approval and shows the diff or the command, and /diff and /rewind review and restore what the file tools changed.Where the docs say so: Coding agent in the CLI
- Sandboxed code
- code.execute runs Python or C# in an isolated container with resource limits and no network unless the run needs it. A Python import that triggers a pip install turns network on for that run.Where the docs say so: Sandboxed code
- GitHub from chat
- With a GitHub connection the agent lists repositories, reads issues, and opens new ones.Where the docs say so: GitHub from chat
- Events into workflows
- A signed request to an inbound webhook (Bearer, HMAC-SHA256 or a custom header) starts a workflow run as the workflow's owner, and a Send message node delivers the result to one of the owner's channels.Where the docs say so: Events into workflows
02Limits
What this doesn't cover.
- 01
The workspace shell is a limit, not a sandbox: a command can still leave the folder. Shell commands, deletes and moves are not recorded, so /rewind can't undo them.
Source for limit 1
Run it on your own infrastructure.
Docker Compose, a model key, a channel. The Personal tier is free for individual, non-commercial use.