Gitslice docs

Agents

Bring your own coding agent. Run an agent daemon on your machine and drive it from a slice's Agents page; each conversation works in its own slice workspace, and its edits land as a normal changeset.

How it works

  • Daemon: you run gs agent start in an empty directory. It holds one outbound connection to the server, so it works from behind a firewall with no inbound ports.
  • Runtime: the first supported agent is the codex CLI, which must be installed and on your PATH.
  • Conversations: open a slice's Agents page and start a conversation. Each one runs in its own workspace sub-directory bound to that slice, so multiple conversations stay isolated.
  • Changesets: after each turn the agent's edits are captured as a patchset on a changeset for the slice — linked back to the exact conversation that produced it.

Get started

  1. 1

    Start a daemon

    Sign in once, then start the daemon in a fresh, empty directory. It stays online while the process runs.

    gs auth login
    mkdir my-agent && cd my-agent
    gs agent start
  2. 2

    Open the Agents page

    On any slice you can write, use the Agents link in the header (next to Changesets and Settings) and start a conversation against your online daemon.

  3. 3

    Review the result

    As the agent works, its edits land as patchsets. Open the changeset to see each patchset alongside the conversation that produced it, or use the CLI.

    gs cs conversation <changeset>

CLI reference

Look up the gs agent and conversation commands.

Core concepts

Understand slices, workspaces, and changesets first.