---
title: Supported agents and compute
description: Current support matrix for coding agents, credential methods, interaction modes, and compute backends in Nori Sessions.
status: verified
sidebar:
  order: 3
---

This page separates what Nori Sessions can launch today from agents and compute
backends that are local-only, deployment-specific, gated, or no longer
supported.

## First-class Sessions agents

These agents appear by default in the managed Sessions product:

| Agent | Sessions support | Credential configuration | Interactive terminal |
|---|---|---|---|
| Claude Code | First-class, preinstalled | Anthropic API key, Claude OAuth, or setup token | Yes |
| Codex | First-class, preinstalled | OpenAI API key or Codex OAuth | Yes |
| Cursor Agent | First-class, preinstalled | Cursor API key | No, ACP sessions only |
| OpenCode | First-class, installed when needed | Compatible API base URL, API key, and model | No, ACP sessions only |
| pi-acp | First-class, installed when needed | Compatible API base URL, API key, and model | No, ACP sessions only |

"First-class" means the agent is visible and launchable in the default product
configuration. It does not mean every binary is baked into the base image.

## Other registry agents

The broker can consume additional safe package-based entries from the public ACP
registry when the ACP registry feature is explicitly enabled. Those agents are
not part of the default customer support set, may install at launch, and do not
automatically receive Nori-managed credential schemas.

An agent shown as **available** in registry metadata is informational and cannot
be launched until it has a supported distribution and credential path.

## Gemini support

Gemini was removed from managed Sessions and is rejected by the broker. Do not
select Gemini for a Sessions fleet, session, or trigger.

Gemini CLI remains a built-in option in the separate, open-source [Nori
CLI](/cli/guides/agents/). Local CLI support does not imply managed Sessions
support.

## Hosted compute

| Backend | Customer status | Selection boundary |
|---|---|---|
| Modal | Preferred for new hosted fleets | Applied to a hosted organization fleet |
| Sprites | Supported legacy backend | Existing hosted organization fleets |

Provider changes are fleet-level operations that drain and rebuild the pool.
They are not per-session settings.

## Deployment-specific compute

| Backend | Status | Intended use |
|---|---|---|
| AWS EC2 | Supported for dedicated BYOC deployment | Private EC2 session machines inside customer-controlled AWS infrastructure |
| Docker | Supported for local deployment | Local worker containers on a prepared image and private network |
| E2B | Internal alpha only | Nori development, demo, and test environments with an explicit feature flag |

AWS EC2 and Docker are selected when the broker is deployed. They do not appear
as hosted self-service fleet toggles. E2B is not a general customer option.

## Model availability

Nori maintains a model catalog for each first-class agent and validates requested
models against it. Actual availability can still depend on the connected account,
subscription, region, or upstream provider policy.

When a requested model is invalid, the broker falls back through the agent and
fleet defaults rather than treating a model name as an arbitrary string.

## How this page is verified

This matrix was checked against the Sessions agent registry, model catalog, and
compute-provider factory on September 14, 2026. Generated lifecycle and provider
references record the exact source revisions used by this documentation build.

For architecture details, continue to [fleets, brokers, and
compute](/sessions/concepts/fleets-and-providers/). For setup, see [integrations
and credentials](/sessions/guides/integrations/).
