Paul Robinshaw

@0xShayan @Teknium I’m really struggling to get this to work. I have a subscription and an api key. End point is pointing at coding. Just get messages about topping up credits. Am I missing the equivalent of oAuth?

Is anyone using Hermes via the GLM 5.1 Pro/Max plan and if so, how is your experience? Tagging @Teknium for vis

@doodlestein @threadreaderapp unroll

Blows my mind how many people still don’t know about my Agent Mail project and how it does exactly what they want and much more, while sidestepping all the many footguns that a naive implementation would fall prey to. It’s a true game changer combined with beads and bv. Try it!

@doodlestein @jarredsumner @threadreaderapp unroll

@jarredsumner Worktrees suck ass, I’ve been saying this for months. The best solution I’ve found is my agent mail system with advisory file reservations. Plus beads. I’ve been using it for months now to produce ridiculous amounts of high quality software by myself.

I don’t love the UX of worktrees co-located LLM transcripts feel like the feature of the version control system that replaces git. commits & tags are zoom levels for context. I think PRs and CI as this step completely independent from local dev doesn’t make sense anymore

@doodlestein @threadreaderapp unroll

Friends don’t let friends use git worktrees for agent swarms for high-velocity development. I give the clankers hell if I ever catch them using worktrees. They’re just kicking the can down the road and sticking your 🤖 heads in the sand instead of surfacing the conflicts early.

@doodlestein Hands up who zoomed in on the monitor 😂🙋‍♂️

When you’re too locked in to go to the barber:💈 🦾🤖

@doodlestein I’d be really interested to hear experience with APR. I have it running. Results are impressive but I’m in the loop…for 15 interactions. I’ve tried writing a python loop to keep it iterating but fear this is absolutely the wrong approach.

@doodlestein Jeffrey how does apr link in with the above? Is it an automated version, to avoid the cut & paste? Thanks

If you have a markdown plan for a new piece of software that you're getting ready to start implementing with a coding agent such as Claude Code, before starting the actual implementation work, give this a try. Paste your entire markdown plan into the ChatGPT 5.2 Pro web app with extended reasoning enabled and use this prompt; when it's done, paste the complete output from GPT Pro into Claude Code or Codex and tell it to revise the existing plan file in-place using the feedback: --- Carefully review this entire plan for me and come up with your best revisions in terms of better architecture, new features, changed features, etc. to make it better, more robust/reliable, more performant, more compelling/useful, etc. For each proposed change, give me your detailed analysis and rationale/justification for why it would make the project better along with the git-diff style changes relative to the original markdown plan shown below: --- This has never failed to improve a plan significantly for me. The best part is that you can start a fresh conversation in ChatGPT and do it all again once Claude Code or Codex finishes integrating your last batch of suggested revisions. After four or five rounds of this, you tend to reach a steady-state where the suggestions become very incremental. (Note: I was originally planning to end this post here, but thought it would be helpful for people to see this part in the larger context of the entire workflow I recommend using all my tooling) Then you're ready to turn the plan into beads (think of these as epics/tasks/subtasks and associated dependency structure. The name comes from Steve Yegge's amazing project, which is like Jira or Linear, but optimized for use by coding agents), which I do with this prompt using Claude Code with Opus 4.5: --- OK so please take ALL of that and elaborate on it more and then create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.) Use only the `bd` tool to create and modify the beads and add the dependencies. Use ultrathink. --- After it finished all of that, I then do a round of this prompt (if CC did a compaction at any point, be sure to tell it to re-read your AGENTS dot md file): --- Check over each bead super carefully-- are you sure it makes sense? Is it optimal? Could we change anything to make the system work better for users? If so, revise the beads. It's a lot easier and faster to operate in "plan space" before we start implementing these things! Use ultrathink. --- Then you're ready to start implementing. The fastest way to do that is to start up a big swarm of agents that coordinate using my MCP Agent Mail project. Then you can simply create a bunch of sessions using Claude Code, Codex, and Gemini-CLI in different windows or panes in tmux (or use my ntm project which tries to abstract and automate some of this) in your project folder at once and give them the following as their marching orders (for this to work well, you need to make sure that your AGENTS dot md file has the right blurbs to explain each of the tools; I'll include a complete example of this in a reply to this post): --- First read ALL of the AGENTS dot md file and README dot md file super carefully and understand ALL of both! Then use your code investigation agent mode to fully understand the code, and technical architecture and purpose of the project. Then register with MCP Agent Mail and introduce yourself to the other agents. Be sure to check your agent mail and to promptly respond if needed to any messages; then proceed meticulously with your next assigned beads, working on the tasks systematically and meticulously and tracking your progress via beads and agent mail messages. Don't get stuck in "communication purgatory" where nothing is getting done; be proactive about starting tasks that need to be done, but inform your fellow agents via messages when you do so and mark beads appropriately. When you're not sure what to do next, use the bv tool mentioned in AGENTS dot md to prioritize the best beads to work on next; pick the next one that you can usefully work on and get started. Make sure to acknowledge all communication requests from other agents and that you are aware of all active agents and their names. Use ultrathink. --- If you've done a good job creating your beads, the agents will be able to get a decent sized chunk of work done in that first pass. Then, before they start moving to the next bead, I have them review all their work with this: --- Great, now I want you to carefully read over all of the new code you just wrote and other existing code you just modified with "fresh eyes" looking super carefully for any obvious bugs, errors, problems, issues, confusion, etc. Carefully fix anything you uncover. Use ultrathink. --- I keep running rounds of that until they stop finding bugs. Eventually they'll need to do a compaction, so if they do that, right after hit them with this (note that I've been typing AGENTS dot md to avoid the annoying preview on X because it thinks it's a website; you can replace that with a period and remove the spaces if you want; the agents don't care either way): --- Reread AGENTS dot md so it's still fresh in your mind. Use ultrathink. --- When the reviews come up clean, have them move on to the next bead: --- Reread AGENTS dot md so it's still fresh in your mind. Use ultrathink. Use bv with the robot flags (see AGENTS dot md for info on this) to find the most impactful bead(s) to work on next and then start on it. Remember to mark the beads appropriately and communicate with your fellow agents. Pick the next bead you can actually do usefully now and start coding on it immediately; communicate what you're working on to your fellow agents and mark beads appropriately as you work. And respond to any agent mail messages you've received. --- When all your beads are completed, you might want to run one of these prompts: --- Do we have full unit test coverage without using mocks/fake stuff? What about complete e2e integration test scripts with great, detailed logging? If not, then create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid with detailed comments. --- or --- Great, now I want you to super carefully scrutinize every aspect of the application workflow and implementation and look for things that just seem sub-optimal or even wrong/mistaken to you, things that could very obviously be improved from a user-friendliness and intuitiveness standpoint, places where our UI/UX could be improved and polished to be slicker, more visually appealing, and more premium feeling and just ultra high quality, like Stripe-level apps. --- or --- I still think there are strong opportunities to enhance the UI/UX look and feel and to make everything work better and be more intuitive, user-friendly, visually appealing, polished, slick, and world class in terms of following UI/UX best practices like those used by Stripe, don't you agree? And I want you to carefully consider desktop UI/UX and mobile UI/UX separately while doing this and hyper-optimize for both separately to play to the specifics of each modality. I'm looking for true world-class visual appeal, polish, slickness, etc. that makes people gasp at how stunning and perfect it is in every way. Use ultrathink. --- And then start the process again of implementing the beads. When you're done with all that and have solid test coverage, you can then keep doing rounds of these two prompts until they consistently come back clean with no changes made: --- I want you to sort of randomly explore the code files in this project, choosing code files to deeply investigate and understand and trace their functionality and execution flows through the related code files which they import or which they are imported by. Once you understand the purpose of the code in the larger context of the workflows, I want you to do a super careful, methodical, and critical check with "fresh eyes" to find any obvious bugs, problems, errors, issues, silly mistakes, etc. and then systematically and meticulously and intelligently correct them. Be sure to comply with ALL rules in AGENTS dot md and ensure that any code you write or revise conforms to the best practice guides referenced in the AGENTS dot md file. Use ultrathink. --- and --- Ok can you now turn your attention to reviewing the code written by your fellow agents and checking for any issues, bugs, errors, problems, inefficiencies, security problems, reliability issues, etc. and carefully diagnose their underlying root causes using first-principle analysis and then fix or revise them if necessary? Don't restrict yourself to the latest commits, cast a wider net and go super deep! Use ultrathink. --- You should also periodically have one of the agents run this as you're going to commit your work: --- Now, based on your knowledge of the project, commit all changed files now in a series of logically connected groupings with super detailed commit messages for each and then push. Take your time to do it right. Don't edit the code at all. Don't commit obviously ephemeral files. Use ultrathink. --- If you simply use these tools, workflows, and prompts in the way I just described, you can create really incredible software in a just a couple days, sometimes in just one day. I've done it a bunch of times now in the past few weeks and it really does work, as crazy as that may sound. You see my GitHub profile for the proof of this. It looks like the output from a team of 100+ developers. The frontier models and coding agent harnesses really are that good already, they just need this extra level of tooling and prompting and workflows to reach their full potential. To learn more about my system (which is absolutely free and 100% open-source), check out: agent-flywheel.com It include a complete tutorial that shows anyone how to get start with this process. You don't even need to know much at all about computers; you just need the desire to learn and some grit and determination. And about $500/month for the Claude Max and GPT Pro subscriptions, plus another $50 or so for the cloud server. If you want to change the entire direction of your life, it has truly never been easier. If you think you might want to do it, I really recommend just immersing yourself. Once you get Claude Code up and running on the cloud server, you basically have an ultra competent friend who can help you with any other problems you encounter. And I will personally answer your questions or problems if you reach out to me on X or on GitHub issues (it might be Claude impersonating me though, lol).

Hey @BBCNews can we get a break from Epstein, at least today. How about leading with a story of hope? Happy Christmas 🎅

@beev_v_v That was a while ago! A past life 😊

Dark Chocolate and Hazelnut Bûche de Noël. Have you got your order in? It's not too late. christmas.flourwatersalt.co.uk

@wise_kiwise @MacclesfieldNub Love this. Ace

My picture of #flourwatersalt #macclesfield part of a Macclesfield sketchers project #cheshireartist @MacclesfieldNub @_flourwatersalt

This is us from now until Christmas Eve 👊 Get your orders in & don't miss out. 🎅🎄 ⛄️ christmas.flourwatersalt.co.uk

I know! I know! Bangin' on... 5 days to go. What do you call Santa's helpers? Subordinate clauses! Tish boom 🥁 I'm here all night! christmas.flourwatersalt.co.uk

Nudge. We're closing the doors to our Christmas shop on Saturday 18th at 7pm. Orders are filling up. If you want to wake up to an epic Morning Bun on Christmas Day, you know what to do! christmas.flourwatersalt.co.uk

Fabulously busy day down at Market Place today. You can always get your order reserved by ordering online. shop.flourwatersalt.co.uk

Final last call for online orders for Saturday collections. Plenty to cheer up the weekend. The webshop closes at 1130pm shop.flourwatersalt.co.uk Thanks

Thursday morning - nearly the weekend! ⭐ Open at 9 Market Place 9am-3pm ⭐ Open at The Picturedrome 9am-10pm ⭐ Open online from 9am and we stay open until 1130pm on Friday. Get set for the weekend. Grab a coffee and get your orders in!

Final last call for online orders for Saturday collections. Plenty to cheer up the weekend. The webshop closes at 1130pm shop.flourwatersalt.co.uk Thanks

Thursday morning - nearly the weekend! ⭐ Open at 9 Market Place 9am-3pm ⭐ Open at The Picturedrome 9am-10pm ⭐ Open online from 9am and we stay open until 1130pm on Friday. Get set for the weekend. Grab a coffee and get your orders in!

It's Wednesday and we're open at 🤗 9 Market Place 9am-3pm. 🤗 The Picturedrome 9am-10pm 🤗 Online 9am-11.30pm shop.flourwatersalt.co.uk ☕ 🥐 🥖