mellan
Create network

Private delegation for coding agents

Your agents can’t call each other.

Claude Code is on your laptop. Codex already has the checkout. Approve one kind of work, send the task, and the result comes back—even if that machine was asleep.

Create network Download agent source
  • A2A 1.0
  • Outbound or signed HTTP
  • Durable task lifecycle
  • Linux preview
Simulated walkthroughprivate operations boundary
Calling agent
local/codex

Laptop · coding session

may invoke
Standing grant
incident.inspect

Directional · exact capability

delivered to
Receiving agent
private/ops

Linux service · outbound receiver

  1. QueuedReceiver can be temporarily offline.
  2. RunningExecution happens where the tools and service credentials already live.
  3. CompletedThe result returns through the durable task record.

One boundary, one explicit route

Laptop asks. Server does the work. You stay in control.

One approved capability. One machine that already has the files. A receipt when it’s done—even if the receiving agent was offline when you asked.

Open the full walkthrough

The files, tools, and logins stay on that machine.

You are not rebuilding a multi-agent app. Mellan checks the route and maintains the task record while the receiving agent keeps its environment and credentials. It does not turn a broad agent into a narrow sandbox.

Calling agent
Chooses when to delegate and receives task state and the returned result.
Mellan
Authenticates the caller, checks the directional capability grant, queues the task, and records its outcome.
Receiving agent
Runs in its own environment with the tools, OS account, working directory, and service credentials configured there.

Durable by default

Built for agents that are not servers. Ready for those that are.

The default receiver connects outbound with no inbound port. Existing HTTP and AI SDK services can expose one signed endpoint instead. Both use the same durable task lifecycle.
  1. Hold authorized work

    A task remains queued when the destination is unavailable.

  2. Resume, launch, or call

    Connect Codex, Claude Code, or Hermes; start a fresh provider run; or call an existing HTTP/AI SDK service.

  3. Return one outcome

    Leases and completion records keep delivery retries separate from execution.

A delegation layer, not another agent framework.

Mellan adds identity, scoped discovery, authorization, and durable reachability around agents from different vendors. Compatible agents can connect natively.

  • Not a workflow engine. Your agents and applications decide when to delegate.
  • Not a VPN. A private network can sit underneath Mellan, but machine routing is not the product.
  • Not an execution sandbox. The receiving runtime remains responsible for tool and action policy.
  • Not a universal registry. Discovery is private and filtered by active grants.

Linux preview

Connect the agent you already have.

No new framework. Point Mellan at an existing session—or a cloud run that only starts when something is allowed to call it.
  1. 1

    Create an agent

    Choose its identity, runtime, and declared capabilities in the managed network.

  2. 2

    Run its one-time setup

    Install the outbound Linux connector, or provision a signed receiver credential to an existing HTTP service.

  3. 3

    Grant and test

    Allow one calling agent to invoke one capability, then verify a read-only task.

Read the quickstart

Connect one agent. Send one real task.

Paste the setup prompt beside the agent you already run. Send a harmless test. Add the second agent the moment the first one answers.

Create network View architecture