orchajs@0.28.1

Patch Changes

• #140 da0b33c Thanks @anuj-sia! - Replace inline type import and export specifiers with statement-level import type and export type declarations so emitted .d.ts files remain compatible with older TypeScript compilers.

orchajs@0.28.0

Minor Changes

• #138 f4d706b Thanks @anuj-sia! - Add vendor-neutral OpenTelemetry GenAI tracing through a global provider or direct OTLP/HTTP endpoint, including model calls, tools, evaluations, errors, and linked subagent runs.

orchajs@0.27.4

Patch Changes

• #136 f9c395e Thanks @anuj-sia! - Keep unused optional features out of the default Node bundler graph.

  The compiler, provider adapters, QuickJS sandbox, MCP client, and SQLite implementation now load through runtime-only package boundaries when their corresponding feature is used. The default ESM and CommonJS entries remain compatible with zero-config orcha.init() while no longer requiring bundlers to resolve unused optional peers or native packages.

  Add an Edge-compatible export condition, preserve the existing lazy NodeSqliteSessionStore API, and add consumer-bundle regression coverage for ESM, CommonJS, and zero-config runtime execution.

orchajs@0.27.3

Patch Changes

• #134 8e21df2 Thanks @anuj-sia! - Support nested subagent chains and cycle detection across the compiler, runtime, and test runner.

  • When an agent is referenced as a subagent of another agent, automatically inherit its own declared subagents and mcp registrations (or allow inline nested subagents declarations).
  • Recursively instantiate nested RuntimeAgent subagent trees in orcha.init() and orcha.runTests(), and allow subagentHistory() / subagentEvents() to inspect descendant sessions across the hierarchy.
  • Detect and reject circular subagent chains (A -> B -> C -> A) at compile and initialization time.

orchajs@0.27.2

Patch Changes

• #132 fc689bb Thanks @anuj-sia! - Preserve assistant messages and surface root-cause tool failures on structured output errors, and make Amarsia telemetry dispatch fully non-blocking.

  • When an outputType: "json" agent returns plain text or invalid JSON, persist the assistant message.created event and token usage first, include a preview of the model's response in the error message, and surface any preceding action or subagent failures from the run.
  • Distinguish action parameter validation errors from action outputSchema errors, surface real MCP tool error details when isError is returned, and safely parse non-JSON provider HTTP error bodies.
  • Make withAmarsiaTelemetry completely non-blocking on append() and dispatch terminal run telemetry immediately in the background without blocking behind in-flight running batches.

orchajs@0.27.1

Patch Changes

• #130 810a6b8 Thanks @anuj-sia! - Redact sensitive values from evaluation reasoning, telemetry, and project sync.

  Evaluation judges are instructed not to quote personal data, tax identifiers, financial figures, or secrets. Those values are also stripped from evaluation reasoning and evidence, run errors, and telemetry before they are stored or sent. Project sync now sends only the project directory name and removes credentials embedded in repository URLs.

orchajs@0.27.0

Minor Changes

• #128 2dbe2e9 Thanks @anuj-sia! - Enable zero-bundler-config initialization across Node.js, Next.js, React, and React Native/Expo, automatic prebuild/predev compilation hooks, and fix the CJS/ESM dual-package singleton hazard:

  • Zero-config Node.js & Next.js server initialization: orcha.init() compiles orcha/ automatically on the spot when no precompiled .orcha/dist/manifest.json exists — including in production if .orcha/dist/manifest.json was not prebuilt and orcha/ is deployed alongside the server.
  • Zero-config Browser & React Native: orchajs init, orchajs dev, orchajs build, and Node orcha.init() sync the compiled manifest directly into orchajs's runtime manifest module (compiled-manifest.js) and globalThis, so import { orcha } from "orchajs" works in React, Next.js client components, and React Native / Expo with zero bundler configuration.
  • Automatic framework target detection & lifecycle hooks: orchajs build and orchajs dev auto-detect Next.js, Vite/React, and React Native/Expo targets from the project, and orchajs init wires prebuild and predev in package.json so npm run build and npm run dev compile Orcha automatically.
  • Shared globalThis singletons: Store orcha runtime singletons (Symbol.for("orchajs.runtime")), compiler hooks, runtime contexts, and build queues on globalThis so ESM (dist/) and CommonJS (dist-cjs/) always share the exact same state in the same Node process.

orchajs@0.26.1

Patch Changes

• #126 4fe97bb Thanks @anuj-sia! - Fix CJS/ESM dual-package singleton hazard during buildProject() across Next.js (withOrcha), Metro/Expo (withOrchaMetro), Webpack (OrchaWebpackPlugin), and esbuild (orchaPlugin) integrations by storing compiler hooks, the shared Node orcha singleton, runtime contexts, and build queues on globalThis via Symbol.for(...), and resolving generated production runtime entry imports to the ESM dist/ output when invoked from dist-cjs/.

orchajs@0.26.0

Minor Changes

• #124 fe3d3e3 Thanks @anuj-sia! - Add multimodal tool result contents for local and client actions.

  • Local actions can return { output, contents } so structured JSON stays
    schema-validated while media and other content items are forwarded to the
    model.
  • Client action resumes accept optional contents alongside output, with the
    same envelope persisted in session events and provider adapters.
  • Propagate multimodal tool contents through Amarsia-managed inference for
    OpenAI, Anthropic, and Google, and surface a clear
    unsupported_content_type error when DeepSeek receives non-text contents.
  • Update AGENTS.md guidance and the playground visualInspector agent so the
    multimodal envelope is easy to exercise end to end.

create-orcha@0.4.5

Patch Changes

• #124 fe3d3e3 Thanks @anuj-sia! - Add multimodal tool result contents for local and client actions.

  • Local actions can return { output, contents } so structured JSON stays
    schema-validated while media and other content items are forwarded to the
    model.
  • Client action resumes accept optional contents alongside output, with the
    same envelope persisted in session events and provider adapters.
  • Propagate multimodal tool contents through Amarsia-managed inference for
    OpenAI, Anthropic, and Google, and surface a clear
    unsupported_content_type error when DeepSeek receives non-text contents.
  • Update AGENTS.md guidance and the playground visualInspector agent so the
    multimodal envelope is easy to exercise end to end.