I’m Nate, the founder of Ardent. We just shipped our public beta, and we’d love your thoughts! Ardent is an agent running in a desktop (Electron) app built to help with knowledge work, designed for less-technical people outside engineering. Think Codex or Claude Cowork, but built around collaboration and customization. I know, I know, it’s yet another agent harness! Ardent is a little different – it leans heavily on codegen to solve problems. Most agents are basically just a bag of tools and a while loop, but Ardent writes code to complete tasks, making it much faster and more token-efficient. [0] Lots of companies are trying to build their own agent harness right now, because token budgets make software appear cheap, and it seems like a competitive advantage to own a custom agent. The thing is, agents are deceptively complex. They aren’t light wrappers around the model anymore; the harness makes a big difference in how capable the agent is. They also come with lots of sticky problems: context management, sandboxing and permissions, authz/authn to remote services, etc. Instead of building your own harness from scratch, you can customize Ardent using abilities: TypeScript libraries that can expose tools and prompts which can be used by the agent. They’re like agent skills, but closer to regular code libraries: type-safe, importable, and with well-defined permissions. Ardent can help you build abilities, but you can also create them by hand if you prefer. Anyone can share abilities with everyone in their organization with a single click, and if Ardent notices that the user is doing repeatable work, it offers to transform the adhoc solution into a reusable ability. Say you prepare the same project update every Friday, pulling issues from Linear and docs from Google Drive. Ardent can turn that workflow into a reusable ability that you can share with everyone in your company. Your company’s ability catalog is like a standard library. To solve a problem, Ardent searches for existing abilities, and then writes glue code to compose them. Because the code is ephemeral, it doesn’t need to be maintainable, which lets us use cheaper, less-capable open weight models like Kimi and GLM. [1] Code executes on the user’s machine in a Deno sandbox with zero permissions by default. Abilities declare required permissions up front, and any code that exceeds the current scope gets terminated and prompts the user for approval. Ardent can also connect to a bunch of tools which you’re already using, like Google, Linear, and so on. We support MCP servers, but in our experience, MCP is slow, token-expensive, and provides a pretty bad experience for both agents and users. [2] Instead, Ardent connectors handle auth, but instead of using MCP, we generate client shims which call the service’s primary API. This is a much better fit for Ardent’s codegen approach, because the agent can read the client and treat it like any other library. There’s a bunch of other interesting stuff in Ardent: memory, conversational recall, scheduled tasks, prompt suggestions, and so on. During our beta period, we’re selling inference at-cost, and we’re giving each organization some free credits to experiment. Please take a look and tell us what you think! We’d love your feedback, whether you think what we’re doing is good, bad, or meh. I’m also happy to answer any questions that you might have. --- [0] Cloudflare has taken to calling this “code mode”: https://blog.cloudflare.com/code-mode/ [1] In our benchmarks, Ardent consumed 63% fewer tokens than Opus running in Claude Cowork, with half the model requests. [2] MCP servers rarely define input/output contracts, and it’s hard to write code that calls a function when you don’t know its arguments, or even its arity! Here's a good read on the subject: https://www.blacksmith.sh/blog/code-smith-code-mode |