Connect the accounts you run today. Agents listen, ideate, produce, publish and learn on them — and you can drive the whole thing from Claude, ChatGPT or Codex, without opening a dashboard.
Private beta · No card · We open workspaces in small batches
Ideas
Thread: the three integrations we shipped this month — and the one we killed.
The morning routine post, in the version that isn't aspirational.
Consistency beats intensity. Eight weeks, one habit, what changed.
Draft
Three integrations shipped this month. We killed a fourth.
The one we killed is the interesting one — it worked, and it still made the product worse.
Thread on how we decided ↓
Activity
The idea is born in a chat and dies there. Your assistant writes the post and stops. It doesn't publish, doesn't schedule, doesn't measure — and tomorrow it has forgotten what it wrote.
Schedulers are systems of record. They store what you already wrote. They don't watch the accounts, don't decide what comes next, and don't learn from what went out.
So the loop never closes — and the work grows by a whole person every time you add a network.
Feed
3 ideas waitingThread: the three integrations we shipped this month — and the one we killed.
The morning routine post, in the version that isn't aspirational.
Consistency beats intensity. Eight weeks, one habit, what changed.
01
Connect Magik to Claude, ChatGPT, Codex or OpenClaw over MCP. Ask for the week's numbers, ask it to schedule three posts for Tuesday — and it happens on your real accounts, without a dashboard.
@nicoreis
X (Twitter)
02
Your personal account and the company's, on one editorial line. Open the Feed on Monday and the week is already proposed, in your voice, grounded in what the company actually shipped.
@lunacampos
9
posts · 7d
@nicoreis
X (Twitter)
12
posts · 7d
@valmoraes
X (Twitter)
7
posts · 7d
03
One idea, reshaped per network, with its own cadence on each account. Metrics come back into one place and feed the next idea instead of sitting in four dashboards.
How it works
Agents run your accounts end to end, every day. The gate is yours: nothing reaches an audience before a person says yes.
Signals
LiveSomeone quoted last week's thread and asked what it costs.
Inbound question about the integration that shipped Monday.
Replies up on the changelog post. Saves flat.
Changelog, Aug 14 — three integrations shipped, one killed.
Every signal lands in memory before an agent writes a word.
Feed
3 waitingThread: the three integrations we shipped this month — and the one we killed.
The morning routine post, in the version that isn't aspirational.
Consistency beats intensity. Eight weeks, one habit, what changed.
Approve, edit or kill. The queue never moves on its own.
Task · Changelog thread
In reviewDraft · @nicoreis' voice
Three integrations shipped this month. We killed a fourth.
The one we killed is the interesting one — it worked, and it still made the product worse.
Thread on how we decided ↓
Variants
One idea, one voice, a shape per network.
Queue
auto@nicoreis · X
Today · 09:10
@lunacampos · IG
Today · 18:30
@valmoraes · X
Tomorrow · 07:00
@nicoreis · X
Thu · 09:10
Queue, timezone and rate limits handled — and an audit trail.
What we learned
Last 7 daysChangelog threads pull replies. Feature posts don't.
The unglamorous version of the routine post travelled.
Captions lose the scroll after the third line.
Saved as memory. The next idea is written knowing this.
Agents arrive paused.
Every public action defaults to copilot: the agent proposes, a human approves — ideas in the Feed, drafts in Task review, and once more at the publish gate. Autonomy is earned per account. It is never the default. The same gates apply to an agent driving Magik over MCP.
The product
Five names, each one a screen rather than a marketing concept.
One connected account, one Profile. Its handle, its voice, its cadence, its metrics — inheriting from your Brand unless you override it per account.
What you and your company know: product, launches, positioning, objections, what already got tired. It's where the agent gets something to say. Suggested memories never activate themselves.
The queue of ideas waiting for you. Approve, edit or kill.
The pipeline a human and an agent share: draft, per-network variants, review, publishing.
Per Profile, per network, per post — so you can tell which account is actually working, and so the next idea is written knowing it.
For agents
Magik ships an MCP server. Connect it to Claude, ChatGPT, Codex or OpenClaw and they drive the product in your words — the same domain, the same permissions, the same approval gates as the UI.
MCP is not an enterprise upgrade. It's the cheapest way into the product, so it ships on the entry plan too — what scales with the plan is the call ceiling, not the access.
The credential is issued per user, scoped to a workspace, expires and can be revoked. Every tool declares the permission it needs, and the agent gets exactly what you can do — never more.
A post created by an external agent is born pending, exactly like one created in the UI. There is no privileged path: if a human hasn't approved it, it hasn't been published.
In private beta alongside the app. Waitlist workspaces get it on day one.
Trust
Magik does not manufacture creators. Every Profile is the handle of a real person or a real company — yours — and what's agent-native is the operation of it.
@nicoreis
X (Twitter)
You connect it, you disconnect it, and you keep the audience either way. Magik doesn't own the account, doesn't hold the followers and doesn't stand between you and the network.
Tone, audience, taboos, CTAs, the things to say and the things never to say — configured per account, inherited from your Brand, versioned. Edit it and every future draft moves with it.
No bought followers, no bought engagement, no account networks inflating a number. Real accounts posting inside each network's rules, with a person approving every public post.
X (Twitter)
Live — connect, publish, DMs
DMs live · connect in polish
LinkedIn · TikTok
Next
Connect an account and it becomes a Profile. Publishing, metrics and DMs run on our infrastructure — nothing for you to set up.
Not an AI influencer. Not a deepfake.
We don't generate a face, we don't clone a voice, and we don't invent a creator who doesn't exist. If you're looking for a synthetic persona, this isn't the product — the accounts here belong to real people, and that's the point.
Before you ask
Join the waitlist. We open in batches, and we set up the first account with you.
No card. Nothing is published from your accounts until you connect them and approve the first post yourself.
Assisted setup
We set up the first account with you — connection, Brand, voice, first week in the Feed.
Direct line
While the beta is small, you talk to the people building it.
MCP on day one
Waitlist workspaces get the MCP server as soon as they're opened.
