Engineering
One browser per bot: give the busy one a helper teammate
Your main bot stalls because everything that needs a look waits in one browser line.
What hurt
William Whittington (@WheelerMan) hit the one-browser-per-bot wall with DNA bot Helix. He built Strand, a second bot whose whole job is to help: anything that needs a visual look in a browser, Strand can take while Helix keeps looking at something else; Strand can also run its own background tasks so Helix gets more done at once. If one bot keeps stalling in line, give it a teammate. Not affiliated with xAI.
What to install or create
Keep specialist busy → spawn helper bot for parallel browser work.
Bots
Helix (specialist)
Owns the main job; keeps its browser on the hard path.
Strand (helper)
Takes overflow browser looks and background tasks.
Plugins
Browser
Required
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/WheelerMan/status/2112668934969209226 (credit @WheelerMan).
- 2Notice when your specialist stalls because one browser is busy.
- 3Create a second bot whose job is only to help that specialist.
- 4Route visual/browser overflow and light background tasks to the helper.
- 5Keep irreversible actions on the specialist (or behind your approval).
Approval fence
You decide which bot owns which sites; helpers don't take irreversible actions alone.
What to tweak
Steal the fence: don't queue behind one browser—add a helper with its own.
Source
William Whittington @WheelerMan · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.