[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-81142":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":12,"openIssues":13,"contributorsCount":13,"subscribersCount":13,"size":13,"stars1d":13,"stars7d":13,"stars30d":13,"stars90d":13,"forks30d":13,"starsTrendScore":13,"compositeScore":14,"rankGlobal":9,"rankLanguage":9,"license":15,"archived":16,"fork":16,"defaultBranch":17,"hasWiki":16,"hasPages":16,"topics":18,"createdAt":9,"pushedAt":9,"updatedAt":19,"readmeContent":20,"aiSummary":21,"trendingCount":13,"starSnapshotCount":13,"syncStatus":22,"lastSyncTime":23,"discoverSource":24},81142,"codexloop","kunkunzhishan\u002Fcodexloop","kunkunzhishan","A local Codex CLI loop for longer tasks with planning, review, checklist state, and audit logs.",null,"JavaScript",31,1,0,0.9,"MIT License",false,"main",[],"2026-06-12 02:04:11","# CodexLoop\n\nCodexLoop is a local session console for longer Codex CLI work.\n\nGive it a goal, a workspace, and a loop budget. It keeps a checklist, reviews progress, chooses the next useful action, runs Codex, and shows you what changed. You can inspect the session at any time, steer it, approve or reject proposed work, and stop cleanly at a safe boundary.\n\nIt is meant for the messy middle: product slices, refactors, prototypes, game demos, agents, and tasks where you know the direction but do not want to hand-write every next step.\n\n## Why\n\nLong Codex tasks can drift. A single huge prompt is hard to monitor, hard to steer, and easy to finish with something that looks complete but skipped the real work.\n\nCodexLoop adds a lightweight control loop around Codex:\n\n- a living checklist for the current task;\n- a review step before choosing the next action;\n- visible progress cards after each loop;\n- a slash-command session where you can check status, steer, approve, reject, or quit;\n- local state and logs under `.agent2long` so the work is auditable.\n\nIt does not replace Codex. It gives Codex a longer-running, inspectable workspace.\n\n## Quick Start\n\nFrom this repository:\n\n```sh\nnode .\u002Fbin\u002Fcodexloop.js session \\\n  --workspace \u002Fpath\u002Fto\u002Fproject \\\n  --task \"Build the next useful product slice and verify it\" \\\n  --max-loops 12\n```\n\nIf installed as a package, use:\n\n```sh\ncodexloop session \\\n  --workspace \u002Fpath\u002Fto\u002Fproject \\\n  --task \"Build the next useful product slice and verify it\" \\\n  --max-loops 12\n```\n\nCodexLoop opens a persistent console:\n\n```text\ncodexloop\u002Fsession>\n```\n\nPlain text is ignored on purpose. Use slash commands so steering is explicit.\n\n## Common Commands\n\n```text\n\u002Fstatus\n\u002Fchecklist\n\u002Fdeferred\n\u002Fsteer Focus on a playable vertical slice before broad cleanup\n\u002Fquit\n\u002Fhelp\n```\n\nUseful commands:\n\n- `\u002Fstatus`: see the task, phase, loop count, current activity, current action, and last result.\n- `\u002Fchecklist`: show the full checklist tree.\n- `\u002Fdeferred`: show useful ideas that are not part of the active work.\n- `\u002Fsteer \u003Cinstruction>`: change direction without interrupting an Act already running.\n- `\u002Fquit`: stop cleanly at the next safe boundary.\n\n## Human Approval\n\nAdd `--approval` when you want to approve every Act before Codex edits the workspace:\n\n```sh\nnode .\u002Fbin\u002Fcodexloop.js session \\\n  --workspace \u002Fpath\u002Fto\u002Fproject \\\n  --task \"Improve the app without drifting into broad rewrites\" \\\n  --max-loops 12 \\\n  --approval\n```\n\nWhen approval is on, CodexLoop shows a proposed Act card. Then use:\n\n```text\n\u002Fapprove\n\u002Freject This is too small; combine it with the adjacent checklist item\n\u002Fsteer Build the first playable path before hardening edge cases\n```\n\n`\u002Fapprove` runs the proposed Act.\n\n`\u002Freject \u003Creason>` skips that Act and feeds your reason back into planning.\n\n`\u002Fsteer \u003Cinstruction>` during approval also rejects the current proposal, then uses your instruction to realign the checklist.\n\n## Continue Or Restart\n\nCodexLoop stores task state in the target workspace under `.agent2long`.\n\nBy default, it continues existing state:\n\n```sh\nnode .\u002Fbin\u002Fcodexloop.js session \\\n  --workspace \u002Fpath\u002Fto\u002Fproject \\\n  --task \"Continue improving the app\" \\\n  --max-loops 12\n```\n\nTo start a new task in the same workspace, use `--task-mode restart`:\n\n```sh\nnode .\u002Fbin\u002Fcodexloop.js session \\\n  --workspace \u002Fpath\u002Fto\u002Fproject \\\n  --task \"Build an AI narrative game with NPC agents and a living world\" \\\n  --max-loops 20 \\\n  --task-mode restart \\\n  --approval\n```\n\nRestart archives the old `.agent2long` state. It does not reset or delete your workspace code.\n\n## Funder Mode\n\nCodexLoop defaults to worker funder mode:\n\n```sh\nnode .\u002Fbin\u002Fcodexloop.js session \\\n  --workspace \u002Fpath\u002Fto\u002Fproject \\\n  --task \"Ship the current slice\" \\\n  --funder-mode worker\n```\n\nWorker funder reviews the current delivery, checklist, and previous Act result without actively searching for broad future opportunities.\n\nUse `--funder-mode founder` when you want the funder to actively discover or reconsider optimization ideas, including deferred ideas:\n\n```sh\nnode .\u002Fbin\u002Fcodexloop.js session \\\n  --workspace \u002Fpath\u002Fto\u002Fproject \\\n  --task \"Explore the product direction\" \\\n  --funder-mode founder\n```\n\n## What You See\n\nThe session prints simple text cards:\n\n- `Think`: the next action and checklist changes.\n- `Proposed Act`: what Codex wants to do before editing, when approval is on.\n- `Act Result`: changed files, verification, and blocker status.\n- `Realign`: checklist updates after steering or rejection.\n\nDuring a long Act, `\u002Fstatus` shows that the session is `acting`. CodexLoop does not interrupt Codex mid-edit unless you terminate the process yourself.\n\nUse `\u002Fquit` for a clean stop. It waits for the current boundary so state and logs can be written.\n\n## Installation\n\nPrerequisites:\n\n- Node.js 20+\n- Codex CLI installed and authenticated\n\nClone the repo, then run:\n\n```sh\nnpm test\nnode .\u002Fbin\u002Fcodexloop.js --help\n```\n\nThe package exposes both `codexloop` and the older `agent2long` command name when installed as a package.\n\n## Permissions\n\nDuring Act, CodexLoop runs Codex with workspace-write\u002Ffull execution permissions:\n\n```sh\ncodex exec --cd \u003Cworkspace> --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check\n```\n\nUse it only on workspaces where Codex is allowed to read and edit files.\n\nCodexLoop redacts common API key and token patterns before writing its own control files, but you should still avoid putting secrets directly in task text when possible.\n\n## Good Fits\n\nCodexLoop is useful for:\n\n- long tasks that need multiple coding passes;\n- rough goals where Codex should discover the next step;\n- projects where you want a checklist and audit trail;\n- work that benefits from review before the next action;\n- experiments with autonomous Codex workflows.\n\nFor tiny one-file fixes, plain Codex CLI is usually enough.\n\n## Status\n\nCodexLoop is early and experimental. The current focus is making longer Codex sessions easier to inspect, steer, and stop cleanly.\n\nFeedback and experiments are welcome.\n\n## License\n\nMIT\n","CodexLoop 是一个用于执行较长任务的本地 Codex CLI 控制台。它通过规划、审查、检查列表状态和审计日志等功能，帮助用户管理复杂的编码任务。项目采用 JavaScript 编写，提供了一个轻量级的控制循环来保持任务清单的实时更新，在每次循环后进行进度审查，并在每个循环结束时显示进度卡片。此外，它还支持通过命令行界面直接与会话交互，包括查看状态、调整方向或终止任务等操作。CodexLoop 适用于需要长时间运行且涉及多个步骤的任务场景，如产品切片开发、代码重构、原型设计等，尤其适合那些已有明确目标但不希望手动编写每一步骤的情况。",2,"2026-06-11 04:03:40","CREATED_QUERY"]