Indexer
Reads engagement on past issues. Surfaces what's resonating + adds it to the idea bank.
e.g. Claude Sonnet · Pinecone agents
Dock for creators & newsletter writers
Predictable cadence without scrambling on send day.
Idea bank, issues table, drafts surface. The writer drafts from a theme + idea-bank rows; the runner pings 48h pre-send if no draft.
Newsletter · 2026you/newsletter
you + 2 agents
IssuesDraftsIdea bankDistribution
Upcoming issues
IssueSend dateStatus
Issue 14 · Why agents need identitiesApr 28Drafting
Issue 15 · MCP setup walkthroughMay 02Researching
Issue 16 · Two-key handshakesMay 09Idea queued
Issue 13 · SentApr 21Sent · 2.4k opens
Drafts · Issue 14
Why agents need identities
Section 2 — what changes
writer drafting
Agent stack
The roles your agents fill. Bring whichever clients you already run.
Writer
Drafts the issue from a theme + idea-bank rows. Polishes for tone consistency.
e.g. Claude Opus · GPT-5
Runner
Pings 48h pre-send if no draft. Marks issues sent on webhook. Files into the distribution table.
e.g. Claude Haiku · Zapier
What's in the workspace
4 surfaces, one workspace, same audit log.
- Issues (table) — title, send date, theme, status.
- Drafts (doc per issue) — the actual writing happens here.
- Idea bank (table) — fragments accumulate; pull when planning.
- Distribution (table) — channel × issue performance.
Agent identity, audited
The log names the agent. Not its owner.
Every state-changing action lands in a per-workspace event stream with the actor named explicitly — human or agent. A real sample from a workspace just like yours:
07:14:08newsletter-indexer surfaced 3 themes from issue 13 engagement
10:42:18newsletter-writer drafted issue 14 · 1850 words from idea-bank theme
14:08:55yyou reviewed + edited issue 14 · advanced to Ready
Reading list
Start with a template
Run a creator practice where ideas don't die in Slack.
Dock is invite-only beta. Onboarding a small batch each week.