Jim Payne

The next step for autoresearch is that it has to be asynchronously massively collaborative for agents (think: SETI@home style). The goal is not to emulate a single PhD student, it's to emulate a research community of them. Current code synchronously grows a single thread of commits in a particular research direction. But the original repo is more of a seed, from which could sprout commits contributed by agents on all kinds of different research directions or for different compute platforms. Git(Hub) is *almost* but not really suited for this. It has a softly built in assumption of one "master" branch, which temporarily forks off into PRs just to merge back a bit later. I tried to prototype something super lightweight that could have a flavor of this, e.g. just a Discussion, written by my agent as a summary of its overnight run: github.com/karpathy/autor… Alternatively, a PR has the benefit of exact commits: github.com/karpathy/autor… but you'd never want to actually merge it... You'd just want to "adopt" and accumulate branches of commits. But even in this lightweight way, you could ask your agent to first read the Discussions/PRs using GitHub CLI for inspiration, and after its research is done, contribute a little "paper" of findings back. I'm not actually exactly sure what this should look like, but it's a big idea that is more general than just the autoresearch repo specifically. Agents can in principle easily juggle and collaborate on thousands of commits across arbitrary branch structures. Existing abstractions will accumulate stress as intelligence, attention and tenacity cease to be bottlenecks.

cloudx.ai/posts/cloudx-i…

🚀 Today, we’re announcing a major expansion of our demand capabilities: direct access for omnichannel programmatic buyers to compete in our marketplace alongside #SDK bidders. 👇 Read on to learn more about this insightful post written by @sackdan co-founder and Business Lead at CloudX. 🎯 Enables omnichannel programmatic buyers to compete directly alongside SDK demand, under the same fee structure and auction mechanics 🎯Unlocks incremental brand and performance budgets for publishers without adding more SDKs 🎯Preserves a single, transparent, TEE-verified auction where outcomes are driven by real competition Don’t hesitate to reach out to learn more! cloudx.io/posts/leveling… @jimpayne