I find this impressive: in my experience, codex-rs loves to add tests even when not prompted. Of course, it’s a bit of a crap shoot as to whether the test tests useful behavior.

(My favorite so far: it created an empty file in /home/whatever and added a test to verify that some code it wrote would indeed fail when tested on this empty input and that it would fail with the correct error message. Never mind that this covered approximately none of the desired behavior and that the test would, of course, fail on any other system.

That would be really interesting. I doubt it's the case, actually probably the opposite? The harnesses seem very happy to write extensive test suits, without me having to ask much.

And what would they test? This is a meaningless wrapper for Anthropic or OpenAI SDKs.

Yeah don’t understand. It’s a lot easier to just build your own.

I think the TypeScript ecosystem is more suitable for this.

I do not think Rust is a bad language. But the agent ecosystem changes very quickly, and in Rust, assembling and reshaping agent workflows is difficult.

Many people prefer Rust, and I understand why. It is a genuinely excellent language, and “Rust is a great language” is a strong message that attracts many developers. But as long as lifetimes exist, I think it will remain difficult.

The lifetime system assumes, in some sense, that humans can fully predict the lifecycle of values and resources. I am not sure that is truly possible in all domains. I am also not sure whether that model is linguistically suitable for the agent ecosystem.

In agent systems, requirements change constantly. Tools change, workflows change, providers change, schemas change, and failure policies change. In that kind of environment, I am not sure Rust is the right fit.

I like Rust a lot, and it is a language I genuinely want to learn. But I am not sure that applying Rust to everything is really the right answer.

I think Rust makes a lot of sense in relatively stable infrastructure ecosystems: operating systems, runtimes, sandboxes, and core low-level layers. But agent code usually requires high-level abstraction and rapid workflow composition. Doing that in Rust takes a tremendous amount of time.

I am using TS sandboxed in deno for all our agent code generated from a UI builder (inspired by OpenAI's own agent builder, and spits out the same code output)

Not ready for production yet but ive been working on https://wingman.actor for quite a while. Its a golang based portable agent runtime with minimal dependencies.

Uh... a flue is not a disease.

Mastra is a business, this seems to be a helpful lib

One big difference seems to be Mastra has tests and this project doesn't.

Why would I choose mastra over anthropic or cursor sdk ?

why not?

How would that actually work? Eventually the specification for the CPU has to be clear. For now, that means machine code.

What was offensive? Was it the use of Cloudflare? Or the way the import was written?

Anders Hejlsberg, who designed C#, is now leading Typescript development. Why would I not join him at the frontiers of his creative and intellectual energies?

Go is a nice language, but it's not expressive the way typescript can be. I'm not convinced, either, that coroutines are all that snazzy an abstraction at the application level.

ADK comes in Go, Java, Python, and TS

Same framework, multiple languages, let people decide their preference while having consistency and interoperability

Not mentioning Java means we are already on the same wavelength.

I love C# too.

You're welcome to port anything over to those languages. LLMs can do it in a couple of days at most.

Kotlin and Scala too if you want the same type of strong type system as TypeScript

One is stuck in 80s and another doesn’t even have official open source debugger, are you serious?