Skip to content

deploy-to-qoder.md

Latest commit

 

History

History
143 lines (111 loc) · 4.52 KB

deploy-to-qoder.md

File metadata and controls

143 lines (111 loc) · 4.52 KB
Raw

Deploy to Qoder

Qoder is a managed-agent platform with native memory stores and deployments, but no multi-agent primitive.

Provider configuration

providers:
  qoder:
    api_key: ${QODER_PAT}
    gateway: "https://api.qoder.com/api/v1/cloud"   # optional; this is the default
    forward_gateway: "https://api.qoder.com/api/v1/forward" # optional; derived from gateway by default
Field Required Default Description
api_key yes — Qoder personal access token. Resolve from .env with ${QODER_PAT}.
gateway no https://api.qoder.com/api/v1/cloud Qoder cloud gateway base URL.
forward_gateway no derived from gateway Qoder Forward gateway used for Template lifecycle requests.

Capabilities

Feature Tier
Environment, Vault, Skill, Agent, MCP Server, Memory Store, Deployment, Session, Identity, Channel native
Multi-Agent unsupported

A deployment run on Qoder creates a native Deployment Run and associated Session. Cron schedules run server-side.

Tool naming

Qoder uses PascalCase tool names natively (Read, Glob, Grep, WebFetch, WebSearch, Write, Edit, Bash). Write tools lowercase in config and OpenAgentPack converts them automatically when applying to Qoder — this keeps the same config portable to Bailian, Claude, and Volcengine Ark.

Function Config (lowercase) Qoder native
Read file read Read
Find files glob Glob
Search content grep Grep
Fetch web page web_fetch WebFetch
Web search web_search WebSearch
Write file write Write
Edit file edit Edit
Shell bash Bash

Minimal agent

version: "1"

providers:
  qoder:
    api_key: ${QODER_PAT}
    gateway: "https://api.qoder.com/api/v1/cloud"

defaults:
  provider: qoder

environments:
  dev:
    config:
      type: cloud
      networking:
        type: unrestricted

agents:
  assistant:
    description: "General-purpose coding assistant"
    model: ultimate
    instructions: |
      You are a helpful coding assistant.
    environment: dev
    tools:
      builtin: [read, glob, grep, web_search, web_fetch]

What Qoder uniquely supports

  • Memory stores — persistent context for an agent. See examples/qoder/with-memory/.
  • Forward Templates — declaratively materialize an agents.* declaration as a reusable Forward baseline:
agents:
  forward-assistant:
    model: auto
    instructions: You are a helpful assistant.
    environment: byoc
    tunnel: private-network
    vault: mcp-credentials
    delivery:
      qoder:
        type: forward

agents plan/apply/destroy then manage a Qoder Forward Template (tmpl_...) instead of a Managed Agent (agent_...). The default remains Managed Agent delivery when delivery is omitted.

Forward Identity represents an end user in the integrating product. Declare it once by its stable business id and select it as the project default:

defaults:
  provider: qoder
  identity: chen

identities:
  chen:
    external_id: user_456
    name: Chen

Then use the same session command to test a Forward-delivered agent:

agents session run "Hello" --agent forward-assistant

agents apply manages the declared Identity. The CLI resolves defaults.identity through state, creates a Forward Session, and routes create, send, stream, get, and archive operations through the Forward gateway. Use --identity-id idn_xxx only as a runtime escape hatch. Managed sessions keep using the Cloud gateway.

Credential-based messaging Channels are declarative too:

channels:
  support-dingtalk:
    agent: forward-assistant
    type: dingtalk
    credentials:
      client_id: ${DINGTALK_CLIENT_ID}
      client_secret: ${DINGTALK_CLIENT_SECRET}

The Channel inherits defaults.identity; the Qoder adapter resolves both remote ids and maps the generic declaration to the Forward Channel request. Feishu uses app_id/app_secret, and WeCom uses bot_id/secret. Personal WeChat is QR-only and is not supported by credential-based apply.

Forward-delivered agents still cannot be referenced by OpenAgentPack deployments; scheduled Managed Deployment runs require an Agent resource.

Next steps