All use cases

Content

Two X agents, one shared file: new/used markers beat clever prompts

Writer and poster bots collide because each trusts its own memory.

Share

What hurt

Paulo Pierrondi (@paulopierrondi) hands X work between two agents via a shared file: one writes posts marked new or used; the other only posts items marked new, then stamps post id and time; anything you ask for goes in a priority file that jumps the line; neither trusts memory—both reread the file every round. A shared file beats a clever prompt. Not affiliated with xAI.

What to install or create

Shared file with new/used → poster stamps → priority file → reread every round.

Bots

  • Writer

    Writes posts into the shared file marked new or used.

  • Poster

    Posts only new items, stamps id/time; rereads every round.

Plugins

  • X

    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

  1. 1Read https://x.com/paulopierrondi/status/2112700188645011794 (credit @paulopierrondi).
  2. 2Create one shared file both bots can read and write.
  3. 3Writer only adds posts marked new or used; Poster only takes new, then stamps post id and time.
  4. 4Put direct human asks in a priority file that jumps the line.
  5. 5Tell both: never trust memory—reread the file every round.

Approval fence

Nothing posts without your usual publish gate if you require one.

What to tweak

Steal the artifact handoff: markers on disk, not vibes in chat.

Source

Paulo Pierrondi @paulopierrondi · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

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.

See Pro