Keep your marketing context as models evolve
Language models provide the reasoning. Coconut gives that reasoning a working brand, defined operations, and somewhere durable for the result. Model choice can change while your sources, assets, and channel versions remain in your workspace.
Build your brand space
Connect model reasoning to real marketing work
A useful marketing agent needs to understand the brief and act on the work. Maris combines configured model routes with Coconut’s brand context and tool contracts, so a conversation can lead to a structured asset or a specific performance query.
The model proposes the next operation. Coconut’s runtime and domain services determine whether that operation is allowed and what it changes. This gives reasoning an execution boundary.
Make model behaviour an explicit engineering choice
A route identifies the provider, deployment, and adapter that an invocation uses. The runtime checks the route’s supported capabilities, including tool use, before admitting it. Model and usage records keep the invocation identifiable.
This separation lets the operating system evolve its model setup without changing the identity of your assets or the meaning of its marketing operations. A new model still works within the same workspace and permission boundaries.
Use another agent with the work you already have
You can also connect a compatible external agent through MCP and use that client’s model settings. Its granted Coconut operations can read saved context and work on supported assets.
Your working material stays in Coconut. Changing the client does not require recreating the brand workspace, and access remains limited to the scope and capabilities you grant.
Explore agent access