Documentation version: 2026-10-03.4
Canonical: https://docs.creator.gg/guides/agent-setup.md

# Base agent setup

Start with one setup prompt in the intended agent. The prompt covers connection, company context and the optional draft offer. Do not require an @ mention or send the user back for a second reply-setup prompt. Use the sequence below for first setup and when adding a host. Later workflows reuse verified access and saved company context. A new host still needs its own access check. Setup does not authorize a marketing action or a recurring job.

## 1. Establish access in the intended host
Use one continuous setup in this conversation. First discover the available Creators tools and call workspace_status in the intended host. If it succeeds, skip installation and authorization and continue with saved company context. Do not require an @creators mention or a second setup prompt; ordinary requests can use available tools. Read https://docs.creator.gg/guides/agent-setup.md for current guidance. Only if tools are missing or access requires recovery, check the host's existing connection and use its supported Connect / Authenticate or plugin-install control when available. Show manual connection instructions only when those controls cannot complete the missing step. The user completes sign-in and consent. A custom MCP server cannot be installed by prompt alone when the host exposes no install control; explain that exact limitation without claiming it is connected. Preserve the setup request and supplied choices, then continue after connection; if the host requires a reload or new session, give a short resume handoff, not a second onboarding questionnaire. @ selection is an optional discovery fallback. Reuse matching connections within the host and account; leave other agents connected and never copy their credentials. A local Codex connection does not transfer to a new cloud task; do not create empty tasks to discover this. During full setup, resume intelligence and the saved plan, then inspect native scheduling availability without creating a job. Prefer hosted execution for recurring work, use the shared native scheduler guidance before creating anything, and report connection, context and automation readiness separately. Missing scheduling leaves manual work usable. Connection-only requests stay scoped to connection verification; free preparation requires neither full OAuth nor automation.

Full workspace endpoint: https://mcp.creator.gg/mcp. Reuse the existing Creators account and business binding. Never copy local OAuth tokens into a hosted agent, shared bot instructions or prompts. If tools are available but access fails, use the returned recovery information; an outage is not a reason to install a duplicate connection.

### Connection recovery for ChatGPT Work and dots
Only use the steps below after tool discovery shows that Creators is missing or needs connection recovery. When workspace_status succeeds, skip them. Prefer a supported native connection/install control if the host exposes one. Plain-language requests can use installed tools; @creators is optional selection, not authorization.
1. In ChatGPT, open Settings, then Security and login, and enable Developer mode if needed. Custom plugins depend on your plan and workspace policy.
2. Open Plugins, select the plus button and add the Creators MCP server URL, https://mcp.creator.gg/mcp. Choose OAuth and complete the connection details and sign-in using your existing Creators account.
3. Open your personal Plugins, find Creators and install it. A saved MCP server alone does not install the plugin.
4. Return to your Work cloud chat or dot and continue the original setup request. If the host requires a new session, use its short resume handoff. Selecting @creators is optional if tool discovery needs help.

[Open Plugins](https://chatgpt.com/plugins) · [Personal Plugins](https://chatgpt.com/plugins?view=personal). If the plugin already exists, start at install/enable. If these controls are unavailable, report the plan or workspace-policy limitation. Marketplace search not finding Creators does not mean this personal MCP route is unavailable. Do not ask the user to find an unpublished directory listing.

A connection in desktop Codex, a browser login, and a ChatGPT Work plugin are separate. Opening a new cloud task does not transfer the first two. When setup begins locally, finish the hosted plugin step before asking another task to work. After the user enables it, resume with workspace_status and their already supplied choices. Do not repeatedly create tasks or ask for another copy of the same brief.

For other hosts and authentication requirements, read [Cloud agents](https://docs.creator.gg/guides/cloud-agents.md). For local agents use the matching official agent kit; local execution remains a supported choice.

## 2. Resume the company foundation
After verified access, read intelligence_get and growth_context_get when available. Follow guides/company-context to complete or resume the foundation in the customer's agent. Reuse reviewed work; do not repeat onboarding questions or overwrite another agent's changes. A free unlinked profile uses its private brief and permitted intelligence tools, with no full connection or reply automation requirement. A linked profile uses the full workspace setup even when it originated in free onboarding.

## 3. Check automation readiness once
Inspect available native scheduling tools and their documented host as a read-only capability check. Do not create a test job during base setup. Report one of: hosted scheduling available, local scheduling available with its computer requirement, or scheduling unavailable/unverified with the specific next step. Live tool discovery is the evidence for this conversation; do not treat a stale copied checklist as a permanent grant.

Prefer hosted execution for recurring agent work that needs no local files. Use the chosen host's native scheduler. Inspect its actual arguments and documented execution target before creating anything. A native cloud target or documented cloud-only tool establishes the environment; do not require an environment field that its schema does not expose. Leave the default model unspecified unless the user requests one; do not invent a requirement to read back the default model or reasoning effort. Preserve explicit model/effort choices when supported and resolve actual conflicts once. Verify Creators access in the intended host before creating or handing off a job. Creating a cloud task alone does not install Creators. Only create a new task when authorized and the destination connection is ready; enable the plugin and verify workspace_status in that task before scheduling. Reuse existing schedules and their owning connection. Local execution requires the user's explicit choice and an available computer. Never substitute a local heartbeat, OS cron, background shell loop or custom scheduler for a hosted request. When a connection needs human action, provide its exact setup step and preserve supplied choices in one private handoff; use only returned task URLs, never construct a ChatGPT URL from a Codex thread ID. For authorized setup, prefer paused job creation when supported. If creation or run-now requires an enabled job, create it with the agreed future schedule, test through the native control, inspect completion and pause on failed acceptance. A run-now acknowledgment is not a completed run. Do not require unsupported pause-at-creation or model fields. Report native job status and next run separately from successful execution.

A full workspace may then receive the optional draft-only reply offer in guides/reply-review within the same setup conversation. After opt-in, carry out that guide directly with the supplied choices; do not require another copied prompt. Other workflows apply their own opt-in and execution contracts. Ask one bundled question for genuinely unresolved choices, reuse supplied answers, and never turn routine implementation choices into repeated approvals. A missing scheduler leaves connected manual tools usable.

## Completion and recovery
Report briefly: the workspace verified in this host, whether existing company context was resumed or needs review, and native automation availability. Do not describe a future job as active until that workflow has verified it. If a step is pending, give the precise host control or account action needed. Preserve choices and private context for resumption, but never include credentials. If public Markdown retrieval fails, use documentation_get when connected or the HTML guide; do not repeatedly open empty cloud tasks to work around a retrieval error.

## Host evidence
Connection instructions and protocol tests establish a supported route, not end-to-end acceptance in every commercial host. ChatGPT Work/dot sign-in and unattended Creators execution still require testing in that host/account. The shared setup does not claim that acceptance merely from a successful local connection.

Sources checked 3 October 2026: [Installed plugins and plain-language requests](https://learn.chatgpt.com/docs/plugins), [OpenAI plugin quickstart](https://developers.openai.com/plugins/quickstart), [MCP authentication](https://developers.openai.com/plugins/build/auth), [native scheduled tasks](https://learn.chatgpt.com/docs/automations). Recheck host UI and tool schemas when they change.