POSTSTEWARD DOCUMENTATION

What would you like to do?

Use the workspace to control publishing. Find step-by-step setup, local installation and agent integration below. Each guide explains prerequisites and the next action.

Start with the task you need.

Open your workspaceConnect accounts, review copy, schedule posts and check results. No installation needed. First-time setupFollow account → project → reviewed post → result. Agent access is optional. InstallInstall the Linux runtime, pair it with your cloud workspace and review activation. LinkedIn Page access requires provider approval. Agent guideConnect an owner, delegate a token, publish approved copy and inspect evidence safely. Operation referenceSearch the generated operation catalogue by name, tier and required scope. Runtime helpMachine-readable availability and operation discovery for the deployment you are actually using. OpenAPIHTTP schema for clients that prefer a standard API description.

The model is intent → authority → effect → evidence.

PostSteward does not treat an API response as proof that a social post exists. It stores the reviewed intent, resolves an explicit destination, fences duplicate external effects and keeps provider readback separate from reservation state.

Do not retry uncertainty blindly.

If a provider write has an ambiguous outcome, inspect the existing receipt and provider evidence. Reusing a new idempotency key to force another post defeats the safety boundary.

Connect the services available to your workspace.

Sign in with Google to create a free workspace, then connect X or Threads through OAuth. Install the local runtime when you want publishing work to run on your machine.

LinkedIn Page access awaits provider approval. Advanced purchases open when the GBP price is confirmed. Browser WebMCP is available in browsers that support it; HTTP and remote MCP are available to authenticated agents.

Agents can skip this interface entirely.

The human documentation is additive. Agents may continue to use the raw guide, generated operation Markdown, OpenAPI, `catalog.json`, `help.json`, `llms.txt`, HTTP or remote MCP directly.

Connect accounts and approve a post

Open Social accounts and connect X or Threads with OAuth. LinkedIn Page access requires provider approval. Connection status explains which actions your account supports.

Create a publishing project to group accounts. Under Create & schedule, enter and validate the exact copy, choose an account and set a time. Direct agent copy waits for owner approval. For recurring work, choose autonomous publishing under AI preparation: authorise sources, editorial context, destinations and cadence once. Checked supply then proceeds within that standing authority. Hosted publishing needs no local install; a payment does not grant authority.

Find a schedule or resolve a failed delivery

Open Schedules & results. Use the state filter or search to find a receipt; the workspace loads the latest 50. Scheduled means reserved, Verified means provider readback matched, and Needs readback means publication is still unverified.

For an ambiguous effect, inspect the existing receipt and provider before taking another action. Do not create a new post to clear uncertainty. Get help if the result cannot be resolved.

Prepare an original campaign

In Release preparation, connect your workspace’s own OpenAI API account, select a release and provide the audience, objective, voice and approved context. Your model account pays for generation directly.

Inspect strategy, exact source support and channel drafts. Edit or regenerate, run editorial checks, then approve the exact saved revision. Preparation does not publish or schedule; delivery needs a separate action. Model checks assist review and cannot prove factual truth. Read the preparation workflow.

Advanced and billing

Advanced & billing holds reviewed automation profiles, exact subscription quotes and billing management. Advanced keeps reviewed source changes moving through approved templates and scheduled work. It requires workspace entitlement and approved profiles.

The monthly price is in GBP and remains to be confirmed. New checkout is unavailable until a matching live price is configured. Existing customers can use Manage billing where configured. Agent billing permission still requires payer consent and any bank authentication.

Automation inventory shows source observations and reserved work; it does not prove a provider published anything.

Control an agent’s permissions

Under Agent permissions, issue only the scopes it needs and set an expiry. Copy the token when shown, keep it private and revoke it when no longer needed. Revocation prevents future authorised operations; it cannot undo an external post already made.

Export data or delete a workspace

Use Export workspace in Schedules & results for your current records. Data & deletion explains deletion, requires explicit acknowledgement and an exact typed confirmation, and reports pending cleanup separately from completion. Read the consequences before proceeding.

Recovery and local runtime help

Recovery shows checkpoint evidence. Restoration and resuming publication require their own reviewed steps; restoring data is not authority to republish. Use the workspace recovery controls only after reading the review and effect warnings.

For installation, pairing, activation, deactivation, updates or migration, use the local installation guide. Local and hosted execution share cloud account custody and one reviewed publishing authority. They are two ways to run the same workspace.

Deployment diagnostics

RuntimeLoading…