Melony

How to share a Claude Managed Agent with your team

Give teammates a hosted chat for an agent built on Claude Managed Agents. Pick the environment, invite people by email and keep your Anthropic API key private.

Published

You built an agent on Claude Managed Agents. The Claude Console is a great place to build and test it, but it isn’t where your teammates should do their daily work. This guide shows how to give them a hosted chat with Melony, without sharing your API key.

Before you start

You need:

  • An agent on Claude Managed Agents, and an environment for its sessions to run in.
  • An Anthropic API key that can access both. Usage is billed to this key.
  • A Google account for you and each teammate.

Step 1: Connect the agent

  1. Open app.melony.dev and sign in with Google.
  2. Choose Connect agent and paste your Anthropic API key. Melony recognizes it as an Anthropic key.
  3. Melony lists the Managed Agents and environments the key can see. This lookup is read-only.
  4. Pick the agent and environment. If there’s only one environment, Melony selects it for you. You can also paste the agent and environment IDs.

Melony never asks for a model, system prompt or tools. Those stay on the agent.

Step 2: Check the agent’s permission policy

This step saves the most confusion later. Melony doesn’t run tools or approve tool calls. If your agent’s permission policy asks for approval before a tool runs, Melony denies the call with a message pointing to the policy, so the session doesn’t hang waiting for a click that will never come.

Before inviting anyone, allow the tools your team needs in the agent’s permission policy. Custom tools that your own client would execute also return an error in Melony, so rely on tools the agent runs itself.

Step 3: Invite teammates

Add up to three teammates by email. If they already use Melony, they join right away. If not, they join automatically the first time they sign in with that Google email. Melony doesn’t send invite emails, so let them know.

Step 4 (optional): Attach a vault

In Agent settings, owners and admins can attach an Anthropic vault by its ID and change the environment for new sessions. Melony stores only IDs and never creates or edits environments or vaults.

Step 5: Chat, then share what’s useful

Each new chat is private to the person who started it. Its creator can share it with everyone on the agent, and only the creator can unshare or delete it. Tool use and MCP tool use show inline, next to their results.

Where your data lives

  • Conversations: on Anthropic, as sessions and events of your agent.
  • Your API key: on Melony’s API host, never in a browser.
  • What Melony keeps: who’s on the agent and which person can see which session. See Security for details.

Ready? Connect your agent. Using OpenAI instead? Read how to share an OpenAI agent.

Frequently asked questions

Do teammates need access to the Claude Console?

No. They sign in to Melony with Google. Requests use the owner’s Anthropic API key on Melony’s server, and the key never reaches a browser.

Why do I need to choose an environment?

Claude Managed Agents sessions run in an environment, so Melony passes the environment ID you choose when it creates each new session. Existing sessions keep the environment they started in.

What happens if a tool call needs approval?

Melony has no approval UI. A tool call that pauses for approval is denied with a message pointing to the agent’s permission policy. Allow the tools your team needs on the agent itself.

Give your team a shared front door to your agent.

Open App — it’s freeMore guides