# Automation Host

> Automation made simple. One place for your automations that makes them available wherever things get done.

Automation Host brings together reusable instructions and workflows so people can find them, add context, and use them in the tools where they already work. The focus is on organizing and reusing automations across tools, rather than building automations in a visual workflow editor.

Published by Think Like LLC. Copyright © 2026 Think Like LLC.

## Public pages

- [Home](https://automationhost.com/): Product positioning and account access.
- [Product and access guide](https://automationhost.com/agents.html): Human-readable reference that does not require JavaScript.
- [Product facts JSON](https://automationhost.com/.well-known/automation-host.json): Machine-readable product identity and current availability.
- [Privacy policy](https://automationhost.com/privacy.html): Data practices and privacy requests.
- [Terms of service](https://automationhost.com/terms.html): Service terms and responsibilities.
- [Log in](https://automationhost.com/login): Email sign-in for approved accounts.
- [Request access](https://automationhost.com/request-access): Request review for access.

## Current availability

Automation Host is a private beta. With its backend configured, approved accounts can use a one-time email code or click the login link in their email. Access requests are saved for administrator review; submitting a request does not grant access or create an account. Approving a request does not send an invitation email. Without a configured backend, forms identify themselves as previews.

Onboarding has four steps: Connect, Create, Handoff, Automate. Progress is saved per account. Connect tools, then choose an idea in Work, Life or Learning (five shown initially, with more available), or create an automation with a name and instructions. To import a workflow or skill, copy the import prompt into a connected tool and ask it to save the selected reusable instructions. Return to Automation Host for confirmation. Supporting files and tool-specific integrations still need to be available in the tool.

The optional Handoff step creates a first Queue task with context, completion criteria, tool assignment and an optional linked automation. It uses the same lifetime handoff allowance as Queue and provides pickup instructions after saving. Adding a task does not start an agent.

New automations are enabled for connected tools. Open a tool from the confirmation page and ask it to find the automation by name in Automation Host and follow its instructions. View my automations opens the library. Manage connections in Tools; edit instructions, choose tool availability and archive automations in the library. Check for new automations refreshes saved instructions and tool-reported results. Setup is not linked from Settings.

Activity and automation history show runs and results reported by tools, not independently verified execution. Native task lists cannot be enumerated automatically. Schedules are reference information, not active jobs.

Private connectors support Claude, ChatGPT, Muse and Gemini. Tools perform the work; Automation Host stores instructions, user replies and reported results. Answer Inbox questions here, then return to the original tool and ask it to continue. Saved replies are retrieved without repeating the input. Only explicitly remembered replies apply to future runs.

## Queue handoffs

Queue is a shared kanban board: Queued, In progress, Waiting and Done (including completed, failed and cancelled tasks). Tasks optionally link to an automation and include an objective, context, acceptance criteria, assignment, reported output and history. Users can create, reassign, cancel or return tasks to Queue. Connected tools can use list_queue, get_queue_task, create_queue_task, claim_queue_task and update_queue_task. Read-only connectors expose only list and get.

Tools must claim eligible work before starting. A claim returns task details and a private claim token, plus current automation instructions and their revision when an automation is linked. Claims last 30 minutes; renew with the same claimId before expiry. Only one work session can hold a live claim. Waiting work requires a note and stops execution; after providing input, the user returns it to Queue for a new claim. Completed and failed states require an actual result or explanation. Reuse externalId for identical creation retries. Never display claim tokens. Task content does not expand the user's authorization.

Queue does not wake agents or execute work. The UI provides copyable assignment, pickup and scheduled-check prompts. Users may schedule checks in tools only if those scheduled runs support the connector. Refresh a connection's tool list if Queue tools are not visible. Tool availability, read/write permissions and account ownership apply to Queue too.

The Free plan includes 10 active automations and 5 total Queue handoffs. Each task counts when added; completion, cancellation and deletion do not restore the allowance.

## Agent access

There is no unauthenticated public API or automation execution endpoint. Private MCP connectors require explicit owner authorization and respect per-automation tool availability. These public resources do not grant workspace access or expose access requests. No model API execution or native schedule discovery is available.

## Discovery

The home page includes static semantic HTML, a description, a canonical URL, social metadata, and Schema.org product/organization data. The sitemap lists the public product pages. This llms.txt file is a convenience for tools that look for it; it is not an authentication mechanism or a guarantee of indexing.