Comment by cpursley

3 months ago

A came here just to write: Pretty please let it churn for a few nights and redo Claude Code in Rust. Because the harness is very very good as are their models, but that node thing is a hog for no good reason at all.

5 comments

cpursley

Reply
canadiantim  3 months ago

People already rebuilt Claude Code in Rust after the Claude Code leak, it's on github as claw code (and other variants)

jcarver  3 months ago

[dead]

  • rytill  3 months ago

    I checked out your agent and it looks pretty well designed. Congrats on starting to share it with others!

    One thing I noticed: "Your Tools: Aether agents get tools exclusively via MCP servers." "...Aether ships with 1st-party MCPs for file system operations..."

    Can you share your thoughts on why you decided to use MCP as the core tool abstraction? I have heard many decry MCP as being context-wasteful. Is this not the case with your agent?

    • jcarver  3 months ago

      Great question.

      The MCP protocol has gotten a bad rap for wasting context due to most MCP clients dumping tool definitions directly into context, which is wasteful.

      Aether doesn’t do that. It uses an opt-in "proxy" that puts MCP tool schemas on the filesystem so the agent can browse, search and load the tool schemas it needs progressively. As for motivation there's several advantages to taking a MCP 1st approach, including:

      1. It allows Aether to be a truly blank slate agent as 0 tools are hardcoded into the core runtime.

      2. It allows users to extend Aether using any language they want

      3. MCP gives a standard way to deal with local+remote tools, progress notifications, permission prompts (e.g. ask the user to allow/deny a tool call), OAuth flows etc.

      4. There's a big ecosystem of existing MCP servers users can connect to

      But that's all optional, you can just as easily give Aether a single Bash tool and only use CLIs too.