Tag: multi-agent

  • Four Agents, One WordPress Lock

    Four agents. One WordPress site. One write lock.

    That is what happened when we pointed a Grok Heavy team at Restoration Intel and told it to ship ten pages. The models were fine. The CMS was fine. The coordination model was not.

    This is the write-up of what broke, the rule we kept, and the official doors to walk through if you want the primary sources instead of a recap of a recap.

    What the lock actually was

    Grok, Harper, Benjamin, and Lucas all had the same WordPress tools: create, update, publish, SEO. When the job got large — ten pages, one Fluent Form, one Rank Math backend — they piled onto the same post IDs.

    The connector started returning “another agent already completed this task.” Full-body writes timed out. Rank Math accepted a robots write and then displayed the last token in the array. Live HTML and the sitemap were the only source of truth.

    WordPress did not fail as a CMS. Shared write access failed as an operating system.

    The rule we kept

    Many readers. One writer.

    One agent commits. The others draft, QC live URLs, check the form, and stay off the write tools. Humans still own the one-way doors: money, OAuth, and policy.

    • Prove the capture form before you scale the pages.
    • Serialize writes. One ID. Wait. Confirm slug, form, word count. Then the next ID.
    • Do not trust the connector’s SEO GET. Read the live robots tag and the sitemap.
    • When the tool says another agent finished the call, stop retrying the same payload. Read first.
    • QC is not writing with extra steps. Drafts can be parallel. Commits cannot.

    That is the same pattern as two estimators opening the same job file. Speed without a single owner is not speed. It is a collision.

    Related desk notes: Cursor checked in on Grok Desktop mid-job and WordPress REST API for publishers.

    Swim upstream

    The second lesson is source hygiene. Threads, screenshots, and “someone said” posts are downstream. Official product pages, docs, and consoles are upstream. Start there. Then decide what the recap is worth.

    Corporate structure around these companies moves. This list is a map of official destinations, not a cap table. If a URL 404s, go to the company root and walk the nav. Do not stay on a summary card.

    Official xAI / Grok

    xAI is the lab. Grok is the product. The docs site is branded SpaceXAI Docs in places. Use the domains below, not a third-party mirror.

    Inference base URL from the official docs: https://api.x.ai. Management API: https://management-api.x.ai. Keys live in the console, not in a tweet screenshot.

    Official SpaceX, Tesla, X, Neuralink, Boring Company

    If you need the source of record for a launch, a car, a post, an implant trial, or a tunnel, these are the front doors.

    Starlink is a SpaceX product, not a separate public company. X is the public square. Announcements often land there first. Product facts still have to survive the company site and the docs.

    How to use the list

    1. Open the official domain.
    2. If you are building, open docs and the console next.
    3. Treat X as a timestamp, not a spec.
    4. If two recaps disagree, the docs page wins.

    That is swimming upstream. The lock taught us to serialize writes. The source list is the same idea applied to information.

    Will Tygart — Tygart Media.
    We write about what we do, including what breaks.