golem-stateless-agent-moonbit

Use #derive.agent("ephemeral") on your struct instead of the default #derive.agent. Each invocation then calls new() to create a fresh instance, executes the method, and discards the instance entirely.

Durable agents persist state across calls and replay their oplog for recovery, while ephemeral agents get a fresh instance per invocation with no replay or persistence. An ephemeral counter returns 1 on every increment call instead of accumulating.

Use ephemeral agents for stateless HTTP APIs, data transformation, validation services, and webhook forwarding where calls are independent. Avoid them for counters, shopping carts, workflow orchestrators, or any logic depending on previous calls.

Yes, ephemeral agents can call other agents via RPC, make HTTP requests, and use all Golem APIs. Only the state persistence and replay behavior changes; the identity model based on constructor parameters remains the same.

That is the intended behavior: ephemeral agents discard memory after each invocation completes, so every call starts from a clean new() constructor. If you need state across calls, switch to the default durable agent mode.