Ingeniería
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.
Qué dolía
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.
Qué instalar o crear
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
Navegador
Obligatorio
Rutinas
Ninguna en el primer uso. Mira primero una pasada manual.
El prompt
Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.
Primer uso
- 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).
Valla de aprobación
You decide which bot owns which sites; helpers don't take irreversible actions alone.
Qué ajustar
Steal the fence: don't queue behind one browser—add a helper with its own.
Fuente
William Whittington @WheelerMan · Publicación original
Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.
Paquete Pro
¿Quieres la configuración completa, no solo la idea?
Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.