CTO @entitledsol. Scalable systems, vibe curator, backprop revelator
Noida, India
Joined December 2011
- Tweets1.4K
- Following395
- Followers119
- Likes3.8K
Meta has their WhatsApp Business Tools MCP out, I can finally configure/figure out stuff without navigating the mess that is Facebook Business Manager portal.
Currently in beta so you can only connect it to ChatGPT/Claude
@MetaforDevs please make it GA so I can connect it my @AmpCode
Vasu Bhardwaj retweeted
The two protocols sound so similar, I thought they were the same thing.
Personal Agent Protocol is being developed by Sierra & Meta.
Personal Agent Consent & Trust Protocol is being developed by Decagon with Instinct.
Let’s not have two protocols before we’ve even started.
People, is this why @claudeai doesn’t have to lure people in with continuous Reset carrots?
I'm betting the Anthropic ban of OpenCode is as technical and cost-saving as it is political. I've long argued there's a moat to be had by closing third party tools to subs. CC can rely on KV caching across every instance, and have KV caches on a per-organization basis for further customization for their largest customers.
They can, across their entire fleet, pre-compute 1/3-1/2 (if not more) of every CC user's system prompt. By encouraging baking this into MDM and enterprise plans too, they can further negotiate that out in these large contracts. It also potentially lets them do some more clever things than just pure prefix caching and make specific tradeoffs you don't just get by allowing anybody to use those endpoints.
At least that's how I'd do it. It surprised me it took THIS long.
When building an agent which needs to perform several business functions, Start with a large system prompt, and slowly start turning that guidance, into well defined workflows (temporal/restate whatever), while chipping away your system prompt. This is the way..
Being able to coach people, helping them look at the things they are avoiding (sometimes stuff that seems so obvious to everyone around them), is a legitimate skill, dare I say a natural talent
Breathe In… Breathe Out
Start thinking of your daily work with coding agents as breath work. You breathe in, then you breathe out. It's the most natural thing in the world.
Inhale. Describe what you want. The agent writes a bunch of code. You figure out what you actually wanted by iterating over what the agent does. Expansion. Keep inhaling. Exploration is nearly free, so you give feedback, until it seems right. Very good. Keep inhaling. Eventually your lungs feel full, no more air fits. You're done with the inhale, but that's only half the work.
Now comes the next half, the exhale. Take what you created. Tell the agent to fold it back into what already existed before. A brand new flow turns out to be just like an old flow, except with one branch in it. Good. Refactor. Delete the new flow. Somewhere three directories over there's a helper that already does what the agent wrote out. Refactor. Delete the duplicate code, and use the helper. Contract. Contract. Contract. Exhale completely, until there is nothing left except the essence of the new functionality. The lungs are empty, but the oxygen entered the body. The breath is done.
Only now do you make the PR, no earlier! Both inhale and exhale, the expansion and the contraction of the code belong in the same pull request. A full breath, or nothing.
Begin to think about merging pre-contraction code as holding your breath. Its technical debt is carbon dioxide, retained. Fine for a minute, then uncomfortable. Unsustainable. Painful, and if not remedied, darkness.
Breathe in. Breathe out. Always.
--
h/t @fractaledmind for the "always expand and contract in a single PR" idea that sparked this metaphor, along with the bout of bronchitis I managed to pick up in Austin at @railsworld this year