
Co-Founder @specstoryai. Organize D.C. AI tinkerers. Use https://teapawt.org/t.co/kg5JldHaiU, a calm agent multiplexer with familiar IDE features, for macOS.
Washington D.C.
Joined October 2015
- Tweets1.9K
- Following475
- Followers1.1K
- Likes1.4K
Pinned Tweet
hAvE yOu hEaRD aBoUt: omniagent, paseo, orca, t3code, herdr, cmux, etc etc?
ofc but I drive my with agents sessions with a cat.
👉tortie.sh/
a calm agent multiplexer that feels like vscode, doesn't make you learn tmux and does everything it can to save your work
Am perplexed. AFAICT Netlify is has terminal Lovable envy and is chasing its users while Vercel (whom Netlify lost the jamstack war to) is the default infra agents want to deploy.
Airtable made this bet too and look how that turned out.
New mission. New brand. New website. New Netlify. ✨
Turn your imagination into reality. Describe an app, build it with agents in a live preview, and developers and your agents can pick it up in Git or your own preferred tools.
Check out @biilmann’s new video.
2
249
millennial kryptonite is having an out of town boomer parent's online account be compromised and being physically and emotionally incapable of helping them
142
Word to the wise: this is NOT a full account reset.
Its just for Fable usage.
Don't be like me (without reading closely) and bash reset. I did this: dropped from 100% consumed to 92% because honestly who was using Fable 5.1 up until today when Opus 5.5 has been so grand to consume their usage.
So really not that generous, definitely misleading and yet another way that Ant sucks at comms.
We wanted to do more for the people who’ve been with us the longest. So with Fable 5.2, the longer you’ve been subscribed, the more Fable resets you get.
3
3
332
Moments ago there was a deafening roar outside… Airforce 1 overhead my roof deck by Catholic U in DC.
1
6
454
Highly recommend you start doing this. Here is an example of how long an org and billing spike took in precise "agent hours" (new estimation unit to replace eng weeks?)
Curious about how to get started? Read: gregceccarelli.com/writing/h…
Using claude code workflows extensively with access to session traces and message timestamps has an unexpected fringe benefit: am able to produce very precise estimates of total wall clock time required to spec, build and fully verify features.
Before: claude was like "Oh this plan will take 2 to 3 engineering weeks" and we all knew that was wrong.
Now: claude is like it will take 7 hours of agent build and integrate implementation time, 5 - 6 hours to verify, fix and reverify and 45 minutes to release to prod via your process based on the last 60 phases you ran and my calculation of spec complexity, files touch, verification scenarios to run through for this change and your CI/CD timings.
Its been accurate within +/- 10 pp over the last few weeks.
1
178
You would not even believe the amount of credentials / keys (aws, gcp, azure, saas vendors, oai, ant, etc) exposed to models via agents on a daily basis in agent session logs.
I don't even think you can even fathom the volume of exposure.
The Trezor Safe 7 is a beautiful piece of hardware with software that is an equal complement.
Upgrading from the Trezor One after years of use was well worth it.
Really an incredible product.
1
240
Expert level baiting
despite the unfortunate timing, we take disclosures seriously at @typesafeai
at approximately 6:49PM this Friday evening, we became aware of a massive unauthorized leak of ALL customer noul outputs
in effort to maximize transparency, here is the link: gist.github.com/diogo149/810…
3
918
Greg Ceccarelli retweeted
Since developers aren’t coding anymore, their new job is to rotate secrets every single fucking day
Greg Ceccarelli retweeted
>junior dev at a mid startup
>wednesday morning
>just want to push a minor bugfix to our php app today
>open laptop, check slack
>company group chat is an absolute warzone
>CTO typing in all caps about php2shell
>fucking php
>whatever, server hasn't blown up yet, I just need to get my code in
>open gitlab to merge the PR
>forced emergency logout because of a critical gitlab security patch release
>fucking gitlab
>pipeline fails because of some weird regex compiler bug
>spend 40 minutes fighting CI/CD
>i can just use AI to help debug
>fire up opencode
>api keys nuked because they were breached
>fucking opencode
>i’ll just get fresh LLM api keys from our corp proxy, LiteLLM
>it won’t connect? It’s down?
>look up LiteLLM news: supply chain compromise
>fucking litellm
>cold sweat forming
>slack alert: db connection error
>check our database connection
>we host on TiDB Cloud
>they just announced a security breach, unauthorized access via stolen service account credentials, data copied
>fucking tidb cloud
>full panic attack incoming
>figure fuck it, just ship the container to Railway and go home
>open Railway dashboard
>bright red banner: "Security Disclosure: Rotate all environment variables immediately. All builds paused."
>fucking railway
>try to open the app URL in browser to see if anything is even working
>NET::ERR_CERT_AUTHORITY_INVALID
>eMudhra intermediate certificates compromised
>4
>instantly untrusted by every major browser
>fucking emudhra
>stare blankly at mac screen for 10min
>random pop-up
>restarting in 10min to fix a critical vulnerability
>fucking macos
>close laptop
>leave office
>never come back
By popular request, field notes with worked examples on exactly how I use estimate future agent work from logs to escape the wrongly calibrated, default and ungrounded "yeah this spec and work will take 2 to 3 engineering weeks" we all dread.
Can skip to a straightforward getting started section!
gregceccarelli.com/writing/h…
Using claude code workflows extensively with access to session traces and message timestamps has an unexpected fringe benefit: am able to produce very precise estimates of total wall clock time required to spec, build and fully verify features.
Before: claude was like "Oh this plan will take 2 to 3 engineering weeks" and we all knew that was wrong.
Now: claude is like it will take 7 hours of agent build and integrate implementation time, 5 - 6 hours to verify, fix and reverify and 45 minutes to release to prod via your process based on the last 60 phases you ran and my calculation of spec complexity, files touch, verification scenarios to run through for this change and your CI/CD timings.
Its been accurate within +/- 10 pp over the last few weeks.
Hot take: long running agents (e.g. using Opus 5.5 w/ ultracode) are so adept at being orchestrated that building software with LLMs has become pedestrian.
~12 months ago using Opus 4.5 still required substantial steering but you really did _feel_ amplified. I remember being absolutely engrossed in the work and looking forward to figuring out what to do next -- whether it was research, planning & speccing, reviewing implementations, figuring out how to translate more ideas into action, etc. All the while combatting (AI Vampirism).
~6 months ago when Opus 4.8 and "/goals" were introduced I was enamored with the possibility of much longer running sessions and figuring out how to construct the right upfront verification requirements. There was the challenge of writing good goals and getting them to run autonomously.
Now once you have a reasonably articulate definition of what you want and a defined process for how to research and build, you barely have to _do anything_ and I can sum up the residual of what was once still a creative process after writing code diminished as just "executive review".
Case in point: over the course of the last 30 days I've pushed over 105B tokens through agentic workflows running 24/7 to build tortie.sh and specstory.com/runstory.
Most days amount to substantial accretive change in each which is exciting but what I'm personally doing is light management if you can even call it that.
I spend a few hours at the start of a week designing the next set of backlogged phases of work to complete and just unblock the agents that fully spec -> build -> integrate -> verify -> fix -> reverify each phase until I end up using what comes out the tail end.
Ofc I can actually go touch more grass now: nice! But manipulating digital bits into existence with agents has started to become as dull and soulless as managing large teams of humans eventually did.
I didn't expect to hit this wall within 2 years and I'd assume others will or do already feel the same.
Imagine by contrast being Accenture who yesterday rolled out $29/mo Claude spend limits to their 800K employees. Which annualizes assuming full consumption to $280M a year in spend.
Some if not most companies have zero understanding of power laws.
in 2 years every company will have 2-5 guys who get paid $10m/year to be the only ones allowed to use fable 10
your job is to figure out how to be one of those 2-5 guys
1
2
379
Using claude code workflows extensively with access to session traces and message timestamps has an unexpected fringe benefit: am able to produce very precise estimates of total wall clock time required to spec, build and fully verify features.
Before: claude was like "Oh this plan will take 2 to 3 engineering weeks" and we all knew that was wrong.
Now: claude is like it will take 7 hours of agent build and integrate implementation time, 5 - 6 hours to verify, fix and reverify and 45 minutes to release to prod via your process based on the last 60 phases you ran and my calculation of spec complexity, files touch, verification scenarios to run through for this change and your CI/CD timings.
Its been accurate within +/- 10 pp over the last few weeks.


















