Skip to content

v0.31.0

Latest

Choose a tag to compare

@kid7st kid7st released this 13 Nov 03:41
7a46168

Bump @fastagent-sh/fastagent from 0.30.3 to 0.31.0.

Included

  • Configuration and deployment instances (#998, #1003, #1009, #1014).
    • A deployment is an instance of its own, named by its configuration (name, else the program's name), with its own manifest (fly.<name>.toml, fastagent.<name>.compose.yml, agentcore.<name>.template.yaml).
    • The image holds only the program; deploy delivers the instance configuration via FASTAGENT_NAME, FASTAGENT_RELEASE_ID, and FASTAGENT_CONFIG_JSON, and reads no default value file.
    • Environment layers apply in order: program defaults < instance config < env vars (FASTAGENT_THINKING_LEVEL, FASTAGENT_HTTP_API, FASTAGENT_HTTP_PUBLIC_URL, FASTAGENT_INGRESS) < CLI flags.
  • Channel turns and sessions (#1001, #1002, #1005, #1007, #1008, #1012, #1016).
    • Group timelines keep one session per sender; turns steer into the target session (including replies) and fold recent discussion within the model's context budget.
    • Opening a new Feishu topic forks the session holding the message it was opened on; Telegram keeps un-summoned messages 14 days and warns about group privacy mode during setup.
  • Embedding and authoring (#988, #993, #994, #996, #1010 / #1028, #1013 / #1029).
    • openAgent(definition, { root }) without config reads <root>/fastagent.json.
    • addContent, removeContent, and listContent work over built definitions with instance.config, and content directories may contain or sit inside the definition directory.
    • addMcpServer and removeMcpServer manage an instance's mcpServers under the same lock and validation rules as openAgent.
    • openAgent opens when a configured default model is absent from the catalog, leaving info().defaultModel unset and reporting info().unusableDefault.
  • Dependencies and fixes: @earendil-works/chord, pi-ai, pi-durable, and pi-schema updated to 1.5.2 (#1027); stops wait for the whole process group (#1015).

Breaking changes

No compatibility layer, as before 1.0.

  • info() separates program and instance identity: info().name and info().description belong to the instance; info().agent holds the program's name and description; info().starters moves to the top level of AgentInfo (#998).
  • fastagent.config.ts removes extensions (put extensions under src/extensions/), and program defaults refuse channels.<name>.app. deploy.* is no longer allowed in an instance's fastagent.json (#998).
  • deploy reads only the renamed per-instance manifests (fly.<name>.toml, fastagent.<name>.compose.yml, agentcore.<name>.template.yaml) and warns once when it sees an old generated manifest. The /etc/fastagent/ layer, FASTAGENT_CONFIG, fastagent.release.json, and FASTAGENT_RELEASE_FILE are removed (#1003, #1009).
  • openAgent(definition, { root }) reads <root>/fastagent.json when present; pass config (including {}) if <root>/fastagent.json should be ignored (#996).
  • openAgent no longer throws on an unknown configured default model (explicit model options remain strict) (#1028).

Known limitations

  • Codex provider session resources can outlive agent.close() (#896; fixed on earendil-works/pi main in #11961, not yet in pi 1.5.2).
  • chord@1.5.2 declares react as an exact optional peer (19.3.0), which can cause ERESOLVE in projects with another react patch version until the upstream range fix is released.
  • Multi-instance deploy plans and variable delivery (#1003, #1009) were verified with test runners, not re-run on live Fly, Railway, AgentCore, or Docker hosts.

Verification

  • npm run lint, npm run typecheck, npm test (80 files, 329 passed), npm run test:integration (16 files, 28 passed), npm pack --dry-run --json on PR #1030 (chore/release-0.31.0).