Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

SpaceXAI engineer Lingxi Li, Lingxi Li, runs code cleanup while everyone else is asleep. Nobody is shipping at 3 AM, so conflicts are rare and the changes are low risk. His bots start a research agent that sweeps the monorepo for quality issues, poor modularization, comment bloat and security...

1,002,200 Aufrufe • vor 14 Tagen •via X (Twitter)

22 Kommentare

Profilbild von Arthur MacWaters
Arthur MacWatersvor 14 Tagen

@lingxi @lingxi is the goat, great guy also

Profilbild von Mike Melgarejo
Mike Melgarejovor 14 Tagen

@lingxi a special mind

Profilbild von tetsuo
tetsuovor 14 Tagen

@lingxi Facts.

Profilbild von Merdog
Merdogvor 14 Tagen

@lingxi So dis bro is da one shipping in the middle of my grinds Bahahha

Profilbild von John Bai
John Baivor 14 Tagen

@lingxi bro is agi

Profilbild von arclight industries
arclight industriesvor 14 Tagen

@lingxi Real G's move in silence

Profilbild von Evan Bacon 🥓
Evan Bacon 🥓vor 14 Tagen

@lingxi Lingxi is an absolute pro 💪

Profilbild von decipherx
decipherxvor 14 Tagen

@lingxi give every overnight cleanup a kill switch. if tests miss a behavior change, the first engineer online should be able to revert the whole batch before reading the summary

Profilbild von Devin Soto
Devin Sotovor 14 Tagen

@lingxi This is actually the best way to ship

Profilbild von why
whyvor 14 Tagen

@lingxi The low-conflict window is interesting, but the real unlock is having the agent surface small, reviewable changes instead of opening one giant cleanup PR.

Profilbild von Vito
Vitovor 14 Tagen

@elonmusk @lingxi That guy is brilliant

Profilbild von K ι T-7Y Wolf❤️🫶❤️
K ι T-7Y Wolf❤️🫶❤️vor 14 Tagen

@lingxi 3am club 😎🫡

Profilbild von Alek
Alekvor 14 Tagen

@lingxi 3 AM merges with zero conflicts?

Profilbild von Aditya Kumar
Aditya Kumarvor 14 Tagen

@lingxi oh wow, we used to do that at @Meta and nobody even noticed. Like upgraded C++ version of a very large codebase with only a handful of people. But AI does it and suddenly it is cool!

Profilbild von The Retarded Elon
The Retarded Elonvor 14 Tagen

@lingxi they talked about peadpod too :)

Profilbild von Eternities AI
Eternities AIvor 14 Tagen

@lingxi 3am is cheap because conflict rate drops, not because judgment does. overnight cleanup only works if the bot can fail closed and leave a receipt a morning human can reject without archaeology.

Profilbild von Tree Lake Rain 🌲🦆🌦️
Tree Lake Rain 🌲🦆🌦️vor 14 Tagen

@lingxi

Profilbild von Hey Its Burt
Hey Its Burtvor 14 Tagen

@lingxi Facts: When you work with a lot of people, sometimes find times when you can work off-hours from everybody else. Or have the bots work when nobody else is working and coordinate with the other bots who happen to be working.

Profilbild von Sam Liu
Sam Liuvor 14 Tagen

@lingxi Overnight agents are compelling because they turn idle hours into a durable inbox, not because they merge unattended. In @puffoai, agents can work in parallel, leave results in shared threads, and hand consequential changes back to humans for review.

Profilbild von Daniel Silva
Daniel Silvavor 14 Tagen

@lingxi Ohh

Profilbild von Mar Jo
Mar Jovor 14 Tagen

@elonmusk @lingxi 👏👏👏👏👏

Profilbild von Daniel Silva
Daniel Silvavor 14 Tagen

@lingxi Great 👍🏻 follow me

Ähnliche Videos

The SpaceXAI team just leaked the Grok Bots they run on themselves. Ten installs. A $1,000,000/year org chart if you hired this as people. 1. Fondi, Nao (Naoufal), Field Engineer at SpaceXAI Reads your public site and stands up a leadership suite. Installing Grok Bot plus this bot is the hire. 2. loops, Matt Palmer, Cursor + Grok Bot at SpaceXAI The outer loop he runs engineering on. Sits above coding agents, writes the goal, reviews, merges. You name the repo. 3. Projects Manager, Eric Zakariasson, SpaceXAI (prev Cursor) One bot, then it spins up a coder, designer, researcher, writer. Notion is source of truth. Replaces a PM plus a four person pod. 4. Chieeeeefy, Nao (Naoufal), Field Engineer at SpaceXAI Chief of staff for a field engineer. Calendar and inbox first. The $120k EA seat. 5. Rutin, Nao (Naoufal), Field Engineer at SpaceXAI Monday tune up for every routine across the fleet. The ops hire that stops silent failures. 6. dr eggbot, Lauren (poteto), Grok Bot at SpaceXAI (prev Cursor) Builds other Grok Bots for you. Skip the consultant who charges five figures to set your agents up. 7. loom, Lauren (poteto), Grok Bot at SpaceXAI Reads your Gmail threads and drafts the reply. Never sends. An $80k EA inbox, minus the send button. 8. Querie, Emily Gavrilenko, building SpaceXAI (prev Cursor, former founder) Her data scientist bot. Owns every analytics query and spreadsheet pull so nobody else on the team touches them. 9. Echo, Krista Letz, Enterprise at SpaceXAI (prev Cursor) Turns a sales call into slides straight from the call notes. Runs automatically after every customer call, or mid call with /echo. 10. SE call bot, Scott Metcalf, GTM Productivity at SpaceXAI Live backup for solutions engineers on customer calls. The $180k SE sitting in the room. Save this. These are the people who ship the product 👇

unicode

48,600 Aufrufe • vor 27 Tagen

acpx v0.4 ships Agentic Workflows, or as I like to call them "Agentic Graphs" It let's you create node-based workflows on top of ACP (Agent Client Protocol), to drive any coding agent (Codex, Claude Code, pi) through deterministic steps This let's you automate routine, mechanical legwork like triaging incoming PRs, bugs in error reporting, and so on... For example, OpenClaw receives 300~500 new PRs per day. A lot of them are low quality, but they still relate to real issues, so you have to address them somehow You need to: - extract the intent - cluster them based on intent - figure out if the proposed changes are legit, or whether they are slop local solutions, like trying to catch flies instead of drying out the swamp - if the PR is too low quality or the intent is not clear, close them - run AI review on them them and address any issues that come up - refactor them if the changes are half-baked - resolve conflicts - and so on... So that when the PR is presented to the attention of the maintainer, all the routine legwork is done and the only remaining thing is the decision to (a) merge, (b) give feedback to the PR author, or (c) take over the PR work yourself I wanted to build this feature since a couple months now, since Codex got so good. OpenAI models are now good at judging implementation quality, so I found myself repeating the same steps I wrote above over and over I also tried putting all this in a single prompt. But I believe there are workflows that should not be a single prompt, but a sequence of prompts in the same session That is because like humans, LLMs are prone to PRIMING. I claim that putting all steps in the same prompt at the beginning of the context will generally give suboptimal results, compared to revealing the intention to the model step by step Creating such a workflow also gives more OBSERVABILITY into the each step that an agent is supposed to take. Agent generates JSON at the end of each step, and that structured data can be used to monitor thousands of agents running at the same time in an easier way, on a dashboard Similar features have been introduced in e.g. n8n, langflow. But AFAIK they are not integrating ACP like the way I do I wanted to have a fresh approach, and to build an API that I can develop freely the way I want, so I created a new workflow API inside acpx The video is from the workflow run viewer, but that is not where you build the workflow. You build it by using the acpx flow typescript API. See examples/pr-triage in acpx repo Before building that, I started from a Markdown file with a Mermaid chart of the flow I had in mind. The Markdown file acts as a spec for the flow, and I have built the workflow through trial and error. I call this process "workflow tuning" I started working on acpx repo PRs one by one, tuning the flow, slowly scaling to more PRs. Finally, when I felt confident, I ran it in parallel over all external open PRs in the acpx repo. I believe it already saved me hours this week My next goal, if well received, is to set this up on a cloud agent so that it can process the 300~500 PRs the OpenClaw repo receives every day, in real time, as they come in I believe this will save all open source maintainers around the world countless hours and make it much easier to herd and absorb external contributions from everyone!

Onur Solmaz

149,693 Aufrufe • vor 6 Monaten