Work items the owner has requested, taken in order, highest first.
Every item is standing: none is ever closed, and every section keeps being built out and re-verified indefinitely.
The owner edits this file to steer the section; agents append ? for tom: bullets and work the items, and never mark one done, strike it through, or remove it.
- Build the research index (standing) - create research notes per the AGENTS.md format, one category at a time, each category seeded with the tools practitioners actually meet. Seed categories, in rough order:
- Harnesses: Claude Code, Codex, Gemini CLI/Antigravity, OpenCode, aider, Crush, Amp, Junie.
- Surfaces: Cursor, VS Code + Copilot, Windsurf, JetBrains/Junie, Zed.
- Orchestration: parallel-agent dashboards and worktree managers (Conductor, dmux, Emdash, and neighbors).
- Protocols: MCP, ACP, AGENTS.md, A2A.
- Context engines: code search and context packing for agents.
- Skills: skill formats, registries, and marketplaces.
- Retrieval: RAG patterns and tooling for code and knowledge bases.
- Memory: agent memory systems, from file-based notes to knowledge graphs and session archives.
- Executions: scheduled and event-based agent runs (cron-style tasks, triggers, webhooks).
- Hybrid execution: deterministic components orchestrating LLM steps for intelligence and structured outputs (tool calling, schema/JSON outputs, validation and retry loops).
- People and publications: the people and websites shaping the domain (Karpathy, swyx/Latent Space, Willison, Yegge, Orosz/Pragmatic Engineer).
Standing work already under way (still open; keep updating and extending each indefinitely):
- Agentic coding tools landscape - started 2026-08-22, published as agentic-coding-tools-landscape; it is the essay layer over the harness/surface/orchestration notes, so keep cross-linking new notes and re-verifying it indefinitely.
- Model selection for coding tasks - started 2026-08-24, published as model-selection-for-coding-tasks; keep folding in new models and price moves indefinitely.
- Context management patterns - started 2026-08-24, published as context-management-patterns; keep re-grounding its patterns in new harness documentation indefinitely.
- People and publications category - seeded 2026-08-29, with the companion people-and-publications-feature-matrix; keep scanning for and adding new voices and publications indefinitely, not only when prompted.
? for tom: The 2026-10-01 banned-term sweep reworded “real” section headings in the main corpus but left this section’s roughly 330 “real” uses (mostly “real-world” compounds and contrastive uses like “adoption is real, stability is not”) in place, and the daily verification has been treating them as the most-appropriate-term exceptions since. Should the section get the same rewording treatment, or is the corpus-only scope the intent? Rewording at this scale needs its own directed run with Changes bullets per touched note, so I have not done it inside a daily refresh.
? for tom: The sandboxing refresh flagged that E2B, the hosted sandbox API the category’s notes already cite as a standing comparison baseline, has never been profiled as a note of its own. Add it to the sandboxing category (it would clear the citation bar easily), or does it stay comparison-only?
? for tom: Following up on the “real” question above: the skills-library banned-terms list now also bans “real” (and “load-bearing”) as of 2026-10-06, while this section’s AGENTS.md still lists only shape/honest/load bearing and the roughly 334 retained uses remain under the documented-exceptions treatment. Confirm and a directed run will reword them with per-note Changes bullets.
? for tom: The retrieval entrant scan rejected Haystack (26.7k stars, active) because the category’s founding scope carries exactly two frameworks and a third framework column is a scope call, not an entrant signal. Should retrieval add Haystack as a third framework column, or does the two-framework scope stand?
? for tom: The trackers scan rejected METR’s time-horizon series as a tracker (a single trend series, not a leaderboard) but flagged it as a possible people-and-publications voice (an evals nonprofit publishing original measurement research). Should METR be profiled in people and publications?
? for tom: The evaluation awesome-list cross-check surfaced Opik (comet-ml/opik, 22.4k stars, Apache-2.0, active) as an uncovered observability-and-eval platform between the category’s two existing columns in adoption (Langfuse 35.5k, Phoenix 11.7k), with promptfoo (25.8k) as a second eval framework next to deepeval and AgentOps (5.9k, quiet since June) the weaker sibling. I rejected all three as scope calls under the retrieval Haystack precedent. Should evaluation-review add a third observability column (Opik), a second eval-framework column (promptfoo), or stand at the current structure?
? for tom: The orchestration framework family now covers the multi-agent systems (CAMEL, AG2, AutoGen, AutoGPT, CrewAI, Agno, Dify, Mastra, LangGraph, and more), and the cross-category scan surfaced the single-vendor agent-building SDKs (openai-agents-python 29.9k, smolagents 29.7k, google adk-python 21.7k, semantic-kernel 28.6k, strands 8.7k, claude-agent-sdk 8.2k). I rejected them as SDKs for building agents rather than multi-agent orchestration systems, a family rejection recorded in the log. Should any of them get orchestration columns anyway?
? for tom: Today’s one new star is p-e-w/heretic (33.8k stars, fully automatic censorship removal for model weights). It fits none of the 23 categories (it modifies models rather than providing access or running agents), so it is logged as out-of-scope. Should model-modification tooling have a home in the section, or does the rejection stand?
? for tom: Three mega-viral repositories surfaced with no clean category: garrytan/gstack (135.6k stars, Garry Tan’s personal Claude Code setup as 23 opinionated agent tools), JuliusBrussee/caveman (110.3k, a skill-plus-proxy claiming 65 percent token cuts by removing articles), and Panniantong/Agent-Reach (92.9k, a CLI giving agents read and search over Twitter, Reddit, YouTube, GitHub, and Bilibili). Profile any of them (skills, context engines, or retrieval would be the nearest homes), or do personal bundles and viral novelty stay out?
? for tom: The people-and-publications scan keeps passing over vendor engineering blogs (Anthropic Engineering, OpenAI’s harness-engineering write-ups) because the category has only admitted independent or practitioner-owned publications. Should a vendor engineering blog be admissible as a voice, or does that stay out of scope?
? for tom: The skills scan surfaced scale records above every prior pack rejection: K-Dense-AI/scientific-agent-skills (47.8k stars, 177 validated science skills), cathrynlavery/diagram-design (44.3k), EveryInc/compound-engineering-plugin (25.4k), and anthropics/claude-plugins-official (37.5k, the vendor-official plugin directory). The standing exclusion covers single skills and packs and vendor in-product directories. Do skills-scale records like these change the policy, or does the formats/registries/marketplaces scope stand?
? for tom: openai/symphony (27.6k stars, Apache-2.0, quiet since September 15) turns project work into isolated autonomous implementation runs, squarely the orchestration category’s subject, and I logged it with the mission-control tail as a family rejection rather than writing it amid today’s 45 notes. Want it profiled next run?
? for tom: The 2026-10-10 scan surfaced tinyhumansai/openhuman (41,802 stars, pushed 2026-10-11, added to both orchestrator directories this week): a Rust library plus desktop harness with built-in memory, token compression, and tool search. It is assistant-runtime-shaped and would sit 2.4x above leon (17.6k), the absorbed family’s largest named rejection, but at OpenClaw-class scale. Profile it, or does the family rejection hold at this scale?
? for tom: GCWing/OpenBitFun (2,412 stars, active, MIT) was rejected from surfaces as a general-purpose Cowork-style agent workspace whose coding support is one mode among several, which reads as assistant-runtime-shaped; but admitting it as a fourth Cowork desktop would re-litigate the standing absorbed-family rejection from the same run. Which shelf (or rejection) stands?
? for tom: Four categories acquired their first credible dedicated awesome lists this run and AGENTS.md changes are yours: yibie/awesome-jev (2,255 stars, hybrid execution), varun1505/awesome-software-factories (17 stars but on-subject and active, software factory), webfuse-com/awesome-autoresearch (2,563 stars, automated research), and walkinglabs/awesome-harness-engineering (4,368 stars, harnesses). Wire any or all into the category-source list?
? for tom: The skills scan surfaced yusufkaraaslan/Skill_Seekers (15,118 stars, active, doc-to-skill converter): a generator kind the category has never admitted, standing beside the formats, registries, and marketplaces scope. Admit the generator kind, or does the standing scope hold?
? for tom: The retrieval family boundaries turned away three scaled tools this run under standing precedents: CocoIndex (11.7k, active, Apache-2.0) under the pathway data-infrastructure rejection, Crawl4AI (85.1k, active) under the Firecrawl crawler rejection, and DSPy (38.6k, active) under the framework family of the still-open Haystack question. Do any of the three deserve their own columns, or do the family scopes stand?
? for tom: The AMO directory’s source-of-truth file (src/data/orchestrators.ts) holds roughly a dozen slugs with no README rendering (ctx, open-agent-relay, agent-coordinator, meshfleet, commonground-kernel, speakeasy-mcp-gateway, agentrq, hyper, and friends) that predate the 2026-10-07 cross-check, which walked the README rendering rather than the data file; the 10-07 “all 67 entries” count was the README’s. Want a directed run to walk the ts-only slugs once?
? for tom: The evaluation-review scan keeps resolving a security-testing cluster the category has never admitted: AgentFence (61 stars, quiet since August), AgentDojo (906 stars, ETH Zurich, quiet since June), and the stronger garak and DeepTeam that a first admission would then owe, all judging attack robustness rather than generated output. Should evaluation-review add a security-evaluation family, or does the output-judging scope stand?
? for tom: The skills pack-scale records grew again today: addyosmani/agent-skills at 105,086 stars and mattpocock/skills at 286,377 stars (both above the 47.8k K-Dense figure in the standing question), and morluto/rea (“REA Reverse Engineer Anything”, 109,906 stars, a 768-point Hacker News launch) resolved as harnesses-kind and held under the same pack exclusion with a skills routing flag. Do any of these change the pack policy, or does the formats/registries/marketplaces scope stand?
? for tom: kodustech/awesome-ai-code-review (49 stars, no license, maintained by Kodus, stale since 2026-06-28) is the only dedicated awesome list the code-review category has ever acquired, but it is vendor-run and stale. Wire it into the category-source list, or does code-review stay on the broad sources?
? for tom: The harnesses wiring question has a name collision: walkinglabs/awesome-harness-engineering (4,373 stars) has been stale since 2026-08-19, while ai-boost/awesome-harness-engineering (4,786 stars, pushed 2026-10-10) is the list you starred on 2026-04-26. If the harnesses list gets wired at all, which one is the intended target?
? for tom: The single-repository star-history chart convention (from your 2026-10-07 note) lives only in log history, not in agents/AGENTS.md, and three waves of workers missed it today before a repair pass added 18 charts. Codify it in the Article format section (one line), or retire the convention? (done 2026-10-12: codified in the Article format section at your direction.)
? for tom: Today’s only new star is TomzxCode/agentic (your own task-and-worktree manager for agent work, public 2026-10-10, 1 star, 0 forks, MIT, ACP harness runs). I rejected it as a note on the citation bar: no third-party footprint, five sources unreachable without counting the repository against itself, and profiling the section owner’s own tool at zero adoption reads like an advertisement. Re-review trigger recorded on independent adoption or third-party coverage. Want an owner-tools exception (disclosed ownership, bar still applied), or does the rejection stand?
? for tom: The browser-automation family keeps scaling past the section (browser-use 117,786 stars, stagehand 25,653, skyvern 23,190, steel-browser 7,791, ClawBench 1,026), and no category covers browser control; the 2026-10-13 scan class-rejected them with the nearest shelf (hybrid execution via cua-s1) judged a whole-family admission. Leave them out of scope, or open a browser-automation family?
? for tom: Update to the OpenBitFun shelf question above: a second same-profile candidate now exists, Orkas (Orkas-AI/Orkas, 2,188 stars, MIT, active, surfaced by the slavak source 2026-10-16), a desktop commander directing sub-agents and coding CLIs, held 2026-10-16 under the same absorbed cowork-desktop family pending your call on that shelf.
? for tom: Update to the autoresearch wiring question above: a second candidate list now exists, WecoAI/awesome-autoresearch (about 1,069 stars, use-case focused), beside webfuse-com/awesome-autoresearch (2,565). Wire either, both, or neither?
? for tom: The executions category acquired its first credible dedicated list sighting: serenakeyitan/awesome-agent-loops (214 stars, CC-BY-4.0, /loop-/goal-/schedule recipes for Claude Code and Codex), on-subject but stale since 2026-06-22 and a recipe collection rather than a tool list. Wire it into the category-source list with the staleness caveat, or leave executions on the broad sources?
? for tom: The trackers category’s nearest scaled list is onejune2018/Awesome-LLM-Eval (659 stars, MIT, eval tools, papers, and leaderboards), but it is stale since 2025-11-24 and academic-eval-focused. Wire it with the staleness caveat, or leave trackers-and-leaderboards on the broad sources?
? for tom: Update to the autoresearch wiring question above: two more dedicated lists surfaced this run, openags/Awesome-AI-Scientist-Papers (176 stars, pushed 2026-10-12, paper links) and Omni-Scientist/Awesome-AI-Scientist (109 stars, pushed 2026-10-07), both report-only while q#26 stands beside the webfuse-com and WecoAI candidates.
? for tom: The sandboxing refresh found the E2B question above already resolved on disk: E2B has held a full note and matrix column in sandboxing since 2026-10-06 (Added bullet dated in the category index). Confirm and treat q#2 as answered, or say what remains open about it.
? for tom: Update to the openhuman question above (q#13): tinyhumansai/openhuman repositioned from “personal AI super intelligence” to “the fastest, cheapest, most efficient open-source agent harness” (fleet-scale Rust framing, GPL-3.0, 42.1k stars as of 2026-10-17), and its README now carries a self-run SWE-bench comparison table against Claude Code, Codex, OpenClaw, and Hermes Agent, the vendor-benchmark pattern this section discounts; still zero independent coverage, so the absorbed-family hold stands, but the harness framing may matter to whichever shelf you pick.
? for tom: The skills-library banned-terms list also names “posture” (as of the 2026-10 list), while this section’s AGENTS.md bans only shape/honest/load bearing; the section carries two uses, both in thesis lines (claude-code-action’s “security posture” and claude-code-routines’s “default posture”). Want a directed pass to reword both with per-note Changes bullets, or does the section’s three-term list stay the section rule?
? for tom: Update to the code-review wiring question above (q#21): a second candidate now exists, zhuyansen/awesome-claude-code-review (created 2026-10-10, pushed 2026-10-17, refreshed every 8 hours, 185 categorized repos with security grades, plus an original 16-tool end-to-end eval with a public results file, but 1 star and run by the Agent Skills Hub site). It supersedes the stale kodustech list on every axis but age and starred history. Wire it (with the 1-star caveat), wire neither, or stay on broad sources?
? for tom: Update to the harnesses wiring question above (q#22): a third kind of candidate now exists, Gloriaameng/Awesome-Agent-Harness (372 stars, CC-BY-4.0, pushed 2026-10-14), the companion list to an “Agent Harness for LLM Agents” survey (168 references, 34 systems) rather than a maintained tool directory, and three more same-named awesome-harness-engineering lists (7, 2, and 4 stars) deepen the name collision. Wire the survey companion, any of the name-collision lists, or none?
? for tom: The memory category now has a second credible dedicated list: IAAR-Shanghai/Awesome-AI-Memory (1,281 stars, created 2025-12-01, pushed daily), a broad AI-memory knowledge base spanning research, frameworks, benchmarks, and practice, beside the wired TeleAI-UAGI list. Wire it as a second source, or stay single-source?
? for tom: The assistant-runtimes category acquired its first credible dedicated list: machinae/awesome-claws (506 stars, updated 2026-10-19, 34 projects, mostly the absorbed claw-family tail). Wire it as a category source (its tail resolves under the standing family rejection), or leave assistant-runtimes on the broad sources?
? for tom: IronClaw (nearai/ironclaw, 12,662 stars, pushed 2026-10-18) surfaced on that list as a claw successor held under the absorbed runtime family, but it sits above the member floor (Octop about 9.2k) and beside the openhuman scale call (q#13). Does the family rejection hold at IronClaw’s scale, or does it join the q#13 ruling?
? for tom: The context-engines category found a second credible dedicated list: yzfly/awesome-context-engineering (213 stars, created 2025-07-28, pushed 2026-10-15), beside the wired Meirtz list. Wire it as a second source, or stay single-source? (Wiring would surface roughly ten in-category candidates for resolution in that run.)
? for tom: Update to the memory second-source question above: the IAAR-Shanghai/Awesome-AI-Memory scan recommends wiring it scoped to its open-source-systems and benchmarks sections only (the 19k-line papers section is high-volume and low-yield for tool notes), which would surface roughly eight non-member candidates (langmem, memobase, MIRIX, ReMe, MemoryOS, EverMemOS, Memori, Memary) for resolution in that run.
? for tom: Today’s token-reduction pass scripted the coordinator mechanics inside agents/worklists/: worker reports now go to /tmp/opencode/agent-reports/## Pricing section the note-format order names (individuals and free publications where pricing does not apply, and the format says notes whose Pricing says pricing does not apply get no price history, not that they can drop the section). Add “does not apply” stubs to the 15 with per-note Changes bullets, or amend the section’s format note so people notes may omit Pricing?
? for tom: Route cuga-project/cuga-agent (CUGA, IBM’s enterprise generalist agent harness, 1,045 stars, Apache-2.0): rejected by harnesses as not coding-harness kind (web/API automation surfaces, AppWorld/WebArena benchmarks, no repository loop) and by control-planes as not a plane. Admit it under assistant-runtimes, hold it out of scope, or extend the harnesses charter to generalist (non-coding) agent harnesses?
? for tom: The control-planes category found a second dedicated list: systempromptio/awesome-ai-agent-governance (52 stars, pushed 2026-10-19, detailed entries), but it is vendor-run (systemprompt.io’s own products fill several sections). Wire it as a second source with the vendor-run caveat, or stay on agentrust-io/awesome-ai-governance alone?
? for tom: Update to the autoresearch wiring question above (q#26): the candidate set now also holds yibie/awesome-autoresearch (784 stars, pushed 2026-10-18, structured categories, active) and AI4Scientist/awesome-autoresearch (170 stars, well-taxed taxonomy list), beside webfuse-com (2,565), WecoAI (1,069), and the two report-only paper lists. Wire any of them?
? for tom: The task-management scan surfaced two dedicated lists owned by other categories, both report-only: kyrolabs/awesome-ade (Agentic Development Environments, created 2026-08-07, nearest homes harnesses or surfaces) and bradAGI/awesome-cli-coding-agents (1,383 stars, updated 2026-10-19, nearest home harnesses). Wire either as a mapped source, or do those categories stay on the broad sources?
? for tom: TypeChat’s rejection reopens on a first tagged release or npm publication; GitHub still shows neither, but the npm typechat package (latest 0.1.4, published 2026-08-21, repository field pointing at microsoft/TypeChat) predates the 2026-10-13 revival push, so should that npm line count as the trigger or must a revival-era publication do it?
? for tom: q#14 evidence refreshed 2026-10-22, OpenBitFun (GCWing/OpenBitFun, MIT core, Rust runtime plus Tauri desktop app, created 2026-02-02, 3,029 stars and 276 forks, v1.0.7 on October 21, zero HN stories) still self-describes as an agent workspace “not a single-purpose AI editor” with Code, Cowork, and Claw pillars and a Mini Apps marketplace, but the Code side is IDE-grade (integrated editor, terminal, Git views, code review, language intelligence, SSH/Docker/WSL remote workspaces, ACP external agents, external-source discovery from OpenCode, Claude Code, and Codex), so both the rejection-holds reading (general-purpose workspace per the 2026-10-10 ruling) and a surfaces admission (more coding-native than tambo, bb/Cate/Codeg-class) have live evidence, and the fork is coding-support-present versus coding-first-framed
? for tom: the q11/q20 skills-scale records keep compounding while the pack policy waits: mattpocock/skills crossed 300k stars (300,191 on 2026-10-22, up from the 286k recorded 2026-10-13), and skills.sh’s leaderboard now shows one publisher (heygen-com/hyperframes) holding four of the top fourteen install rows.
? for tom: two more skills-scale records surfaced above everything named in q#11/q#20: multica-ai/andrej-karpathy-skills (222,124 stars) and tt-a1i/archify (87,285 stars); they ride the same open pack-policy question.
? for tom: q26 wiring input: webfuse-com/awesome-autoresearch (2,574 stars, pushed 2026-09-21) and WecoAI/awesome-autoresearch are both live dedicated lists; this run scanned the webfuse list report-only and admitted AutoKernel from it; wiring one as the category’s dedicated source would give the daily scan a direct feed.
? for tom: the webfuse-com/awesome-autoresearch scan routed five agent benchmarks (openai/mle-bench, THUDM/AgentBench, snap-stanford/MLAgentBench, gersteinlab/ML-Bench, chchenhui/mlrbench) to evaluation-review per the new routing line; should evaluation-review add an agent-benchmarks family, or do benchmark repositories stay pointers as in the model-benchmark-matrix ruling?
? for tom: Update to the people-notes Pricing question above: three rotation fixes this run (armin-ronacher, indydevdan, owain-lewis gained Pricing sections with fetched prices and Price history rows) leave 14 notes without the section, and several of them sell products (Pocock’s courses, Ball’s Amp, Horthy’s HumanLayer workspace, Beck’s paid Substack tier), so filling them means per-note price fetches rather than does-not-apply stubs; fill them in rotation, or amend the format note so people notes may omit Pricing?
? for tom: Update to the code-review wiring question above (q#21): the kodustech list was scanned report-only this run, stale since 2026-06-28 with dead, 404, and 1-star entries at HEAD; its one live entrant, Nayjest/Gito (452 stars, MIT PR reviewer for any provider), was admitted to code-review directly. Keep the category on the broad sources, or wire the list anyway with the staleness caveat?
? for tom: the h2o-lightning-4b note is scoped to the 4B checkpoint while the family’s new 31B v1.0.7 now leads the JevBench board at 84.3; keep the note 4B-scoped with the 31B as ecosystem evidence, or widen it to the H2O-Lightning family?
? for tom: Chon-1.0-12B held the JevBench capability lead for about a day before method v1.7’s 10-second rule dropped it to rank 30; index one-liners naming capability leaders now carry the protocol revision (method-v1.7 board) rather than a bare date, confirm that reading
? for tom: the jev-model GitHub topic page surfaced as a cheap standing entrant source for hybrid-execution (small jev-like repositories under one page); category source lists are yours to wire, so should it join the AGENTS.md source list?
? for tom: rotation passes that verify a note clean append no Changes bullet, so the worklist’s last-verified date never moves and the same note heads every rotation until something material changes (lars-faye has repeated this way since 2026-10-07); should a clean full rotation pass record itself (a verification marker the generator reads, or a permitted no-op Changes bullet), or does the repeated re-verification stay the intended cost?
? for tom: q#11/q#20 evidence point: the rea.tools scale record (morluto/rea) read 387,014 stars on 2026-10-26, up from the 109.9k recorded 2026-10-13 and past mattpocock/skills at 286k as the largest known record; does this change the pack-policy hold?
? for tom: q#14 (OpenBitFun shelf) looks closable: the 2026-10-27 re-read still self-describes a general-purpose agent workspace with a Mini App marketplace, so the Cowork-style rejection holds; it is growing (3,286 stars as of 2026-10-27, active daily), so say the word if you want it profiled anyway
? for tom: q#13 evidence refreshed 2026-10-28: openhuman stands at 42,378 stars, up only about 180 in the week since 10-21, against OpenClaw’s 393k, so the OpenClaw-class scale trigger as framed has not fired; openhuman stays on the absorbed-family shelf unless you rule otherwise.
? for tom: q#26 wiring input: both candidate autoresearch lists are unchanged since their last checks (webfuse-com pushed 2026-09-21, WecoAI pushed 2026-07-30). This run scanned WecoAI’s list report-only: its non-member entries resolved onto standing families except evo-hq/evo, admitted today. The WecoAI list skews to personal ports and benchmarks, the webfuse list to papers and benchmarks; wiring either would formalize the feed, neither keeps the current carry-over checks.
? for tom: is the multi-agent framework tier closed (CrewAI, AutoGPT, AutoGen, Dify as the admitted set) or can active peer frameworks earn columns? swarms 7.3k, agency-swarm 4.6k, and langroid 4.1k were rejected below the tier’s adoption this run, while ChatDev 34.6k (active 2.0) was handed to orchestration as note-worthy
? for tom: the 2023-24 dormant-wave line is now holding large coding tools (gpt-pilot 33k, plandex 15.8k, sweep 7.7k); keep the uniform rejection or carve a dormant-harness exception for tools engineers still run
? for tom: q#85 (agent-benchmarks family) now has an in-category anchor pair, MLR-Bench and ResearchClawBench; a third research-agent benchmark admission would make the family call concrete
? for tom: elyase/awesome-personal-ai-assistants (21 stars) is the first dedicated assistant-runtime list found; too small to map as the category source, but its full scan yielded LangBot and the largest claw-family tail yet (IronClaw 12.7k). Map it as the category’s dedicated source, or keep it a one-off scan?
? for tom: nearai/ironclaw (12.7k stars, WASM-sandboxed assistant from NEAR AI) is the largest member ever held on the absorbed-family shelf; keep it there, or should its sandboxing-first design get a sandboxing-category look?
? for tom: q#26 update - the dedicated-source check found yenanjing/awesome-ai-for-science (12 stars, 502 entries, updated 2026-10-29) as a candidate third autoresearch list beside the two already in the question; say whether to wire any of them as this category’s mapped source, or leave the broad sources to carry the category
? for tom: fold Google’s 2026-11-13 retrievable-usage billing rule (Gemini 4 completions over 32K tokens billed even when the request times out) into the model selection guide’s hidden-details list?
? for tom: q#26 re-check 2026-10-29, wiring data for the autoresearch-list question: four credible lists now exist. webfuse-com/awesome-autoresearch (2,578 stars, unchanged since 2026-09-21, carries over from the 2026-10-23 scan, its tail resolved on standing families), yibie/awesome-autoresearch (790 stars, pushed 2026-10-28, 424 repo links, 21 overlap this category’s membership, tail dominated by the single-harness personal ports the 2026-10-23 ruling rejects), WecoAI/awesome-autoresearch (1,074 stars, unchanged since 2026-07-30, 25 links, 4 member matches, a vendor use-case list), AI4Scientist/awesome-autoresearch (181 stars, pushed 2026-10-28, functional taxonomy, 15 member matches, best signal-to-noise of the four). Worker read: AI4Scientist is the one worth wiring as the dedicated source, webfuse-com carries, yibie and WecoAI stay unwired; the call is yours.
? for tom: the executions work list carried no rotation slice this run (the generated YAML names members and signals but no rotation section), so I derived the two oldest from last_verified dates (trigger-dev 10-24, codex-action 10-25 cohort with the oldest full re-verify at 10-20); confirm that derivation matches the generator’s intent
? for tom: q5 (METR as a voice) update: The Batch issue 377 (2026-10-30) cites METR’s OpenAI/Hugging Face incident investigation (2026-08-26) as the primary source on agent swarming, a second high-profile agent-era publication; if that counts as coverage-window evidence, the q5 rejection premise (“tracker rejection”) deserves a fresh look.
? for tom: the orchestration member Superset renamed its repository and product to Paradev (ParadevAI/Paradev, the old path redirects, README headlines “Paradev (formerly Superset)”); the note records the rename under the Superset title. Retitle the note and slug to Paradev, or keep the founding name as with the agentmeasure/Verovo pivot question above?
? for tom: q#14 (OpenBitFun shelf) reads closable: the 2026-10-31 re-check found the same general-purpose agent workspace pitch (four harness modes, cross-device remote control, Mini App marketplace, 3,423 stars, growing) with coding beside it, so the Cowork-style workspace rejection stands; close unless you want a periodic growth watch.
? for tom: q24 evidence refresh 2026-10-31: no independent adoption or third-party coverage surfaced for TomzxCode/agentic (repository search returns only the repo itself, HN search zero); the rejection stands unless you grant the owner-tools exception.
? for tom: q26 update - the “two autoresearch lists” framing undercounts the field; seven dedicated autoresearch lists now exist (webfuse-com 2,579 stars, handsome-rich 1,262, WecoAI 1,075, yibie 792, AI4Scientist 183, MinhaoXiong 126, SUSTech-GenAI 58), six of them with no digest record; name the set to wire or keep riding the broad sources.
? for tom: should Verovo (formerly AgentMeasure) keep its session-analytics seat now that v0.10.0’s headline is buyer-side charge and delivery verification, or move when a release drops the coding-agent diagnostics lane entirely?
? for tom: wire kyrolabs/awesome-ade as the orchestration dedicated mapped source (judged credible 2026-11-01 at 25 stars with 18 member entries and active pushes; the wiring run must walk its back catalog per the 2026-10-25 carry-over lesson), or leave orchestration on kaushikb11 plus the broad sources?
? for tom: portofcontext/pctx (282 stars, MIT, active, Block’s goose listed as a user) converts agent tools and MCP servers into Deno-sandboxed code execution; all four candidate categories declined it on kind (sandboxing, protocols, executions, hybrid-execution). Should a Code-Mode tool-execution substrate get a home in the section, or does the out-of-scope closure stand?
? for tom: (2026-11-05) the model selection guide and provider matrix cover seven model providers, and xAI is not one of them. Today xAI’s flagship grok-4.7 lists at $2/$6 under a 200K prompt ($4/$12 past it, 500K context) and its coding-oriented grok-build-0.1 at $1/$2 (256K context), both under the converged workhorse rate the guide treats as the decision anchor. Add an eighth xAI column, or hold the seven-provider scope and record the exclusion as a standing decision?
? for tom: (2026-11-05) the AI4Scientist/awesome-autoresearch walk surfaced four major open deep-research agents (deer-flow 85k, Tongyi DeepResearch 20k, RD-Agent 15.2k, open_deep_research 12.7k) against a member tier of three (gpt-researcher 30.1k, local-deep-research 9.2k, the OpenAI product): does the deep-research tier gate admissions the way orchestration’s same-kind line does, or does each major agent earn a note?
? for tom: (2026-11-05) map the decision-model dedicated sources into hybrid-execution’s scan set (AnotiaWang/awesome-decision-models, andyrewlee/awesome-system-one, ckaraca/awesome-jev) or rule which are scan sources versus ecosystem-evidence watchers
? for tom: close q#14 (OpenBitFun): five re-reads (2026-10-27, 10-31, 11-04, and this run) found the same self-described general-purpose agent workspace with a Mini App marketplace, now at GCWing/OpenBitFun and 3,720 stars; the Cowork-style rejection is stable and the governing-question loop can stop re-firing
? for tom: does a knowledge-work skill runtime get a home (LazyMind, LazyAGI/LazyMind, 612 stars, self-hosted desktop plus enterprise service that exposes skills, workflows, and artifacts to Codex and DeepSeek Harness), or does the no-claiming-category hold stand as it did for pctx (q8-family)?
? for tom: hybrid-execution found its first credible dedicated list: andyrewlee/awesome-system-one (48 stars, pushed 2026-11-05, web version at system-one-models.com, maintained by the awesome-agent-orchestrators maintainer), carrying a large unprofiled decision-model wave (Chon-1.0-12B, mammoth-1, Cloudflare’s Clef family, Liquid AI’s d1 line, and more). Wire it as the category’s mapped source (its wave resolves once mapped), or leave hybrid-execution on the broad sources?
? for tom: q#85 (agent-benchmarks family) now has a second parked candidate, MemPABench (on-policy personal-agent memory benchmark, 2 stars, routed from the memory source), beside SGI-Bench; the ruling decides whether benchmark-pointer members join evaluation-review or route by the object they judge (MemPABench’s judged object is agent memory behavior, so memory may be the better home if pointers are admitted)
? for tom: the task-management worker’s link check found three main-corpus files outside agents/ carrying internal links to targets that do not exist on disk (CI fails on these): about/index.md links ../questions/index.md (the section holds only _index.md), global-sessions-a-git-model-for-llm-agent-context/index.md links ../the-agentic-development-environment-landscape/index.md (that article lives only under agents/), and llm-agents-learning-without-a-reward-signal/index.md links ../metrics-for-a-software-factory/index.md (no index.md in the directory); fix, retarget, or say which reading stands
? for tom: two candidate sources surfaced outside their owning categories’ mapped lists: cuihuan/awesome-ai-gateway (148 stars, active daily, 240+ gateways) for model-access’s dedicated-source check, and mahmoudsajjadi/awesome-ai-coding-tools (15 stars, three-tier coding-tools taxonomy) as an additional broad source beside ai-for-developers; wire either?