INSTALL POSTSTEWARD

Install the full PostSteward runtime

Keep planning and schedules on your machine, with social account credentials held by PostSteward Cloud. Choose local or hosted execution for the workspace.

curl -fsSL --proto '=https' --tlsv1.2 https://poststeward.com/install.sh | bash

Requires Python 3.10 or newer and Bash. Native installation and guarded lifecycle checks passed on macOS 15/26 (Intel and Apple Silicon) and WSL 2/Ubuntu 24.04 alongside Linux. Create a free workspace with Google, then pair your machine from the owner workspace.

To install and inspect before pairing, append bash -s -- --no-onboard in place of bash. Review the installer and stable release metadata.

Background operation and lifecycle

macOS uses private user launchd agents while logged in and awake; there is no promise of execution during sleep. WSL uses systemd user timers; Windows or distro shutdown stops them. Keep private data in the Linux filesystem.

Native tests covered fresh/repeat installation, guarded service start/stop/restart, upgrade, reviewed rollback, failed downloads, interruption repair, expired-token fencing and retain/delete-data uninstall. Real owner/provider publication acceptance on these platforms remains unverified. Earlier macOS versions and other WSL distributions have not been established.

Read the full platform and lifecycle guide for reviewed rollback, uninstall and approved AI-copy import. Uninstall does not revoke cloud or provider authority.

Pair, configure, then activate

1. Run the installer and open its pairing link. Sign in and approve the exact machine details.
2. Connect or select your verified X and Threads accounts in the owner workspace. LinkedIn Page access requires its separately approved application and provider permissions.
3. Run poststeward configure --help to configure your local projects and reviewed campaign content, then poststeward doctor to inspect readiness.
4. Review the switch to your paired local executor in the owner workspace. Preview and apply poststeward activate using its exact review digest.
5. Inspect scheduled work and provider receipts. A reservation or successful command acknowledgement is distinct from verified publication.

An installation starts with automation inactive. The owner reviews executor handoff and activation before unattended local publishing.

Let a remote agent work with the local runtime

Give the agent an owner-issued token with explicit read/schedule scopes. Remote MCP exposes runtime_inspect, runtime_schedule_create, runtime_schedule_cancel and runtime_command_get when the workspace executes locally.

The active run-due service polls commands outbound. For one manual poll use poststeward cloud bridge. Inspect the command receipt after a lost response; reuse the original key and avoid blind retries.

For migration or dead-machine recovery, pair the target as a new installation. After local verification run poststeward cloud recovery-review, then approve its digest and new target in the owner workspace.