Keep people and agents working on the same objects
Coconut gives you a conversation beside a workspace. Sources, assets, channel versions, and reports remain available to inspect directly, while Maris and compatible external agents work through the operations those objects support.
Build your brand space
Keep the conversation beside the work
The chat panel carries the brief and the agent’s response. The workspace panel opens the sources, assets, or results involved in the task. You can inspect the object while the conversation stays in view.
That arrangement makes agent output tangible. A draft opens as an editable asset, and a performance question can be reviewed alongside Profile. The work has a place beyond its mention in a message.
Give each kind of work an appropriate surface
Sources supports research and curation. Assets supports structured authoring and channel branches. Calendar shows publication planning. Inbox carries updates and reports, while Profile provides channel and post measurements.
Explorer exposes relationships between the objects. These surfaces let the builder move between a broad view of the brand and a specific piece of work without rebuilding its context in separate tools.
Extend the workspace through governed agent access
A compatible MCP client receives access to supported Coconut operations through an explicit grant. It can work on authorised objects while the same saved work remains accessible in the native workspace.
Human and agent asset commands share the underlying versioned model. The interfaces can differ while object identity, publishing authority, and attributable history stay with the operating system.
Explore agent access