[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-80461":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":8,"htmlUrl":8,"language":9,"languages":8,"totalLinesOfCode":8,"stars":10,"forks":11,"watchers":12,"openIssues":13,"contributorsCount":13,"subscribersCount":13,"size":13,"stars1d":14,"stars7d":14,"stars30d":14,"stars90d":13,"forks30d":13,"starsTrendScore":15,"compositeScore":16,"rankGlobal":8,"rankLanguage":8,"license":8,"archived":17,"fork":17,"defaultBranch":18,"hasWiki":17,"hasPages":17,"topics":19,"createdAt":8,"pushedAt":8,"updatedAt":20,"readmeContent":21,"aiSummary":22,"trendingCount":13,"starSnapshotCount":13,"syncStatus":23,"lastSyncTime":24,"discoverSource":25},80461,"Crack-CLI","Royaltyprogram\u002FCrack-CLI","Royaltyprogram",null,"TypeScript",52,7,51,0,1,3,2.71,false,"main",[],"2026-06-12 02:04:02","# Crack CLI\n\n![Crack CLI Banner](.\u002Fbanner.png)\n\nA CLI built for Codex. More precisely, it is a tiny remote control for making Codex boss around other agents.\n\n## The Problem It Solves\n\n0. Codex's Plan mode considers every step in a single context, which creates a performance bottleneck. It feels like inviting the entire company into one meeting room inside its head.\n1. Codex tends to make the smallest possible change to the current codebase instead of thinking seriously about code quality. Sometimes the result feels like repairing a bridge with toothpicks.\n2. Instead of using agents like the oh-my series or Aider directly in a TUI, I want Codex to use them for me inside the Codex app. I want to be the director, not the keyboard intern.\n3. Most agent harnesses are only effective in specific situations, which makes them hard to use generally. They look like universal remotes, but somehow only turn on the air conditioner.\n\nCrack CLI is a tool for making these problems slightly less sad.\n\n## Quick Start\n\n0. We prepared a skill for Codex, not for you. Give Codex this prompt and let it do the chores:\n\n   ```text\n   Install Crack CLI from https:\u002F\u002Fgithub.com\u002FRoyaltyprogram\u002Fcrack-cli.git.\n   Clone the repository, run npm install, run npm run build, and link the crack binary with npm link.\n   Then install the Codex skill by copying skills\u002Fcrack-cli into ${CODEX_HOME:-$HOME\u002F.codex}\u002Fskills\u002Fcrack-cli.\n   After that, verify the setup with crack --help.\n   ```\n\n1. Make sure the GitHub CLI is installed and authenticated:\n   https:\u002F\u002Fdocs.github.com\u002Fen\u002Fgithub-cli\u002Fgithub-cli\u002Fquickstart\n2. Make sure the Codex CLI is available, because Crack uses `codex exec` for planning, implementation, and conflict resolution.\n3. Finished. In theory. If not, congratulations: you have discovered software.\n\n## How It Works\n\nCrack does not run a daemon, background queue, or secret little scheduler hiding under your desk. Every workflow step happens inside the CLI command you run, and the source of truth is plain Markdown under `.crack\u002F`.\n\n```text\n.crack\u002F\n  inbox.md\n  pr-lock.md\n  plans\u002F\n    \u003Cplan-name>\u002F\n      plan.md\n      queue.md\n      log.md\n```\n\n### Branches\n\nWhen Crack creates a new Plan, it also prepares a branch. If you do not pass `--branch`, it turns the request title into a `codex\u002F\u003Cslug>` branch name.\n\n- If the branch already exists, Crack runs `git switch \u003Cbranch>`.\n- If it does not exist, Crack runs `git switch -c \u003Cbranch>`.\n- The Plan lives under `.crack\u002Fplans\u002F\u003Cname>\u002F`.\n- The real source branch is read back from the `Branch:` line in `plan.md`.\n\nThat last part matters: the Plan document is not decoration. It is the map. A tiny map, yes, but still a map.\n\n### Scheduling\n\nCrack's scheduling model is deliberately boring.\n\n- `submit` and `route` do not immediately implement code.\n- If `.crack\u002Fpr-lock.md` exists, new requests go to `inbox.md`.\n- If you pass `--plan \u003Cpath>`, the request goes to that Plan's `queue.md`.\n- If active Plans exist, the Router decides whether to attach the request to an existing Plan or create a new branch.\n- `run-next` executes one unfinished commit unit.\n- `run-all` repeats `run-next` until the Plan is complete or something returns `needs_work`.\n\nThe next commit unit is selected by comparing `### Commit N:` sections in `plan.md` with `Completed commit unit N` entries in `log.md`. This is not glamorous. It is also very easy to read at 2 a.m., which is a feature.\n\n### PR Locks\n\nRemote PR mode creates `.crack\u002Fpr-lock.md`. While that file exists, Crack pauses new Plan creation and stores incoming requests in `inbox.md`.\n\nThe lock is cleared when `crack pr-check` sees that the PR was merged, or when remote merge succeeds for the same branch. After that, `drain` routes queued inbox requests back through the Router one at a time.\n\n### Merge\n\nMerge only runs for a complete Plan. Crack checks `plan.md` and `log.md`; if any commit unit is unfinished, merge stops with `needs_work`.\n\nLocal merge switches to the target branch, merges the Plan branch, and records the result in `log.md`. Remote merge pushes the source branch, reuses or creates a PR, and runs `gh pr merge --merge`.\n\nIf a conflict appears, Crack calls a Merge agent whose job is intentionally narrow: resolve the current conflict, not redesign the feature, not rewrite the Plan, not suddenly become a product manager. If the conflict cannot be fully resolved, Crack stops with `merge_needs_work` and writes the reason to the Plan log.\n","Crack CLI 是一个为Codex设计的命令行工具，旨在作为Codex与其他代理交互的小型遥控器。其核心功能包括通过分散处理任务来解决Codex在单个上下文中考虑每一步骤导致的性能瓶颈问题，以及改善代码质量而不只是最小化修改现有代码库。此外，该工具允许用户像导演一样指挥Codex使用其他代理执行任务，而不仅仅是手动操作。Crack CLI适用于需要提高开发效率、优化代码质量和简化与多个软件代理协作的场景。此工具以TypeScript编写，支持GitHub CLI和Codex CLI集成，并通过Markdown文件管理计划和请求队列，确保工作流程透明可控。",2,"2026-06-11 04:00:50","CREATED_QUERY"]