Agent setup

Connect your agent

Choose your agent and copy its setup prompt. Connected agents can use the same saved business context and growth plan.

Add an agent

Each agent has a separate connection to this workspace’s tools, business context and plan.

Already connected?

Where do you use your agent?

Local agentRuns on your computerCloud agentRuns in a hosted service

Paste this prompt once into your chosen agent.

Agent setup prompt

Set up Creator Agents for Claude Code. Use one continuous setup in this conversation. First discover the available Creator Agents tools and call workspace_status in the intended host. Use workspace_status.data.workspace.name as the connected location/workspace label in greetings and status messages. Prefer the workspace name alone; when a verified human name is available, a greeting such as Hey Name from Workspace is also suitable. Do not substitute the authorizing user or email sender for the workspace, invent a personal Account label, or rename the native location. If it succeeds, skip installation and authorization and continue with saved company context. Do not require an @creator-labs 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. During full setup, read https://docs.creator.gg/guides/agent-refresh.md and establish this public routing rule through the host's supported durable instruction or owned-skill mechanism: creator-labs-routing/1: For business context, growth planning, short links or URL masking, contacts, email and social tasks, discover available Creator Labs / Creator Agents tools before choosing an external service, unless I explicitly choose that service. Use the host's actual tool search, load the returned schema and verify workspace_status. A short initial connected-services list or a legacy bridge label is not the full catalogue. Follow live guides for the requested task. Claim only actual tool results and available capabilities. Preserve unrelated instructions, user overrides, working connections and schedules. Verify persistence by readback; if the host cannot save and read it, provide the exact rule for the user and report routing pending. A chat acknowledgment is not persistence. Connection-only checks do not change host instructions. If tools are still unavailable and this local client needs installation, use the official instructions at https://agents.creator.gg/downloads/agent-kit/v1/claude-code.md and manifest at https://agents.creator.gg/downloads/agent-kit/v1/manifest.json. Verify all required download checksums and the actual host/profile before installing the four skills or configuring https://mcp.creator.gg/mcp. Preserve customized skills, instructions, permissions and unrelated settings. Reuse existing native authentication controls before adding any connection. I will complete sign-in and consent myself; do not automate login or ask for credentials. After authorization, verify workspace_status and continue this setup. Complete or resume the company foundation pass in https://docs.creator.gg/guides/company-context.md using this agent and its available research tools. Website onboarding supplies initial direction; this first setup in my own agent develops the full foundation. Read current intelligence and the saved onboarding brief/plan when available, or use the supplied private context. Reuse existing work and corrections; adding another agent must not restart a completed foundation. Research relevant gaps, then present a concise first pass covering vision, mission, customer problem, ICP and buying situation, customer job, positioning and differentiation, current capabilities versus future ambition, releases, voice, evidence and open questions. Draft supported proposals before asking targeted questions; do not invent my ambition, product availability or customer proof. Save the foundation and review progress through permitted intelligence tools and verify by reading back. Without a live connection, retain a private snapshot in this host's supported storage and report sync pending. Keep proposals distinct from confirmed facts. Then review the existing growth plan against the enriched context and continue the next requested task without repeating completed work. Report foundation drafted or reviewed and context saved or sync pending separately from connection success. Setup permits maintaining this private company context, not sending, publishing, scheduling, editing contacts or enabling automations. Browser access is optional for Creator Agents tools; a hosted browser has a separate session from my local browser. For a full connected Creator Platform workspace only, after the company foundation and social account check, read guides/reply-review, guides/social-writing and social_replies_settings. Reuse an existing schedule; adding another agent must not create a duplicate. Offer optional comment-reply drafts once, as one short proposal: hosted execution, all currently supported connected accounts, daily at 9am in the user's established timezone, with hourly, every 12 hours or manual available. Reuse choices already supplied in this conversation or saved settings. Ask one bundled question only for the opt-in and genuinely missing or conflicting details; do not repeat answered questions. An explicit request to set up automated drafts already supplies opt-in. Only after the user opts in, establish or reuse the private social reply profiles using guides/social-writing, then complete setup using the guide in this conversation; do not send the user back to copy a separate reply-setup prompt. This authorizes drafting only; publishing requires approval of the exact reply. Free preparation-only users do not get this offer. A connection-only request stays within connection scope. Reuse the shared base setup at guides/agent-setup for connection readiness and native scheduler compatibility.

About browser access

Use your saved context

Ask your agent to read your saved business context and growth plan before starting work. It can then use updates from you and your other agents.

Manage access and check last use in Agents. Revoke one connection without disconnecting the others.

What the setup prompt does

Your agent checks its connection, reads your saved business context and researches missing details. You review its suggestions before it saves them. If setup is complete, it resumes from your saved context.

With Creator Platform access, you can also ask for daily comment reply drafts. Your agent needs a supported scheduler. You review each reply before it is sent.

Setup guide Connection requirements and troubleshooting

Browser access is separate

Creator Agents tools work without browser control. Some tasks need a platform screen. Your agent must check whether it can open that screen and is signed in to the right account.

A cloud browser has a separate sign-in session. If your agent cannot use the required screen, it will tell you what to do there.

Agent documentation

Find guides for business context, contacts, email, social publishing and connection recovery. Your agent can search these guides through its Creator Agents tools.

Read the agent documentation

Connect your agent

Choose your agent and copy its setup prompt. Connected agents can use the same saved business context and growth plan.

Add an agent

Each agent has a separate connection to this workspace’s tools, business context and plan.

Already connected?

Where do you use your agent?

Local agentRuns on your computerCloud agentRuns in a hosted service

Paste this prompt once into your chosen agent.

Agent setup prompt

Set up Creator Agents for Claude Code. Use one continuous setup in this conversation. First discover the available Creator Agents tools and call workspace_status in the intended host. Use workspace_status.data.workspace.name as the connected location/workspace label in greetings and status messages. Prefer the workspace name alone; when a verified human name is available, a greeting such as Hey Name from Workspace is also suitable. Do not substitute the authorizing user or email sender for the workspace, invent a personal Account label, or rename the native location. If it succeeds, skip installation and authorization and continue with saved company context. Do not require an @creator-labs 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. During full setup, read https://docs.creator.gg/guides/agent-refresh.md and establish this public routing rule through the host's supported durable instruction or owned-skill mechanism: creator-labs-routing/1: For business context, growth planning, short links or URL masking, contacts, email and social tasks, discover available Creator Labs / Creator Agents tools before choosing an external service, unless I explicitly choose that service. Use the host's actual tool search, load the returned schema and verify workspace_status. A short initial connected-services list or a legacy bridge label is not the full catalogue. Follow live guides for the requested task. Claim only actual tool results and available capabilities. Preserve unrelated instructions, user overrides, working connections and schedules. Verify persistence by readback; if the host cannot save and read it, provide the exact rule for the user and report routing pending. A chat acknowledgment is not persistence. Connection-only checks do not change host instructions. If tools are still unavailable and this local client needs installation, use the official instructions at https://agents.creator.gg/downloads/agent-kit/v1/claude-code.md and manifest at https://agents.creator.gg/downloads/agent-kit/v1/manifest.json. Verify all required download checksums and the actual host/profile before installing the four skills or configuring https://mcp.creator.gg/mcp. Preserve customized skills, instructions, permissions and unrelated settings. Reuse existing native authentication controls before adding any connection. I will complete sign-in and consent myself; do not automate login or ask for credentials. After authorization, verify workspace_status and continue this setup. Complete or resume the company foundation pass in https://docs.creator.gg/guides/company-context.md using this agent and its available research tools. Website onboarding supplies initial direction; this first setup in my own agent develops the full foundation. Read current intelligence and the saved onboarding brief/plan when available, or use the supplied private context. Reuse existing work and corrections; adding another agent must not restart a completed foundation. Research relevant gaps, then present a concise first pass covering vision, mission, customer problem, ICP and buying situation, customer job, positioning and differentiation, current capabilities versus future ambition, releases, voice, evidence and open questions. Draft supported proposals before asking targeted questions; do not invent my ambition, product availability or customer proof. Save the foundation and review progress through permitted intelligence tools and verify by reading back. Without a live connection, retain a private snapshot in this host's supported storage and report sync pending. Keep proposals distinct from confirmed facts. Then review the existing growth plan against the enriched context and continue the next requested task without repeating completed work. Report foundation drafted or reviewed and context saved or sync pending separately from connection success. Setup permits maintaining this private company context, not sending, publishing, scheduling, editing contacts or enabling automations. Browser access is optional for Creator Agents tools; a hosted browser has a separate session from my local browser. For a full connected Creator Platform workspace only, after the company foundation and social account check, read guides/reply-review, guides/social-writing and social_replies_settings. Reuse an existing schedule; adding another agent must not create a duplicate. Offer optional comment-reply drafts once, as one short proposal: hosted execution, all currently supported connected accounts, daily at 9am in the user's established timezone, with hourly, every 12 hours or manual available. Reuse choices already supplied in this conversation or saved settings. Ask one bundled question only for the opt-in and genuinely missing or conflicting details; do not repeat answered questions. An explicit request to set up automated drafts already supplies opt-in. Only after the user opts in, establish or reuse the private social reply profiles using guides/social-writing, then complete setup using the guide in this conversation; do not send the user back to copy a separate reply-setup prompt. This authorizes drafting only; publishing requires approval of the exact reply. Free preparation-only users do not get this offer. A connection-only request stays within connection scope. Reuse the shared base setup at guides/agent-setup for connection readiness and native scheduler compatibility.

About browser access

Use your saved context

Ask your agent to read your saved business context and growth plan before starting work. It can then use updates from you and your other agents.

Manage access and check last use in Agents. Revoke one connection without disconnecting the others.

What the setup prompt does

With Creator Platform access, you can also ask for daily comment reply drafts. Your agent needs a supported scheduler. You review each reply before it is sent.

Setup guide Connection requirements and troubleshooting

Browser access is separate

Creator Agents tools work without browser control. Some tasks need a platform screen. Your agent must check whether it can open that screen and is signed in to the right account.

A cloud browser has a separate sign-in session. If your agent cannot use the required screen, it will tell you what to do there.

Agent documentation

Find guides for business context, contacts, email, social publishing and connection recovery. Your agent can search these guides through its Creator Agents tools.

Read the agent documentation

Connect your agent

Add an agent

Use your saved context

What the setup prompt does

Browser access is separate

Agent documentation

Loading your workspace

Connect your agent

Add an agent

Use your saved context

What the setup prompt does

Browser access is separate

Agent documentation