chieflab/activate · workspace not created yetv0.3 · MCP
// preview before activate
See ChiefLab launch your product, then activate.
Paste your product URL. We run the actual launch loop in a shared sandbox — same 13 skills, same per-channel drafts your agent would render. If you like what you see, create a workspace key and your IDE agent picks up where the preview left off.
running preview · real model calls
selecting skills (icp / positioning / per-channel / measurement)drafting LinkedIn · X · HN · Reddit · email · landing hero · Product Huntrendering inline (this is what your IDE agent would show in chat)
Preview · what your agent would render in chat
// sandbox is read-only — nothing publishes. With your own workspace, the same drafts come back wired to approval-gated publish actions.
↓ Activate to make this realCreate a workspace key, paste it into your MCP config, and your IDE agent picks up where this preview ended — approval-gated publish, measurement, memory.
Preview failed
You can still — sandbox is decorative.
01 · runtime02 · workload03 · key
agent_runtime
Which agent are you using?
We will show the right config after your workspace key is created.
target_workload
What's your agent building?
So the launch loop picks the right channels. One click.
comms_channel · optional
Create your workspace
Email is optional — only used for run digests + critical security alerts. Leave blank to stay anonymous.
rate-limit: 5 keys / ip / hour · no card · free tier
// WORKSPACE CREATED
Workspace key created
Copy once — never shown again. Paste into your MCP config (snippet below) and your agent can call ChiefLab.