{"full_name":"KKKKhazix/agent-autoloop","owner":"KKKKhazix","name":"agent-autoloop","url":"https://github.com/KKKKhazix/agent-autoloop","description":"让你的命令行 Agent 在后台自己接活、自己跟进到底；平时不烦你，遇到拿不准的事才发卡片找你拍板。","homepage":"","topics":[],"language":"TypeScript","license":"MIT","avatar":"https://avatars.githubusercontent.com/u/239590580?u=e36ff439fc89c0ec6eff33f6d1d5e869ce0b214f&v=4","created_at":"2026-11-03T08:02:11Z","pushed_at":"2026-11-10T09:21:57Z","metrics":{"stars":4375,"forks":797,"watchers":7,"issues":30,"prs":170,"releases":13,"issues_open":null,"issues_closed":null,"prs_open":null,"prs_closed":null,"prs_merged":null,"discussions":1},"growth":{"day":{"stars":164,"forks":32,"base_day":"2026-11-09"}},"history":{"dates":["2026-11-05","2026-11-09","2026-11-10"],"stars":[2423,4211,4375],"forks":[485,765,797],"watchers":[8,7,7],"issues_open":[null,null,null],"prs_open":[null,null,null]},"boards":{"weekly":70,"daily_rate":54,"weekly_rate":6,"monthly_rate":44,"new":162},"same_owner":[{"full_name":"KKKKhazix/AIHOT","name":"AIHOT","boards":{"daily":151,"weekly":126,"monthly":112,"daily_rate":71,"weekly_rate":35,"monthly_rate":37,"new":46}},{"full_name":"KKKKhazix/human-writing","name":"human-writing","boards":{}}],"issues":[],"discussions":[{"number":136,"title":"Chinese deep-dive review: agent-autoloop — recoverable CLI task loops","comments":0,"category":"Show and tell","created_at":"2026-11-05T19:03:23Z"}],"latest_release":{"name":"Agent Autoloop 1.6.4","tag":"v1.6.4","published_at":"2026-11-08T01:20:15Z","body":"来源能查到自己发出的事件后来怎么样了；`status` 在终端里彩色分区显示；修好 Windows 自带 Administrator 账号、保留端口和短路径目录上的几处问题。旧规则、旧插件不用改。\n\n- **来源查事件结果。** 来源发完事件，用同一把密钥 `GET /v1/events/<应答里的 event>` 就能查到它被哪些规则接了、每一轮现在什么状态（在跑、没跑成、等重试、被停、不再重试）和最后的结论。只查得到这个来源自己从门口发进来的事件，中台代它记的（回执发出的、手动运行、卡片回答、到期复查）和别的来源的都返回 404。\n- **`status` 更好读。** 在终端里按颜色和分区排：总数、在线、等你、正在做、最近几轮、最近的卡片、定时、没有规则接的事件。新加“正在做”，写清已跑多久、因为什么开始。接管道、被 Agent 调用、设了 `NO_COLOR` 时仍是纯文本，`--json` 不变。\n- **Windows：自带的 Administrator 账号不再以管理员权限常驻。** 开着 UAC 的自带 Administrator 账号，登录任务照样会拿到完整权限。现在 `service install` 发现这种情况会撤掉任务，并打印一行命令，改由「启动」文件夹以普通权限拉起；建不了任务时也打印这一行。\n- **Windows：数据目录在 8.3 短名路径下不再崩。** Node 24.16 起，中台监视规则文件时，短名目录里一有改动就会退出；现在监视前先展开成完整路径。\n- **Windows：端口落在系统保留范围时说清楚。** 报 `listen EACCES` 时提示怎么用 `netsh` 查、`config.json` 改哪几处；`service install` 等不到中台应答时打出 `up.log` 的最后几行。\n\n感谢 Jecvay、youngzs 的报告。\n\n---\n\nSources can look up what became of the events they sent; `status` is colored and sectioned in a terminal; fixes for Windows' built-in Administrator account, reserved ports and 8.3 short paths. Existing rules and plugins work unchanged.\n\n- **Sources can check an event's outcome.** With the same key, `GET /v1/events/<event from the response>` shows which rules took the event, the state of each run (running, failed, waiting to retry, stopped, given up) and the final summary. A source only sees events it sent through the front door; events the hub records in its name (from receipts, manual runs, card answers, scheduled rechecks) and other sources' events return 404.\n- **`status` is easier to read.** In a terminal it is colored and grouped: totals, online, waiting on you, in progress, recent runs, recent cards, schedules, events no rule took. The new \"in progress\" section shows how long each run has been going and what started it. Piped output, agent calls and `NO_COLOR` still get plain text; `--json` is unchanged.\n- **Windows: the built-in Administrator account no longer keeps the hub elevated.** With UAC on, that account got a full token even from the limited logon task. `service install` now detects this, removes the task and prints one line that starts the hub from the Startup folder at normal rights instead; it prints the same line when the task cannot be created.\n- **Windows: a data folder under an 8.3 short path no longer crashes.** From Node 24.16, watching a short-name folder exits on the first change; the path is expanded before watching.\n- **Windows: reserved ports are explained.** `listen EACCES` now points to the `netsh` check and the `config.json` settings to change; when `service install` gets no answer from the hub it prints the last lines of `up.log`.\n\nThanks to Jecvay and youngzs for the reports.\n"},"readme":true,"readme_zh":false,"news":[{"title":"SNSのノイズを消す。直近7日間で世界のエンジニアが支持した「一次情報・CUI回帰」ツール4選（実数値データ）","url":"https://note.com/coinearn/n/n5a4f0df36a31","source":"note","lang":"zh","date":"2026-11-09"},{"title":"agent-autoloop の注意点は？ 入れる前に見る4つ","url":"https://note.com/s_kashiwakura/n/nfb1b2858b394","source":"note","lang":"zh","date":"2026-11-05"},{"title":"别再守着终端了：Agent Autoloop 让 Claude Code、Codex 在后台自己接活、跟进到底的完整入门指南","url":"https://blog.csdn.net/gitblog_00979/article/details/170140701","source":"blog.csdn","lang":"zh","date":"2026-11-05"},{"title":"一条命令装完就能跑：Agent Autoloop 快速上手教程，10分钟完成第一次提问、拍板到干完","url":"https://blog.csdn.net/gitblog_00857/article/details/170137939","source":"blog.csdn","lang":"zh","date":"2026-11-05"},{"title":"卡兹克开源一年成果Agent-Autoloop自动化系统","url":"https://www.sohu.com/a/1096878075_122066678","source":"搜狐","lang":"zh","date":"2026-11-04"},{"title":"开源我这折腾了1年的「Agent自动化系统」，愿所有人都能感受Agent的魅力","url":"https://news.qq.com/rain/a/20261104A03C5F00","source":"腾讯网","lang":"zh","date":"2026-11-04"},{"title":"ALGOIT | AI News & How-Tos","url":"https://x.com/ai_algoit/status/2118158231252115638","source":"x","lang":"en","date":"2026-11-04"}],"stale":false,"snapshot_at":"2026-11-10T09:35:25Z","history_start":"2026-09-06"}