DistributionOSAbout DistributionOS
Distribution memory for Codex or Claude Code.
DistributionOS keeps durable marketing context for each subscribed app so Codex or Claude Code can work from the product, audience, proof, and history instead of starting every marketing task from a blank prompt.
Canonical identity
These are the stable facts owned pages, public profiles, and agent answers should use when they describe the product.
- Canonical name
- DistributionOS
- Official domain
- distributionos.dev
- Category
- Distribution memory and marketing context for Codex and Claude Code
- Primary audience
- Indie app builders who work with Codex or Claude Code
- Current availability
- Open beta
How the current workflow works
- 01
A Brain Doc keeps the app’s product, audience, positioning, proof, and guardrails together.
- 02
Codex or Claude Code reads that context before planning or creating marketing work.
- 03
DistributionOS saves research, reviewable briefs, image direction, and tracking requirements.
- 04
The connected Codex or Claude Code agent implements and publishes through the builder’s existing repo or CMS.
- 05
Shipped URLs and analytics signals return to DistributionOS so later work can build on what happened.
What it is
A hosted context, research, handoff, analytics, and memory layer for Codex and Claude Code. It is organized per app and keeps the connection between the context an agent used and the work that shipped.
Those are the only coding-agent clients currently tested and supported. Other MCP clients may be compatible at the protocol level, but they are not yet part of the supported product.
What it is not
It is not a generic AI content writer, a promise of hands-off growth, or a replacement for the builder’s repo and publishing tools. Capabilities still being verified remain clearly labeled.
Give your agent durable distribution context.
Questions about the product or its identity? Email support@distributionos.dev.