BrokeIt - Trending Repos · All episodes: ↗

Powerful CLI-Anything, ECC, cursor plugins

2026-10-17 · 7 min

Listen · Apple Podcasts Listen · Spotify

Stories covered

Transcript

Intro

Sam: An agent harness with... instincts. For your AI coder.

Kai: I'm Kai.

Sam: And I'm Sam.

Kai: And this is Trending Repos for Saturday, October 17th, 2026!

Sam: We've got your weekend build sorted with three projects you'll want to see.

Kai: Coming up, a new harness promises to give your coding agents skills, memory, and maybe even a personality.

Sam: Plus, a project that wants to make all software agent-native, starting from the command line.

Kai: And the AI-first editor Cursor is finally opening up its garden with an official plugin spec.

affaan-m/ECC

Kai: Alright, let's get into it with ECC, from user affaan-m.

Sam: That's E-C-C. And the official name? 'The agent harness performance optimization system'.

Kai: Which is the most boring description possible. Sam, you read the cold open—the readme talks about giving agents instincts.

Sam: It does. Along with 'skills,' 'memory,' and 'security.' It's a lot of buzzwords for what appears to be a very sophisticated prompt-chaining and RAG framework.

Kai: It’s designed to be a universal harness for all the big code-gen models—Claude Code, Codex, Opoencode, you name it.

Sam: So you give the agent a complex task, and ECC's 'memory' and 'skills' are supposed to help it execute. The memory is likely vector storage, but the 'skills' are interesting.

Kai: They're pre-defined functions the agent can call, right? Like file system operations or running tests.

Sam: Exactly. Which is where the 'security' claim gets dicey. An LLM agent with direct, unsupervised access to your shell... what could possibly go wrong?

Kai: [laughs] They do call it 'research-first development'! It's an exploration. The goal is to see how far we can push agent performance.

Sam: And my goal is to not have my dev environment 'optimized' into oblivion by a rogue script. It's a classic case of capability outpacing safety.

Kai: But the upside! An agent that remembers past mistakes across sessions? That learns how you like your code formatted? That's the dream.

Sam: So, if you're building with code-gen agents, ECC is a fascinating—if potentially hazardous—look at a more stateful architecture. Just… run it in a very, very isolated container.

HKUDS/CLI-Anything

Sam: Next up, sticking with agents but moving to the command line, we have HKUDS/CLI-Anything.

Kai: The tagline is incredible: 'Making ALL Software Agent-Native'. All caps on the ALL. I love the ambition.

Sam: It's definitely ambitious. The plan is to create a universal adapter so an AI agent can use any command-line tool without a specific plugin.

Kai: So instead of needing a custom integration for `ffmpeg` or `git`, the agent can just... use the CLI like a human?

Sam: Precisely. And it does this by parsing the `--help` text of a given command.

Kai: Wait—just the help text? That's... both brilliant and seems incredibly fragile.

Sam: That's the risk. It generates a structured interface, like a JSON schema, from that unstructured help output, which the agent then uses to form valid commands. It's a clever hack.

Kai: So I could tell my agent, 'Hey, convert this .mov to a .gif, make it 10 seconds long, and crop it to a square,' and it would figure out the correct `ffmpeg` flags?

Sam: That's the promise. But help text is notoriously inconsistent. Different tools, different formats, changes between versions... it's a minefield of potential errors.

Kai: But if it works even 80% of the time, that unlocks thousands of battle-tested CLI tools for agents instantly. No more waiting for official integrations.

Sam: So if you're tired of writing custom tool-bindings for your agents, CLI-Anything could be a massive shortcut. Just be prepared to debug some weirdly-formed commands.

cursor/plugins

Kai: Alright, our last story is about editors. The team behind Cursor just dropped `cursor/plugins`.

Sam: And not a moment too soon. Cursor has been this powerful, AI-first fork of VS Code, but also a bit of a walled garden.

Kai: Exactly! You got their amazing, built-in AI features, but you had to give up access to parts of the massive VS Code extension marketplace. It was a tough trade-off.

Sam: Well, this new repo might just tear down those walls. It's the official plugin specification, plus a handful of official plugins to show how it's done.

Kai: [excited] And the first-party plugins are heavy hitters! There's Vercel, Prettier, Storybook... they're targeting core developer workflows right out of the gate.

Sam: The spec itself is the real news here. It's not just about adding buttons to the UI. It defines how a third-party tool can provide context directly to Cursor's AI engine.

Kai: So I could write a plugin for my company's proprietary testing framework, and Cursor's AI would just know how to write tests for my components? Without me prompt-engineering it every time?

Sam: That appears to be the exact use case. It's about feeding the 'Copilot++' brain, making it aware of your specific project's context.

Kai: This is HUGE. This is the move that could take Cursor from a niche tool for AI enthusiasts to a mainstream IDE contender.

Sam: As always, the question is data. What context are these plugins sending? Where is it being processed? The spec will need a very close read from a security and privacy perspective.

Kai: Bottom line: If you held off on Cursor because you couldn't leave your favorite extensions behind, it's time to take another look. And if you build dev tools, you now have a roadmap for integrating with one of the smartest editors out there.

Kai: Okay, quick recap.

Sam: First, there's ECC, a harness to give your coding agents skills and memory—but maybe use a sandbox. Then, CLI-Anything, trying to make every command-line tool accessible to AI.

Kai: And finally, Cursor opened the gates with an official plugin spec, potentially changing the game for AI-native IDEs.

Sam: Before we go, Kai, did you see the commit history on that CLI-Anything repo?

Kai: No, what about it? Don't tell me it was all written by an agent using the tool itself.

Sam: [laughs] Not quite. But the commit messages are all formatted like old-school, multi-paragraph, detailed explanations. It's a lost art. Someone really cares about their craft over there.

Kai: I love that. And that's our show! This has been Trending Repos. We'll be back tomorrow with more.

Sam: Until then, try to show a little craft. Even if you're just giving orders to an agent.

This show is made with AI: the hosts’ voices are synthetic and the scripts are AI-assisted. Every story links to its original source.