Quickstart

This gets you from login to a real D1-backed card and run attempt. It does not start an external Codex executor yet.

Prerequisites

• OpenClaw GitHub org membership.
• Bootstrap token from deployment secrets, or GitHub OAuth already configured.
• Access to https://crabyard.openclaw.ai/app/.

1. Log In

Open https://crabyard.openclaw.ai/app/.

• Use GitHub OAuth if configured.
• Use the bootstrap token for setup/recovery.

Bootstrap sessions last 1 hour. GitHub sessions last 15 minutes.

2. Add Access

Open Admin.

Add users or teams:

@steipete
@openclaw/maintainer

Roles:

• owner: full admin.
• maintainer: create/start/control cards.
• viewer: read-only board and attach/watch.

3. Enable Repos

Add repos in owner/repo format. openclaw/openclaw is sorted first and is the default repo in the card form.

Enabled repos drive:

• Card creation.
• Issue/PR preview search.
• CRABYARD.md workflow evaluation.
• Run allowlist checks.

4. Optional: Evaluate CRABYARD.md

In Admin → Workflows, enter a repo and refresh CRABYARD.md.

Supported shape:

---
runtime:
  default: auto
merge:
  default_policy: open_pr
---

Invalid configs are visible and ignored. stall_ms, cap, prompt_prefix, and the Markdown body are parsed/stored for future policy work, but only runtime and merge defaults are effective today.

For private repos, the Worker needs deployment GITHUB_TOKEN access to fetch CRABYARD.md; it does not use the logged-in user’s OAuth token for this refresh.

5. Create a Card

Click New card.

Required:

• Repo
• Prompt

Optional:

• Title
• Runtime
• Merge policy

Blank title is generated from the prompt. Blank merge policy uses repo default, then open_pr.

6. Create from Issue/PR Number

Type #76552 in board search. Crabyard previews matches across enabled repos when GITHUB_TOKEN is configured; without it, preview falls back to the preferred repo or first enabled repo. Choose a match to create a card with the GitHub URL, title, body, repo, runtime auto, and repo-default policy.

7. Start and Attach

Click Start on a Todo card.

The Worker will:

• Check capacity, default cap 20.
• Verify repo allowlist.
• Evaluate cached repo workflow defaults.
• Select container or crabbox.
• Store a run attempt with selection reason and capabilities.
• Move the card to Running and append events.

Click Attach to open the Ghostty WASM session grid. The current grid replays D1 events. Live PTY/app-server transport is planned.

Troubleshooting

Repo blocked by allowlist

Add the repo in Admin → Repos.

GitHub user not allowlisted

Add a direct @login entry or the exact team slug, for example @openclaw/maintainer.

Capacity blocked

Increase cap in Admin → Policy or move active runs out of Running.

Take over hidden

Takeover appears only for active runs whose runtime capabilities include takeover. Container runs do not advertise takeover.