The parts of an automation
What happens during a run
1
A trigger fires
A Slack message arrives in a watched channel, Sentry reports a new issue, someone runs
/automate in Discord, or the schedule comes due. You can also start a run with Run now or Test.2
Superlog starts a sandbox
Each run gets its own sandbox. Superlog checks out your repositories into it. Provider credentials stay outside the sandbox.
3
The agent works
The agent reads the trigger event, follows your instructions, and uses the selected connectors. It can read and edit code, run commands, query Sentry and Datadog, and read Slack and Linear.
4
The agent acts
Depending on its connectors, the agent opens a pull request, replies in Slack, or creates a Linear issue. These write actions run without a human approval step, so choose connectors with that in mind.
5
You review the run
The run page shows the agent’s messages, the tools it used, and anything it created. Send a follow-up to continue the same run in the same sandbox.
Where inference comes from
For each run, Superlog uses the first available source:- Your ChatGPT subscription, when the automation uses the Codex harness.
- Your newest API key for the model’s provider.
- The usage included in your plan.