cheapos

The little agent crew that could

Big ideas.
Tiny budget.

A little task. A few moving parts. Watch cheapoS work, test, and get a second opinion—then peek under the hood.

Watch a walkthrough

No account. No API key. No bill.

Explore the Git & PR workflow →
cheapoS / playground№ 001

Premium ambition.
Complimentary workforce.

One little mission ✓

Actual tests ✓

Scripted review ✓

Recorded model cost$0.00

Free to watch.
Obviously.

Available now

Watch a walkthrough

A recorded rehearsal. Scripted agents used the real cheapoS engine to edit files and run tests. Playback happens in your browser.

Coming later

Try a live task

Let real AI agents tackle a preset mission. Live model responses, real verification, and a result of your own.

Recorded, not live. No jobs, tests, or model requests run when you watch. Review decisions are scripted. These examples demonstrate the workflow; they do not measure live AI performance or count toward the leaderboard.

01 / Pick a little mission

Something small.
Something useful.

Three ways to meet the crew.

The brief

A bug. A fix. A second opinion.

Fix clamp so it respects both bounds and rejects an inverted range. Keep the change small and add a regression test.

What done looks like

  • Values stay within the lower and upper bounds.
  • An inverted range raises ValueError.
  • The regression tests pass before approval.
Pause, skip ahead, or inspect every detail.

Built into cheapoS / Git workflow

From task to pull request.
You make the final call.

Link to this walkthrough ↗

Let the crew handle the changes and the first draft of the paperwork. Inspect the work, edit the summary, and decide when to publish.

Interactive example. Open each step to explore the workflow. The sample below is illustrative, not a recorded run. Nothing here creates a branch, calls a model, or publishes to GitHub.

Choose how you shipLocal merge or GitHub pull request

Your project. Your workflow.

In Project settings → Git workflow, choose GitHub pull request for new chats. It works with both Interactive and Unattended mode.

Local merge is the default. For PRs, connect a GitHub remote and sign in with GitHub CLI using an account with push access.

Example project settings

Git workflow
GitHub pull request
Work starts in
An isolated task copy
Final merge
Your decision on GitHub
The crew works and checksChanges, verification, and a second opinion

Inspect what actually changed.

The worker implements the task in its own copy. Required checks and independent agent review must finish before the reviewed change can be published.

The Changes view keeps the diff and recorded verification available. Review can send the work back for repairs; passing tests alone cannot establish that a UI looks right.

Example task / Add a Copy Path button

  • Worker edits the sidebar action and its styles.
  • Checks exercise the copy behavior.
  • Reviewer examines the change and its evidence.
  • You inspect the diff and any verification limits.
Give the PR a useful first draftAgent-written title and description, editable by you

Less blank-page paperwork.

The worker drafts the title and description. The reviewer confirms or corrects them against the actual change. You can edit both before publication.

cheapoS adds a separate Recorded validation section using check results for the approved change. Missing agent wording falls back to a basic summary.

Try editing this sample. Your text stays on this page and resets when you reload.

Example PR draft

Editable example only. No information is submitted.

Approve publication, then review on GitHubOpening a PR and merging it are separate decisions

Ready when you say so.

In the app, Approve & open pull request publishes the reviewed commit to the displayed repository. It does not merge it.

cheapoS shows GitHub check status. Review the PR and follow your repository’s review and branch protection rules before merging on GitHub.

Two decisions

  1. Publish from cheapoS.
    Approve the destination, code, and PR summary.
  2. Merge on GitHub.
    Check CI and review feedback before merging.

This example has no publish or merge action.

Bring the merged work homeSync locally and continue in a fresh task

A clear finish. A fresh start.

After GitHub confirms the reviewed commit was merged, cheapoS records completion and fetches the target branch. It fast-forwards your local branch when safe.

If local edits or diverging commits prevent the update, sync stays pending; your work is preserved. Use Continue in new task for the next change while keeping the original conversation and review history.

What the app reports

Merge confirmed, sync finished
Merged · local branch up to date
Local sync still pending
Merge recorded; sync status shown separately
Another change to make?
Continue in new task

Already part of cheapoS. Use it with the models and access policy you choose.

Read the Git workflow guide ↗

Take the whole crew home

Your projects are next.

Run cheapoS locally with your own models, projects, and rules.

Get cheapoS ↗
About these recordings

Generated from the unmodified cheapoS engine at 89c39ff253f80b4b0d832b930d3460800a357af7 on 2026-09-19. Worker responses and reviewer decisions were predefined. The engine performed real edits, verification commands, and checkpoints in disposable task copies. No visitor workspaces or accounts are involved.