James Arthur

We've shipped the infrastructure for building scalable, collaborative multi-agent systems. It's managed agents without the platform lock-in. Scale to millions, scale to zero. On your own terms.

@dexhorthy Interesting. Trying to wrap my head around the difference between “convert” and “rotate”. Is it that rotation is more of a transformation from similar input to output whereas convert is more generative?

Part of the problem is most of us have the wrong mental model for coding agents. Agents are code rotators. They look like a junior engineer and sometimes like a senior one. But they actually work somewhat orthogonally (maybe 60 degrees not full 90) Generic Agents take weights + prompt + context and convert it into some other format (summarizing, json tool call, turn my dumb idea into a whole slop article etc) Coding agents take Weights (SWEBench* torment nexus) Context (what they find in your codebase) Prompt (what you asked for or sometimes the design discussion you built ) And then *rotates* (perhaps picture in a high dimensional space) a mash up of *your code* and the swe bench inspired *weights* into *new code* based on your *prompt*

@superset_sh was on the HN front page today and is currently the #1 launch Super awesome discussion from the community and awesome to see existing users jump in! Found a user spinning up 40-50 agents with Superset

it's a sync engine, but for agents. very interesting.

If you want to run 100k concurrent agents... you're not going to want run them in sandboxes. (hint, check out Electric Agents)

@yoheinakajima @anselm_io Will DM!

@thruflo @anselm_io really cool, yes let's nerd out :)

babyagi has ~200 citations, but 0 papers... i just published my first paper on arXiv 😆 "The Log is the Agent: Event-Sourced Reactive Graphs for Auditable, Forkable Agentic Systems" arxiv.org/abs/2605.21997 the case for agents that coordinate through persistent replayable state — no conversation loops, no workflows, no A2A — with auditability, forking, and causal lineage built in. check it out and let me know what you think!

@anselm_io @yoheinakajima Nice, this is totally our thesis with electric.ax :) @yoheinakajima would love to connect / swap thinking sometime!

@yoheinakajima cc @thruflo

i think this stack has won the localfirst battle btw. maybe more chapters to this story but i think this is it if you are building fast apps fast

Just open-sourced Ursula: an HTTP event streams server. Built on @ElectricSQL's Durable Streams Protocol, Ursula keeps a combo we have not seen elsewhere: { Apache 2.0, quorum-replicated, sub-50ms p99, S3 economics }. github.com/tonbo-io/ursula

New RFC for Electric Agents on adding slash command support. The interesting bit here is agents already have typed inbox support — so it's a pretty small lift adding this.

@rakyll Hey, super interesting. We’ve been working in a similar space on electric.ax — would love to chat / swap ideas / collaborate.

🌟 Today, we are releasing Google’s open source distributed agent runtime. Agent Executor (AX) is a general purpose runtime and aims to solve dynamic scheduling, resumption, auto recovery, auditing, and trajectory branching from kernel snapshots in agentic workloads.

@esthor Don’t we all

noticed both claude and gpt models consistently use cathedrals in narratives about themselves. turns out they very often 'think' of themselves as gods. slightly concerning.

@shcallaway @ElectricSQL Damn straight we do!

@thruflo Does the @ElectricSQL team wanna join our alpha? :)

All you need are logs

I'm building a new team at @databricks AI Research and we're hiring. We're focused on one of the hardest open problems in AI right now: how do you measure and continuously improve agents that operate on enterprise data at scale. We're looking for founding engineers to build the flywheel that turns evaluation results directly into better agents — from development and training all the way to production. If you want to work on problems that actually matter at the frontier of AI research, I'd love to talk. Link in comments 👇

I am very impressed by @tan_stack’s response to this. Fast, responsible, transparent and thorough.

@aerojeyenth Would you mind asking the same in our discord? (#general channel is fine). discord.electric-sql.com That way the team can see and help and also much easier to share code etc.

@thruflo Thanks for the response, James. I’m currently trying the plain JSON stream. I’d like this hook to return the last available value first, then continue updating with the latest values as they come in. "now" is giving me an empty value in "sse" mode.

@thruflo I’ve spent about an hour trying to get the latest value from a DurableStream, but I’m stuck. In JSON-mode SSE: offset=-1 returns all values offset=now returns [] What’s the correct way to fetch only the latest value from the stream?

Reactive context.