Open source / CLI

Cue.

From an issue to a reviewed pull request.

GitHub issue 29 in the cue repository, closed, labelled agent:done, linked to pull request 32.
The interface is the issue. Cue moved this one from agent:ready to agent:done and opened the pull request.
The Cue dashboard. Total spend, token count, agent time and a cost breakdown for each pipeline stage.
The local dashboard keeps the work inspectable — spend, tokens and wall-clock across every recorded run.

A home for coding agents inside a workflow you already know. Cue uses GitHub issues and labels to move work through planning, implementation, and review.

GitHub is the interface

Labels hold the state. Issue comments hold the plan. Draft pull requests hold the result. The workflow stays close to the repository, so there is less context to move between tools.

An agent is one part of the process

Cue supports Claude Code, Codex, and Antigravity through engine adapters. Work happens in isolated git worktrees, with test and lint commands as quality gates and human approval before implementation and merge.

Keep the work inspectable

A local dashboard brings transcripts and cost tracking together. The aim is to make the path from issue to pull request something you can follow, review, and improve.

← All projects Back to the workshop