Overview - Qoder

Qoder Cloud Agents is a fully managed runtime for AI agents. You don't have to build your own agent loop, manage tool execution sandboxes, or handle long-lived connections. Define an Agent and start a Session via API, and complex tasks run in the cloud while results stream back in real time.

Choose an integration method

Choose whether to use Cloud Agents in an AI tool or integrate it into your own application. These links take you directly to installation and configuration instructions.

Plugin

Install the Plugin in New Qoder to use Skills, an MCP Connector, and shortcuts together. It reuses your current login session.

Skill

Install in an AI tool that supports Skills. The Skill prefers available MCP tools and calls the HTTP API when MCP is unavailable.

MCP

Connect Cloud Agents to an MCP-compatible Agent. Standalone configuration currently uses a PAT through a static Authorization header.

SDK

Integrate your service with the TypeScript, Python, or Go SDK. The official open-source repository also provides Skill and MCP resources.

If your tool does not offer a native Plugin yet, install the Skill and configure MCP separately. If MCP is unsupported, follow the Skill instructions to use the HTTP API. Open the Cloud Agents website, select the tab for your integration method, and copy the installation or configuration commands.

Core Concepts

Concept	Description	Analogy
Agent	A reusable configuration template that defines the model, system prompt, and tool set	"Job description"
Environment	The container runtime for a Session, including dependency and startup configuration	"Desk and toolbox"
Session	A concrete instance of a conversation or task execution	"A specific work session"
Event	The real-time event stream produced by a Session	"Live progress feed"

Workflow

Define an Agent

Specify the model, system prompt, and available tools.

Configure an Environment

Choose the container type, preinstalled dependencies, and setup script. New accounts do not have a pre-provisioned default environment — you must first POST /api/v1/cloud/environments to create one.

Start a Session

Bind an Agent and Environment to create a runtime instance.

Send message + Stream events

Send a user.message to the Session and stream the Agent's thinking, messages, and status changes over SSE (or fetch them via polling).

Verify Connectivity

# Verify the PAT or SAT and list all Agents
curl -s https://api.qoder.com/api/v1/cloud/agents \
  -H "Authorization: Bearer $QODER_ACCESS_TOKEN"

A successful response looks like:

{
  "data": [],
  "first_id": null,
  "last_id": null,
  "has_more": false
}

When to Use Cloud Agents

Long-running asynchronous tasks — code review, large refactors, automated test generation.
API integration — embed agent capabilities in backend services without maintaining a runtime.
Batch processing — fan out parallel Sessions to handle bulk requests.
Scheduled jobs — combine with a scheduler to run periodic inspections or reports.

Authentication

Every API request must include the following header:

Header	Value	Description
`Authorization`	`Bearer <PAT or SAT>`	Personal Access Token (PAT) or Service Account Token (SAT)

Personal users can create a PAT under "Settings → Personal Access Tokens" in the Qoder console. A Service Account must exchange an SA API Key for a short-lived SAT through the Service Token Exchange endpoint. See Authentication.

Pagination

List endpoints use cursor-based pagination with this response shape:

{
  "data": [...],
  "first_id": "agent_019e451902fe7a2ca42c2dfc62d9320e",
  "last_id": "agent_019e45369b3379e18bfaf59b3aad2fc9",
  "has_more": true
}

Use the after_id and before_id query parameters to page through results.

FAQ

Q: Can I use Cloud Agents and the Qoder CLI at the same time? A: Yes. The CLI is best for local interactive development; Cloud Agents is best for automation and integration. They complement each other. Q: How many Sessions can a single Agent run concurrently? A: There is no hard limit. The same Agent configuration can back many active Sessions simultaneously. Q: How is data secured? A: Each Session runs in an isolated container sandbox; Sessions cannot reach one another. Data is wiped when the environment is destroyed.

Next Steps

Quickstart — get your first Cloud Agent running in five steps.
Defining an Agent — dive deeper into Agent configuration.
Cloud Environments — configure the runtime environment.
Sessions — manage Session lifecycle.

​Choose an integration method

Plugin

Skill

MCP

SDK

​Core Concepts

​Workflow

​Verify Connectivity

​When to Use Cloud Agents

​Authentication

​Pagination

​FAQ

​Next Steps

Choose an integration method

Core Concepts

Workflow

Verify Connectivity

When to Use Cloud Agents

Authentication

Pagination

FAQ

Next Steps