ellmer
ellmer stopped being a chat wrapper and started shipping the parts production LLM code needs
A side-by-side editorial comparison of AutoGPT and btw — release velocity, themes, recent moves, and the top alternatives to consider.
AutoGPT is building a workforce: experts now get schedules, credits, and their own briefings.
The last three releases all advance one idea. v0.7.0 split the Copilot into experts with scoped sessions, identity context and a marketplace, on a rebuilt Better Auth foundation. v0.7.1 gives those experts schedules — attribution, triggers, thread posts and a credit guardrail — plus editable Soul documents, collapsible expert chat groups in the sidebar, and a briefing-first home built around a morning briefing and unified needs-attention view. Tavily search/extract/crawl/map blocks and Claude Sonnet 5 support land in the same release. Underneath, v0.6.69 had already taught the copilot bot to post into Slack and Telegram unprompted.
btw is turning into an agentic R harness that no longer needs you to be in R
btw assembles context about an R session — packages, documentation, files, data frames — and hands it to an LLM through ellmer, with btw_app() as a chat interface. Over the last year it has grown well past context assembly: LLMs can document, check, test and measure coverage of a package, read CLAUDE.md and AGENTS.md as project context, fetch skills from packages or GitHub, and inspect the source of any installed namespace. Much of this is now reachable from a terminal CLI rather than only from an R prompt.
The last three releases all advance one idea. v0.7.0 split the Copilot into experts with scoped sessions, identity context and a marketplace, on a rebuilt Better Auth foundation. v0.7.1 gives those experts schedules — attribution, triggers, thread posts and a credit guardrail — plus editable Soul documents, collapsible expert chat groups in the sidebar, and a briefing-first home built around a morning briefing and unified needs-attention view. Tavily search/extract/crawl/map blocks and Claude Sonnet 5 support land in the same release. Underneath, v0.6.69 had already taught the copilot bot to post into Slack and Telegram unprompted.
The platform is converging on persistent, scheduled, individually-billed agents that report back rather than wait to be asked. Scheduling with a credit guardrail is the piece that makes that economically safe; Soul documents are the piece that makes each expert configurable by its owner. The briefing-first home is the consumption side of the same design — the user opens to what the agents did overnight. Release cadence is roughly weekly and the contributor list is small and consistent.
Given scheduling, credit guardrails and a marketplace now coexist, per-expert monetisation or publishing by outside authors is the obvious next step. The Soul document format is also likely to grow structure.
btw assembles context about an R session — packages, documentation, files, data frames — and hands it to an LLM through ellmer, with btw_app() as a chat interface. Over the last year it has grown well past context assembly: LLMs can document, check, test and measure coverage of a package, read CLAUDE.md and AGENTS.md as project context, fetch skills from packages or GitHub, and inspect the source of any installed namespace. Much of this is now reachable from a terminal CLI rather than only from an R prompt.
The direction is from describing a session to operating on it, and from inside R to outside it. Each release adds either a tool group that lets a model do something (document, check, test, cover; read namespace source; fetch skill resources) or a CLI command that removes the need to start R first. The 1.2.0 tool renaming — session becoming sessioninfo, search becoming cran, files_read_text_file becoming files_read — reads as the naming cleanup you do when you expect a lot more tools to follow.
The CLI has been absorbing one tool family per release (skills, then pkg desc and pkg src) while the R-side tool groups stay ahead of it, so the next releases likely continue exposing existing tool groups as terminal commands rather than adding new capabilities.
Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either AutoGPT or btw.
ellmer stopped being a chat wrapper and started shipping the parts production LLM code needs
tfevents logs TensorBoard events from R, and this release only changes who maintains it.
safetensors for R changes hands with no code change to show for it.
torchdatasets ships custodial work as mlverse gathers its torch satellites under one maintainer.
A curated catalogue of published hyperparameter search spaces, now reaching deep neural networks
Hyperband tuning for mlr3, now built on an asynchronous backend it treats as mandatory
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. AutoGPT is currently shipping more aggressively (velocity 7.5 vs 2.5), with 2 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. AutoGPT is currently shipping more aggressively (velocity 7.5 vs 2.5), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
Top AutoGPT alternatives in ai-assistants are ranked by recent ship velocity. Browse the "AutoGPT alternatives" section above for the current picks, or visit /alternatives/autogpt for the full list with editorial commentary on each.
Top btw alternatives in ai-assistants are ranked by recent ship velocity. Browse the "btw alternatives" section above for the current picks, or visit /alternatives/btw-r for the full list with editorial commentary on each.