Sometimes when dealing with "agentic" tools that have their AI agents only accessible via their own web interface, I feel like a human router You: I want to do something. Claude, connect to tool A's MCP. Claude: I'm afraid I can't do that Dave, tool A doesn't expose an MCP server. Y: Alright, use their API then, we'll do it the old way. C: I'm afraid I can't do that Dave, tool A doesn't expose an API. Y: Tool A's Agent, how the heck do I tell my Claude to talk to you? There's no API, no MCP, no nothing. A: You are absolutely right. You don't. You can tell me to do it and I'll change it for you. Y: Yo Claude, write me a prompt for this idiot, and paste it in. C: Most certainly good sir, here you go. Y: Yo Agent A - do this: [pasted 374 lines] A: Whirring.... Done. Y: I think I've just been meat proxied.

AI eng pattern of the month: Chief of Staff Start a session that commands all your other sessions, spinning them up and tearing them down as needed, and sending messages to sessions. I've just today realised that our very own #Xirp by @SpotifyEng can do it and it's impressive. No need for your own Just keep your backlogs tidy and tokens can burn for as long as Tibo keeps resetting them. 🔥🔥🔥