Open Source Radar — September 19: agents get a spec layer
Today's daily trending board is three-quarters skills and plugins, and the three things that actually broke through are all fixes for the same complaint: the agent does the work, but nothing holds the plan, the context, or the tooling in place. One project makes specs the unit of work, one makes memory a service you can self-host, and one hands an agent your trading charts.
OpenSpec (TypeScript, ~62,000 stars, MIT) — Spec-driven development, packaged as a framework rather than a manifesto. Instead of asking a coding assistant to write a feature straight from a prompt, OpenSpec has the agent draft a proposal, requirements with concrete scenarios, a technical design, and an implementation checklist as plain Markdown in the repo — then you approve the plan before any code lands. It is built for brownfield work, which is the part most spec frameworks skip: the change lives in a folder, gets applied task by task, and is archived with the specs updated, so the repo accumulates a record of what was decided and why. Worth trying on a codebase where the assistant keeps "helpfully" rewriting things you didn't ask it to touch.
Supermemory (TypeScript, ~29,000 stars, MIT) — A memory and context engine that claims the top spot on LongMemEval, LoCoMo, and ConvoMem, the three benchmarks that matter for agent memory, with 95% recall at 15 retrieved items and a reported 99.4% context reduction. The pitch is the whole stack in one system: it extracts facts from conversations, maintains a user profile, resolves contradictions and expired facts, and serves hybrid search that mixes knowledge-base retrieval with personalized context. It runs fully local, ships connectors for Drive, Gmail, Notion, OneDrive, and GitHub, and handles PDFs, images, and code. If you have been gluing a vector store to a summary table and calling it memory, this is the category doing it properly.
TradingView MCP (JavaScript, ~5,900 stars, license: custom) — An MCP bridge that connects a coding agent to the TradingView Desktop app already running on your machine, over Chrome DevTools Protocol. It reads and drives your own charts — analysis, Pine Script development, repetitive chart work — and the README is unusually blunt about what it is not: not affiliated with TradingView, not a paywall bypass, requires a valid subscription and the desktop app, and it does not place trades. Because it drives undocumented internal interfaces, a TradingView update can break it without warning. That caveat is the honest part, and it is also why the fork count is nearly half the star count — people are already building on it.
Worth watching this week: whether OpenSpec's artifact-first flow survives contact with real deadlines, and whether Supermemory's benchmark numbers hold up outside its own harness.
Do you want your agent to plan before it codes, or do you find the spec layer just slows it down? Tell us in the comments.
Sources: OpenSpec (GitHub) · OpenSpec · Supermemory (GitHub) · Supermemory docs · TradingView MCP (GitHub)
