Skip to content
clandclandcland

Features

Everything cland does, one line each. Each line links to the page that explains it.

The work

Section titled “The work”
  • Items and the tracker. Releases, categories, epics, specs, tasks, questions and maps are Markdown files in your repository, with a container ladder you configure in .cland/config.toml.
  • Tasks with status, rank, size and criteria. The hub moves a task’s status on claims, verdicts and merges; rank sets what is next; acceptance criteria carry done and verified marks.
  • Categories. Bugs, Tech debt, Follow-ups and Ideas collect what the crew finds along the way, until you promote it.
  • GitHub issue import. One command brings your open issues into the tracker.
  • Plans with stages and lanes. Every epic is planned before work starts: ordered stages, parallel lanes and a QA policy per stage, approved by you if you want.

Talking to the crew

Section titled “Talking to the crew”
  • Topics. You talk to the Coordinator in topics bound to units of work, each with a status that says who is waited on.
  • General and the Agents topic. A standing topic for free conversation, and a read-only one that keeps agent-to-agent traffic out of your way.
  • Asks and the inbox. Questions travel up the chain of leads; only the Coordinator asks you, and the inbox holds only what needs you now.
  • Layers. Now, watch, background and archive decide what demands your attention and what waits behind a fold.
  • Artifacts. Reports, diagrams and pages a session shows you, as chips in their topic and rendered in the browser.

The crew

Section titled “The crew”
  • Sessions and direct harness access. Every session is a real Claude Code, Codex or OpenCode session; attach to it and type into it at any time.
  • Roles and crew configuration. Choose the harness, model, effort, account and permissions of every role, and how many sessions of each run.
  • Accounts and limits. The usage windows Claude Code and Codex report in one place (OpenCode has no limit data); a limited account stops new launches, and you choose what happens next.
  • Your Aide and the onboarding. Your own session studies the project, proposes the crew and drafts the first plan with you.
  • The rulebook. The project’s own rules for how work is done, delivered into every role’s instructions.

Landing the work

Section titled “Landing the work”
  • The merge gate. A task lands on dev only with current clear verdicts from other sessions and every criterion done and verified.
  • Verification for any stack. Your own check and test commands through one queue, with an idempotent prepare command for cloud images and runs.
  • Cloud runners. Run verification on fresh DigitalOcean machines in parallel, under a daily spend cap the hub enforces.
  • Releases from the item. cland release tags the release, writes its notes and pushes to GitHub in one atomic push.

Where you work

Section titled “Where you work”
  • The terminal workbench. cland’s own Neovim, with a palette that shows every action and its key; no Neovim experience needed.
  • Web and phone. The same hub in any browser and on your phone, installed as an app, with notifications for what needs you.
  • Remote control. Follow and steer the crew from a private Telegram chat or a channel in your own Discord server. General goes both ways; asks and Codex and OpenCode approvals arrive as cards. Send photos, files and voice notes. Pair through cland setup on the machine running the hub.
  • The CLI. Every command by area; most take --json for scripts.