~/sursakit

// docs

Workflows

The day-to-day loop in Sursakit:

1. Edit and run

  • Open the file in the editor.
  • Click Run on the service that consumes it (or Run all).
  • Watch logs in the bottom panel; iterate.

2. Commit through version control

  • Open the Version Control panel.
  • Review the working diff.
  • Stage, then commit. Use Generate commit message to draft a message from the diff.
  • Use Discard or Rollback when an experiment didn't work.

Sursakit uses Jujutsu underneath but speaks Git on the wire.

3. Open a pull request

  • From the version-control panel, push and open a pull request against your connected GitHub / GitLab / Bitbucket remote.
  • Review PRs without leaving the workbench. Conflicts open in the three-way editor.
  • Merge when ready; the PR closes upstream automatically.

4. Hand work to Codex

  • Open the chat panel and describe the task.
  • Codex runs inside an isolated runner container, sees your services through the MCP control plane, and works in its own session.
  • When it's done, it lands the change as a pull request you review the same way you'd review a teammate's.

5. Automate with skills

  • Define a skill — a reusable capability the agent can use.
  • Use it from chat, tasks, or a saved automation that runs on a schedule or by hand.
  • Each automation run is a chat thread you can audit.

6. Track work with tasks

  • Create tasks for bugs, features, or follow-ups.
  • Assign to a teammate or to Codex (mention the agent as the assignee).
  • Webhook integrations turn GitHub / GitLab / Bitbucket events into tasks automatically.