Skip to content

Sessions configuration

Organization configuration is edited in Fleet Setup or through an authorized nori-sessions CLI workflow. Some deployment and experimental settings remain operator-managed and do not appear in the customer dashboard.

Key Type Default Notes
fleet size number 3 Effective capacity can be limited by the organization’s billing entitlement
lifecycle timeouts durations provider-aware defaults Ready max age, claimed idle, session inactivity, provision, and related limits are listed in the lifecycle reference
hosted sessions provider sprites | modal Last applied value Operator-managed; new hosted deployments prefer Modal, while the code fallback remains Sprites when no value has ever been applied
Key Type Default
default agent agent id claude
enabled agents list [claude]
default models per-provider map provider defaults
default skillset name none
default trigger timezone tz none
Key Values Default
commit attribution nori · none · agent nori
Slack access mode open · guarded · strict Organization setting
Slack agent reach channel-only · public-member · all-channels · direct-token channel-only
Slack DMs / file upload / file download on/off on
distribute Nori access tokens on/off on
distribute infra provider credentials on/off off

Workspace mode and repository list control what gets cloned onto each session machine; an org setup script runs on every machine at claim time.

The default skillset and other provisioning defaults carry a generation marker. When those defaults change, ready machines converge before they are used rather than silently keeping stale configuration.

AWS EC2 and Docker are selected when a dedicated broker is deployed. They are not values in the hosted sprites | modal fleet field. Modal VM Sandbox runtime and resource sizing are also operator-managed settings rather than normal Fleet Setup fields.

See supported agents and compute for the public availability boundary.

this page as markdown: /sessions/reference/config.md· index for agents: /llms.txt