Skip to content

Latest commit

History

History
75 lines (55 loc) · 3.99 KB

File metadata and controls

75 lines (55 loc) · 3.99 KB

OpenAgentPack Documentation

English files are the canonical source for behavior; translated files use a .zh-CN.md suffix and describe the same public contract. This index organizes documentation by what you want to do.

Getting started

DocWhat's inside
Getting startedShortest path from install to a running session. (中文:getting-started.zh-CN.md)

Concepts

Mental model behind plan and apply — no field tables.

DocWhat's inside
Agents as codeWhy a declarative agents.yaml instead of console clicks.
ResourcesThe resource types OpenAgentPack manages and their dependencies.
State and driftThe three sources of truth and how drift is reconciled.
Sessions and deploymentsInfrastructure resources vs. runtime runs.

Guides

Task-oriented, with steps and verification.

DocWhat's inside
Configure an agentBuild an agents.yaml from minimal to full stack.
Deploy to BailianBailian (Aliyun AgentStudio) setup and notes.
Deploy to QoderQoder-specific setup and notes.
Use BYOC environmentsConnect Qoder sessions to administrator-provisioned self-hosted environments and private-network tunnels.
Deploy to ClaudeClaude-specific setup and notes.
Deploy to Volcengine ArkVolcengine Ark (Managed Agents) setup and notes.
Use skillsAuthor and attach reusable capability modules.
Use MCP and vaultsConnect external tool servers and manage their credentials.
Multi-providerDeploy the same agent to more than one provider.
Run sessionsStart runtime conversations from a managed agent.
Manage deploymentsScheduled / triggered runs and outcome rubrics.

Reference

Stable facts — fields, commands, provider matrix, API.

DocWhat's inside
Configuration referenceEvery agents.yaml field: type, required, default, provider support.
CLI referenceEvery agents command, options, and behavior.
Provider referenceCapability matrix and per-provider configuration.
SDK referencePublic @openagentpack/sdk API surface.
OpenAPI referenceThe HTTP surface exposed by apps/server.

Architecture

For contributors and deep users.

DocWhat's inside
How it worksState management, dependency graph, incremental diffing.

Contributing

For external contributors.

DocWhat's inside
Contributing overviewDev setup, merge requirements, code style.
Maintainer reviewEvidence-based PR review and merge gates.
DevelopmentClone, install, run, test, package boundaries.
Provider developmentThe six files a new provider must implement.
Releasenpm publishing workflow and Trusted Publishing.

Conventions

  • Design briefs and trade-off notes under package-specific documentation describe implementation history and do not override the public contract above.
  • Provider capability tables are verified against the SDK declarations by scripts/provider-docs.test.ts; the canonical matrix lives in Provider reference.