Golem Multi Instance Agent Moonbit

Phantom Agents in MoonBit

Phantom agents allow creating multiple distinct agent instances that share the same constructor parameters. Normally, an agent is uniquely identified by its constructor parameter values — calling get with the same parameters always returns the same agent. Phantom agents add an extra phantom ID (a UUID) to the identity, so you can have many independent instances with identical parameters.

Agent ID Format

A phantom agent's ID appends the phantom UUID in square brackets:

agent-type(param1, param2)[a09f61a8-677a-40ea-9ebe-437a0df51749]

A non-phantom agent ID has no bracket suffix:

agent-type(param1, param2)

Creating and Addressing Phantom Agents (RPC)

The #derive(agent) macro generates a <AgentName>Client with three constructor methods:

Example

#derive(agent)
struct Counter {
  name : String
  mut value : UInt
}

fn Counter::new(name : String) -> Counter {
  { name, value: 0 }
}

pub fn Counter::increment(self : Counter) -> Unit {
  self.value += 1
}

pub fn Counter::get_value(self : Counter) -> UInt {
  self.value
}

// --- In another agent, using the generated CounterClient: ---

// Non-phantom: always the same agent for the same name
let counter = CounterClient::get("shared")

// New phantom: creates a brand new independent instance
let phantom1 = CounterClient::new_phantom("shared")
let phantom2 = CounterClient::new_phantom("shared")
// phantom1 and phantom2 are different agents, both with name="shared"

// Retrieve the phantom ID to reconnect later
let id : @rpcTypes.Uuid? = phantom1.phantom_id()

// Reconnect to an existing phantom by its UUID
let same_as_phantom1 = CounterClient::get_phantom("shared", id.unwrap())

Scoped Variants

The generated client also includes scoped versions that automatically call drop() when the closure completes:

// Scoped non-phantom
CounterClient::scoped("shared", fn(client) {
  client.increment()
  client.get_value()
})

// Scoped new phantom
CounterClient::scoped_new_phantom("shared", fn(client) {
  client.increment()
  client.get_value()
})

// Scoped get phantom (reconnect)
CounterClient::scoped_get_phantom("shared", phantom_id, fn(client) {
  client.get_value()
})

WithConfig Variants

If the agent has @config fields, additional methods are generated:

• AgentClient::get_with_config(params..., config_fields...)
• AgentClient::new_phantom_with_config(params..., config_fields...)
• AgentClient::get_phantom_with_config(params..., phantom_id, config_fields...)

Querying the Phantom ID

From a Client Reference

Use the phantom_id() method on any client instance:

let phantom = CounterClient::new_phantom("shared")
let id : @rpcTypes.Uuid? = phantom.phantom_id()
// Returns Some(uuid) for phantom agents, None for non-phantom agents

HTTP-Mounted Phantom Agents

When an agent is mounted as an HTTP endpoint, you can set mount_phantom to true to make every incoming HTTP request create a new phantom instance automatically:

#derive(agent)
#derive.mount("/api")
#derive.mount_phantom(true)
struct RequestHandler {
  // ...
}

fn RequestHandler::new() -> RequestHandler {
  { .. }
}

#derive.get("/status")
pub fn RequestHandler::handle(self : Self, input : String) -> String {
  // ...
  ""
}

Each HTTP request will be handled by a fresh agent instance with its own phantom ID, even though all instances share the same (empty) constructor parameters.

Key Points

• Phantom agents are fully durable — they persist just like regular agents.
• The phantom ID is a standard UUID.
• new_phantom generates the UUID internally.
• get_phantom is idempotent: calling it with the same UUID and parameters always returns the same agent.
• Phantom and non-phantom agents with the same constructor parameters are different agents — they do not share state.
• Always call client.drop() when done, or use the scoped_* variants which handle this automatically.