For Claude Code and Codex

A quest log for your repo and your agents

Readable plans. Explicit dependencies. Reviewable Git changes.

Quest keeps your plans as Markdown files in your repository, so you and your agents read, accept, and finish the same work.

Paste this into Claude Code or Codex:

Follow https://quest.moq.dev/setup to set up Quest here.

Get startedView on GitHub

Quest log

  • Add the CSV endpoint
  • Add a CSV download button
  • Document the export format
  • Stream exports for large accounts

The format

Every plan is a file

A quest is a Markdown file scoped to one pull request: its objectives, what has been decided, and what stands in the way. Epics are folders, and milestones group them by horizon.

Any agent that can read your repository can find the work. No database, no tracker to sync, and quest check keeps every link and dependency honest.

Your repository
quest/
  README.md      # The roadmap
  m0/
    README.md    # First milestone, in priority order
    export.md    # Available
    download.md  # Requires: export.md

Coordination

Coordinate agents through Git

No server holds the plan. Agents coordinate the way your team already does: with branches and pull requests.

  1. Available

    quest unblocked lists the quests with nothing standing in their way.

  2. Accepted by @agent

    A live runner lock takes active work. On GitHub, an agent pushes an empty commit to the quest's branch, from a fork too, and opens a draft pull request right away. The earliest open pull request holds the claim.

  3. Ready to turn in

    The work lands on that pull request, marked ready for review, plan and code reviewed together.

  4. Quest complete

    Merging deletes the plan, Git keeps its history, and the next quest becomes available.

Rendering

As written, as read

The same quest: the Markdown your agents edit, and the page you read.

quest/m0/download.md
# [M] Add a CSV download button

## Goal

People can download their data as a CSV from
the settings page.

## Plan

Call the export endpoint. Show progress, and let
people retry a failed download.

## Required

- [CSV endpoint](/quest/m0/export.md) - the
  button needs something to call

## Closes

- [#42](https://github.com/acme/app/issues/42)

Add a CSV download button

M

Requires: CSV endpoint

Objectives

People can download their data as a CSV from the settings page.

Plan

Call the export endpoint. Show progress, and let people retry a failed download.

Requires

  • CSV endpoint: the button needs something to call

Rewards

  • Closes #42

Workflow

How it works

  1. Plan with your agent

    /quest-plan asks the questions that turn an idea into scoped quests, with dependencies, in priority order.

  2. Run agents in parallel

    /quest-start takes one quest to a pull request. /quest-spawn sends several agents out in parallel.

  3. Review and merge

    You review every change. /quest-merge lands it once checks and reviews pass, and the next quest becomes available.

In Codex, use $quest-plan and friends. The binary carries the skills, so your repository pins one version.

Roadmap

Long-term plans, as a map

Quest is planned with Quest. Milestones become regions, epics become paths, and every quest is a waypoint coloured by its size. Each deploy charts the tree as it stands.

  1. Milestone 0

    moq-dev adoption

    185 of 211 quests complete
    1. Land through GitHub's merge queue with an async fixer · 7 of 12 complete

      1. SVerify the public repositories' merge queues land PRsready
      2. SHarden the merge-queue runnersready
      3. LTests fit their timeout on the queue runnerready
      4. SThe land daemons prune their own logsready
      5. MRetire the batching host gateblocked
    2. Merge through a host gate until the merge queue replaces it · 4 of 5 complete

      1. SThe fixer's container trusts public TLS certificatesready
    3. Main path

      1. SThe land fixer resolves every mechanical failure itselfready
      2. SReview sessions keyed by upstream branchready
      3. XSTurn off Codex cloud reviewsready
      4. XSCodex keeps a way to skip project configready
      5. MA Claude session's checkout is released when the session endsready
      6. XSReport claude rm's unlock advice upstreamready
      7. SModel checkblocked
    4. Kix decision UI · 45 of 52 complete

      1. SDeploy the Worker to quest.moq.devready
      2. MPer-job opencode saved outputready
      3. MThe Claude Code sandbox's boundary test runs nightly in CIready
      4. LRunner account pool through CLIProxyAPIready
      5. SSet up the Kix bot's pilot repositoriesblocked
      6. MEnroll private repositoriesblocked
      7. LSpawn and iterate work from decision promptsblocked
    5. Route quests to models by size · 5 of 9 complete

      1. Squest agent starts Grokready
      2. Skix records its follow-up sessionsready
      3. M/quest-spawn routes each quest down a ranked listblocked
      4. XSmoq-dev repositories pick up model routingblocked
    6. Agents get the dev shell from user settings, not repository config · 1 of 3 complete

      1. S.worktrees/ stays out of git statusready
      2. SRepositories drop their dev-shell configready
  2. Milestone 1

    Public release

    28 of 41 quests complete
    1. Main path

      1. LUser state in their RunnerHubready
      2. SCut a release with the worktree hooksready
      3. MRe-plan workers that fit a 5-minute prompt cacheready
      4. XSRetire the ## Decisions needed headingready
      5. XSBun's EFAULT on concurrent rmSyncready
      6. SOpen kix.questblocked
      7. MPrepare launch materialblocked
      8. Lquest usage reports models, cost, and accuracyblocked
      9. MModel checkblocked
    2. Kix for any repository · 5 of 8 complete

      1. MVerify the sandbox on macOS, then lift the approval gateready
      2. LBuild untrusted PR devShells in a VMready
      3. MGuide maintainers through Kixblocked
    3. Quest log theme · 8 of 9 complete

      1. SConnect the landing page to Kixblocked
  3. Milestone 2

    Later work

    3 of 19 quests complete
    1. Cloud runners · 0 of 4 complete

      1. LFund cloud runners with maintainer API keysblocked
      2. LEnable free cloud runners with one clickblocked
      3. LFund cloud runner jobs with donor allocationsblocked
      4. LCharge for cloud runner computeblocked
    2. Main path

      1. LAnswer decisions from a native mobile appready
      2. LShare your runner with other projectsready
      3. Lquest review runs Grok and opencode reviewersready
      4. XSGet approved for hosted Sign in with ChatGPTready
      5. XSDelete the legacy hold labelsready
      6. XSWorktree hooks name the launch route when quest is missingready
      7. L/quest-council reviews with one model per maker, blindblocked
      8. LIsolate untrusted local donor jobsblocked
      9. MUse ChatGPT for web login and cloud runnersblocked
    3. Donated review and check automation · 0 of 3 complete

      1. LDonate repository check capacityblocked
      2. MShare a main-only Nix cache across runnersblocked
      3. MDonate independent agent reviewsblocked

Size: XSSMLXL

A solid waypoint is ready or in review; a dashed one is blocked. Charted from quest/ on 2026-11-04.

Contribute

Built in the open

Quest is open source, and it is planned in the open with Quest itself. Contributors pick up quests from the same log your agents read.

Soon you will be able to offer tokens from your own agent account to fund a quest you want finished.

Offer tokens

Arrives with the quest board. Until then, pick an available quest and send your agent to finish it.

Browse the questsContributing