Scape (@scapedotwork) header
Scape (@scapedotwork) profile picture

Build the tools and infrastructure that supercharge how you work, then let your agents use them to work exactly like you do. Run unlimited agents in parallel.

Joined April 2026
Photo by Scape (@scapedotwork)Photo by Scape (@scapedotwork)Photo by Scape (@scapedotwork)Photo by Scape (@scapedotwork)Photo by Scape (@scapedotwork)Photo by Scape (@scapedotwork)Photo by Scape (@scapedotwork)Photo by Scape (@scapedotwork)Photo by Scape (@scapedotwork)
Meet Argus, the best agent orchestrator in the galaxy.
1
5
66,575
Ok. Here me out @scapedotwork
1
1
54
Head of Design at Stripe on how to stop creating zombie UIs
If we only use AI to make the things that we already make, just faster, then we're definitely missing out on the most interesting part. From my talk at @lennysan’s Summit, here are four ideas for raising the ceiling, not just the floor: - Have a point of view [5:38] - Encode your standards into the machine [9:07] - Don't confuse done with good [12:21] - Unleash creativity and artistry [16:19] Full talk here: youtu.be/GLvFTMtw4Jk?si=-5Ts…
106
469
76
5,160
357,374
Flight Plans have dropped on Scape.work
2
2
98
Replying to @scapedotwork
@scapedotwork impressive IDE, maybe the first orchestrator IDE workflow that feels usable
1
1
1
49
this is probably the dumbest thing i've ever built a leaderboard where the best laugh ranks at the top 😂 lolololololol.lol
72
9
11
210
22,052
A senior engineer with 20 years of experience built an AI agent that runs like a full time employee. It works on a loop. 24/7. 🤯 He called it Lloyd. Here is what it actually does. Lloyd has its own database. Its own ticketing system. Think of it like giving your AI agent its own internal Jira that only it manages. Every few minutes, Lloyd runs a heartbeat. A cycle of automated checks: → Scans email for new customer bug reports → Before creating a ticket, it searches its own database for previous related work → Checks if any documentation on the website is outdated → Reads the app's live logs to find problems nobody reported yet → If it spots a bug or has an idea for improvement, it creates its own ticket and flags it for the human to review 600 tickets managed so far. Lloyd found bugs that no customer reported. Surfaced patterns from logs that did not throw errors but looked wrong. Created enhancement ideas on its own. Here is why this matters. Most people use AI agents as chatbots. Ask a question, get an answer, done. This engineer gave his agent memory, autonomy, and a database. Every ticket it handles makes it smarter about the next one. Compounding knowledge. Just like a real team member who has been at the company for years. The agent is not waiting to be told what to do. It is proactively finding work that needs doing. This is the difference between using AI and employing AI.
11
10
2
87
10,188
Dropping shortly
2
185
I may have a problem.
175
Here's a quick example of what agent orchestrator loops can look like with Claude Code, Codex, or OpenCode
1
169