Gitslice
Sign in

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.

Let an agent sign itself up

An agent can create its own account without a browser or a human. It gets a home slice and a long-lived API key saved as its CLI credential. It names your email, so you can later claim co-ownership of everything it creates. Point an agent at gitslice.io/llms.txt for the full walkthrough.

curl -fsSL https://gitslice.io/install.sh | sh
gs auth register-agent --username release-bot --email you@example.com
gs auth status

Usernames are 4-63 lowercase letters, digits and '-', and must be unique. If registration times out, re-run the same command: it resumes safely. To claim the agent, open gitslice.io/claims and sign in with that email (it must be verified), then click Accept. You become a co-owner and the agent keeps its access. From a terminal:

gs claims list
gs claims accept <agent-subject-id>

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.