Configure Agent Runtime
Attach a snapshot, understand activation, and review runtime and telemetry settings for an agent.
The runtime section of the agent page controls what environment the agent boots into when a new run starts.
The Most Important Runtime Setting
The most important runtime choice is the snapshot. Salambo derives the runtime environment from the selected snapshot, so this is where you decide which image, entrypoint, size, and runtime type the agent should use.
If you want the agent to run with a different image or runtime type later, the normal pattern is:
- create a new snapshot
- assign the new snapshot to the agent
- save the runtime configuration
Assign Or Change A Snapshot
- Open the agent detail page.
- Expand Runtime.
- Use Snapshot selection to choose the snapshot.
- Save the runtime configuration.
Unsaved changes stay local to the page until you save them.
Activation And Availability
An agent can be active or inactive.
- Active means it is available for new runs.
- Inactive means the configuration is still there, but new work should not be sent to it.
Use deactivation when you need a safe pause for maintenance, migration, or incident response without deleting the agent entirely.
Telemetry
The runtime section also includes telemetry controls. If your team exports OTEL data to an external observability platform, review this section when:
- a new agent is going live
- a workspace changes telemetry requirements
- troubleshooting requires confirming where traces are going
Runtime Best Practices
- keep the snapshot stable for production agents
- create a new snapshot instead of mutating a production image in place
- document the purpose of the agent clearly before multiple teammates use it
- deactivate agents instead of deleting them when you only need a temporary pause
Common Questions
Why is the agent shown in the dashboard attention list?
One common reason is that the agent has no snapshot assigned.
Can I change the runtime type directly from the agent page?
No. Runtime type is determined by the snapshot. If you need to move from one runtime family to another, create a new snapshot and attach it.