Comments URL: https://news.ycombinator.com/item?id=47445805

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=47400851

Points: 3

# Comments: 0

sandbox-profiles is a solid primitive for local agents. The missing piece in production is the tool layer — even a sandboxed agent can still make dangerous API calls if the MCP tools it has access to aren't individually authed and scoped.

The real stack is: sandbox the runtime (what Agent Safehouse does) + scope the tools (what we do with JIT OAuth at the MCP layer). Neither alone is enough.

Nice work shipping this.

https://www.arcade.dev/blog/ai-agent-auth-challenges-develop...

Growing up as an integration engineer, I built my career religiously reading the Enterprise Integration Patterns book from Gregor Hohpe. Content-Based Router, Dead Letter Channel, Claim Check these weren't just patterns, they were how I thought about systems. That book shaped an entire generation of us who built middleware, ESBs, and messaging infrastructure.

Two decades later, I found myself staring at a eerily familiar set of problems but with a completely different consumer. Not applications. Not services. AI agents.

It's been an exciting and one-of-its-kind experience working with the Arcade tool engineering team to extract implementation patterns from 7,000+ production tools. Especially Evan Tahler Renato Byrro & Francisco Liberal

54 patterns across 10 categories, so everyone building tools and MCP servers can ship higher quality tools for their agents.

A couple things that make this practical:

Every pattern downloads as a flash card. Drop them into your architecture decks, design reviews, team workshops.

Every pattern exports as markdown / llms.txt for your IDE.

The workflow: point your coding agent at one or more patterns and say "build an MCP server for this API."

The pattern becomes your implementation spec.

Blog: https://blog.arcade.dev/mcp-tool-patterns

Full catalog: https://arcade.dev/patterns

Comments URL: https://news.ycombinator.com/item?id=46954615

Points: 3

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=46657947

Points: 5

# Comments: 1

For a start, now have llms.txt to aid models while developing nerd programs.

https://www.nerd-lang.org/llms.txt

Eg:

Write a function that adds two numbers and returns the result Use https://nerd-lang.org/llms.txt for syntax.

Considering their experience, this saves them time to think beyond coding. :)

Comments URL: https://news.ycombinator.com/item?id=46471097

Points: 1

# Comments: 1

On New Year's Eve I announced NERD - a language built for LLMs, not for human authorship. The response was unexpectedly overwhelming. Questions, excitement, discussions, roasting - all of it.

But one question struck me: "What use case is this language built for?"

Fair. Instead of a general-purpose language covering all features - some of which may not even be relevant because we're not building apps the old way anymore - I picked one: agent-first.

What this means - you can now run an agent in NERD with one line of code:

-- Nerd code llm claude "What is Cloudflare Workers?"

No imports. No boilerplate. No framework.

The insight from working with agents and MCP: tools are absorbing integration complexity. Auth, retries, rate limiting - all moving into tool providers. What's left for agents? Orchestration.

And orchestration doesn't need much: → LLM calls → Tool calls → Control flow → That's it.

Every language today - Python, TypeScript, Java - was built for something else, then repurposed for agents. NERD starts from agents.

Fully story here: https://www.nerd-lang.org/agent-first

Do jump in to contribute, these are amazing thoughts.

40% of code is now machine-written. That number's only going up. So I spent some weekends asking: what would an intermediate language look like if we stopped pretending humans are the authors?

NERD is the experiment.

Bootstrap compiler works, compiles to native via LLVM. It's rough, probably wrong in interesting ways, but it runs. Could be a terrible idea. Could be onto something. Either way, it was a fun rabbit hole.

Contributors welcome if this seems interesting to you - early stage, lots to figure out: https://github.com/Nerd-Lang/nerd-lang-core

Happy to chat about design decisions or argue about whether this makes any sense at all.