Aircheck

Preview agent-queued social posts before they go out

Aircheck shows queued social posts, their media, and their send status before a posting job sends them. The posting job writes one JSON manifest per post. Aircheck reads that day's queue and shows the rendered post and media on the Today screen. The live landing page states that Aircheck shows every post agents queued today with its media; the live docs define the manifest and MCP tools that write and read it.

Evidence checked 10 November 2026: the live Aircheck landing page and the live Aircheck docs.

The workflow

  1. 1. Connect the queue writer

    Use the Aircheck MCP server. Add it to Claude Code or Codex, then ask your agent to call configure. Aircheck reads your setup, proposes the config and the required change for each posting job, and writes nothing until you approve it. See the setup procedure in the docs.

  2. 2. Queue one manifest per post

    When an agent queues a post, call queue_post. The MCP server then writes a manifest. A post manifest includes the lane, optional send time, exact post text, ordered media sources, status, and an empty postUrl until the post is sent. A job that already writes daily plans can instead run npx -y aircheck-mcp push with AIRCHECK_TOKEN. See the manifest and daily push procedure in the docs.

  3. 3. Open the day in Aircheck

    Open Aircheck's Today view after the queue has been written. The landing page describes three views: a send-time strip, a thumbnail sheet grouped by hour, and a list with the lane, format, send time, and file count. The list also shows whether each post is sent, queued, or missing files. See the Today view described on the landing page.

  4. 4. Inspect, then fix before sending

    Open each queued post and inspect its copy and every media item before the posting job runs. Use Example to show a fresh version, Feedback to request a revision, or Repair to rebuild the post through its own pipeline. Repair can replace a queued post only after approval. Undo restores the old copy. See the preview and repair actions on the landing page.

What should you check before a post goes out?

Check the lane, send time, exact text, media order, and status. A queued post should use the queued status ladder. Aircheck reports missing local media instead of silently dropping it. After a send, the same manifest is rewritten with sent and postUrl. See the manifest fields and status rules in the docs.

Can the preview publish the post?

No. The landing page says that a preview runs with no network and can write only in its run folder. Your posting jobs remain responsible for publishing. Aircheck reads the queue and can replace a queued post only when you approve a repair. See the local preview boundary on the landing page.

Sources: live landing page and live docs, both checked 10 November 2026.

Back to Aircheck