Making AI agents for non-technical teams @nullshotai. They do the real work, you stay in control. First up: Reddit. Prev @earnalliance, @kintohub, Junglee.
Hong Kong
Joined November 2011
- Tweets8.1K
- Following1.6K
- Followers8.2K
- Likes18.1K
I submitted gitstalk as my open source submission to Cloudflare Github for Agents competition 4 minutes before the deadline 😅
I didn't have much time to edit the video, but I'm happy with the results:
- 6-9x faster features merged compared to Merge Queues
- Merge queues is an enterprise feature, so small biz likely are 20-30x slower at agent scale on Github.
- Ask questions with Clef. "Who and what changed with coupons in the last week?"
- 100% Github Actions Supported! Running on cloudflare workers.
- Introduce Github Actions running on Dynamic Workers for lightweight tasks.
- 456 Commits and almost 2 million LOC in 2 weeks
- It's purely running on Cloudflare with no 3rd party dependencies: Email, Workers, In Memory Cache, Edge Caching, Durable Objects, D1 SQL, Artifacts (git storage), Domain Purchasing + Hosting, Unified AI Gateway, Rate Limit Service, R2 Buckets, Analytics Engine, Secrets, Containers, && Observability / Traces
- The docs has all my published research on what worked, and what didn't.
The open source link is in the comments below.
Results are in, Scion helps a lot of agents work together, but didn't improve my submission to Cloudflare tonight
What it is improving is distributed code to agents, so once I have 100+ agents coding, I'm sure its code will work therefore, I'm keeping the changes in the official release.
Due to Cloudflare's requirements, the initial version will be released as Apache 2.0 - anyone can enjoy the billions of tokens spent on this one.
The docs have all the research and ideas, failures and wins, for everyone to learn from.
My submission for the @Cloudflare @CloudflareDev Github competition is due in ~36 hours.
Anthropic shares their 30K per day process and I went ahead to see how far "off" we are from that.
I'm about 80% there and going to implement and test hopefully before submission time
My submission for the @Cloudflare @CloudflareDev Github competition is due in ~36 hours.
Anthropic shares their 30K per day process and I went ahead to see how far "off" we are from that.
I'm about 80% there and going to implement and test hopefully before submission time
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
We are now up to 900% faster at shipping features. The breakthrough being:
Inform and Sync active work that does not conflict in realtime.
This is all done without any harness, pure claude code and git APIs. Optional plugin to enrich context for better collaboration.
Submission t-minus 8 days.
Opening public website Monday for feedback @CloudflareDev @Cloudflare #GitHub Competition
Early results from my Cloudflare submission:
- 55% Faster merges than batch merges in Github.
- Agents <> PRs = Intents that automate dep management
- Built for always on, always living, agents. If there's an idea, or a bug, it's on it.
- Humans are notified when agents cannot decide how to proceed with parallel conflicting ideas.
- Tested with 50+ parallel agents, 300+ features shipped.
I hope the humans are ready to keep up with my take on the future of git.
Most founders pivot too early.
Got a rule: every new idea goes in the back pocket for three months before I do anything with it. Most of them die on their own. The ones that survive are usually worth chasing.
