golem-multi-instance-agent-moonbit

Use the generated client method new_phantom, which appends a random phantom UUID to the agent identity. Each call creates a distinct durable instance even when constructor parameters are identical, and get_phantom reconnects using a known UUID.

A phantom agent is a Golem agent whose identity includes an extra phantom UUID appended in square brackets, like agent-type(param)[uuid]. This lets many independent instances share the same constructor parameters without sharing state.

Call phantom_id() on the client to get its UUID, then use get_phantom with the same parameters and that UUID. The call is idempotent, so the same UUID and parameters always return the same agent.

Yes. Set mount_phantom to true on an HTTP-mounted agent so every incoming request is handled by a fresh phantom instance with its own UUID, even when all instances share the same constructor parameters.

No. Phantom and non-phantom agents with the same constructor parameters are different agents and do not share state. Phantom agents are fully durable and persist just like regular agents.

Use scoped, scoped_new_phantom, or scoped_get_phantom when you want the client to call drop() automatically after the closure completes. This avoids manually managing client lifecycle for short-lived interactions.