Skip to content

Releases: objectstack-ai/framework

objectstack-vscode@6.1.1

24 May 14:57
d536528

Choose a tag to compare

objectstack-vscode@6.1.1

objectstack-vscode@6.0.0

24 May 12:51
59be331

Choose a tag to compare

objectstack-vscode@6.0.0

create-objectstack@6.1.1

24 May 14:56
d536528

Choose a tag to compare

create-objectstack@6.1.1

create-objectstack@6.0.0

24 May 12:49
59be331

Choose a tag to compare

create-objectstack@6.0.0

@objectstack/types@6.1.1

24 May 14:58
d536528

Choose a tag to compare

Patch Changes

  • @objectstack/spec@6.1.1

@objectstack/types@6.0.0

24 May 12:51
59be331

Choose a tag to compare

Patch Changes

  • Updated dependencies [629a716]
  • Updated dependencies [dbc4f7d]
  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0

@objectstack/sveltekit@6.1.1

24 May 14:55
d536528

Choose a tag to compare

@objectstack/sveltekit@6.1.1

@objectstack/sveltekit@6.0.0

24 May 12:49
59be331

Choose a tag to compare

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0

@objectstack/spec@6.1.1

24 May 14:57
d536528

Choose a tag to compare

@objectstack/spec@6.1.1

@objectstack/spec@6.0.0

24 May 12:51
59be331

Choose a tag to compare

Major Changes

  • 629a716: # v1 AI Protocol focusing — remove application-template schemas

    The @objectstack/spec/ai protocol is reduced to only the primitives
    the runtime directly consumes
    . Eight schemas that described
    application templates or product features (not platform contracts) are
    removed; three more are slimmed to their primitive cores.

    Removed (8 files, ~4,700 lines)

    File Reason for removal
    ai/devops-agent.zod.ts A specific Agent template, not a primitive. Compose with Agent + Skill + Tool.
    ai/plugin-development.zod.ts Specific workflow; same reasoning.
    ai/runtime-ops.zod.ts AIOps is a vertical product, not a backend platform concern.
    ai/predictive.zod.ts ML pipeline product (DataRobot/H2O space), orthogonal to metadata-driven backend.
    ai/agent-action.zod.ts 100% conceptual overlap with tool + flow.
    ai/orchestration.zod.ts Multi-agent plans can be expressed as agents-as-tools. Premature.
    ai/nlq.zod.ts NLQ is LLM-native capability + a query_data tool over ObjectQL, not a protocol.
    ai/feedback-loop.zod.ts RLHF / training-side concern; not platform-owned.

    Slimmed (3 files)

    • ai/rag-pipeline.zod.tsai/embedding.zod.ts (318 → 80 lines).
      Keeps EmbeddingModelSchema + VectorStoreSchema primitives.
      Removed: chunking strategies, retrieval pipelines, rerankers,
      document loaders, end-to-end RAG pipeline DSL. The ragPipelines
      field on defineStack() is removed.
    • ai/cost.zod.tsai/usage.zod.ts (431 → ~70 lines).
      Keeps TokenUsageSchema + AIUsageRecordSchema. Model pricing is
      the canonical ModelPricingSchema already exported from
      ai/model-registry.zod.ts. Removed: budget definitions,
      enforcement, alerts, allocation reports, optimization
      recommendations.
    • ai/mcp.zod.ts (629 → ~100 lines). Defines only how to
      reference an external MCP server and bind its tools to an
      agent. The MCP protocol itself is owned by Anthropic's published
      spec and the @modelcontextprotocol/sdk; we no longer re-declare
      transport/capability/resource/prompt/streaming/sampling shapes.

    Migration

    No production code in this repository depended on the removed
    schemas. Downstream consumers that imported any of the removed types
    from @objectstack/spec/ai must:

    1. Remove the import. The platform no longer provides these types.
    2. Define your own application-level shape in your project / plugin
      if you still need the concept. The primitives (Agent, Skill,
      Tool, Conversation, Embedding, Usage, MCP{ServerRef,ToolBinding})
      are sufficient to express every removed schema.
    3. For RAG: replace RAGPipelineConfig with your own pipeline
      description built on EmbeddingModelSchema + VectorStoreSchema.
    4. For cost: replace budget enforcement with your own service built
      on AIUsageRecordSchema records.

    Why

    The platform's job is to define primitives that any AI feature can
    be built on top of
    , leveraging the metadata-driven nature of
    ObjectStack. The removed schemas described specific product features
    (DevOps agent, AIOps, RAG pipeline DSL, budget enforcement) that
    should live in plugins or applications — not in the canonical
    protocol. Shipping a 6,245-line AI protocol where 80% of it has no
    runtime implementation creates false promises to integrators.

    After this change the AI protocol is:

    ai/
    ├── agent.zod.ts          ← who
    ├── skill.zod.ts          ← when
    ├── tool.zod.ts           ← what
    ├── conversation.zod.ts   ← what to remember
    ├── model-registry.zod.ts ← which LLMs
    ├── embedding.zod.ts      ← embedding + vector store primitives
    ├── usage.zod.ts          ← token + cost accounting
    └── mcp.zod.ts            ← external ecosystem bridge
    

    8 files, ~1,200 lines. Every schema has a runtime implementation in
    @objectstack/service-ai or @objectstack/plugin-mcp-server.

  • 944f187: # v5.0 — projectenvironment hard rename

    The runtime concept previously called "project" (per-tenant business
    workspace; Org → Project → Branch hierarchy; per-project ObjectKernel,
    per-project DB, per-project artifact) is now uniformly called
    "environment".

    This is a hard rename with no aliases, deprecation shims, or compatibility
    layer
    . Upgrade requires a coordinated update of CLI, runtime, server, and any
    clients calling the REST API.

    Note: "project" in the npm / monorepo sense (the framework itself, package.json,
    tsconfig project references, vitest projects config) is unchanged.

    Breaking changes

    CLI

    • Flags renamed:
      • --project / -p--environment / -e (os publish, os rollback)
      • --project-id--environment-id (os dev)
    • Default local env id: proj_localenv_local.
    • Env var: OS_PROJECT_IDOS_ENVIRONMENT_ID.
    • Command group renamed: os projects ...os environments ...
      (bind, create, list, show, switch).
    • Persisted auth-config key: activeProjectIdactiveEnvironmentId.

    HTTP / REST

    • Scoped routes: /api/v1/projects/:projectId/.../api/v1/environments/:environmentId/....
    • Cloud control-plane routes: /api/v1/cloud/projects/.../api/v1/cloud/environments/...
      (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata,
      /cloud/environments/:id/credentials/rotate, etc.).
    • Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id
      (x-environment-id).
    • Route param name in handlers: req.params.projectIdreq.params.environmentId.
    • Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.

    Runtime / spec

    • Exported symbols (no aliases):
      • createSystemProjectPlugincreateSystemEnvironmentPlugin
      • SYSTEM_PROJECT_IDSYSTEM_ENVIRONMENT_ID
      • ProjectArtifactSchemaEnvironmentArtifactSchema
      • PROJECT_ARTIFACT_SCHEMA_VERSIONENVIRONMENT_ARTIFACT_SCHEMA_VERSION
      • ObjectOSProjectPluginObjectOSEnvironmentPlugin
      • createSingleProjectPlugincreateSingleEnvironmentPlugin
    • Plugin identifier strings:
      • com.objectstack.runtime.objectos-projectobjectos-environment
      • com.objectstack.studio.single-projectsingle-environment
      • com.objectstack.multi-projectmulti-environment
      • com.objectstack.runtime.system-projectsystem-environment
    • Provisioning hook: provisionSystemProjectprovisionSystemEnvironment.

    Database / schemas

    • Column renames on sys_metadata and sys_metadata_history:
      project_idenvironment_id.
    • Column renames on sys_activity: project_idenvironment_id (plus index).
    • Object renames in platform-objects metadata: sys_projectsys_environment
      (lookup targets), sys_project_membersys_environment_member,
      sys_project_credentialsys_environment_credential.
    • Auth-context field: active_project_idactive_environment_id.
    • JSON schemas under packages/spec/json-schema/system/:
      ProjectArtifact*.jsonEnvironmentArtifact*.json (regenerated at build).

    Automatic forward migration

    A new migration migrateProjectIdToEnvironmentId
    (packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts)
    auto-runs from DatabaseLoader.ensureSchema() on bootstrap and rewrites any
    existing project_id column on sys_metadata / sys_metadata_history to
    environment_id (idempotent, best-effort). Existing rows are preserved.

    The legacy reverse migration migrateEnvIdToProjectId is retained verbatim
    for historical / disaster-recovery use; it is not auto-run.

    Migration guide

    -os publish --project proj_xyz
    +os publish --environment env_xyz
    
    -curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer
    +curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer
    
    -OS_PROJECT_ID=env_xyz os dev
    +OS_ENVIRONMENT_ID=env_xyz os dev
    
    -import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";
    +import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";
    
    -import { ProjectArtifactSchema } from "@objectstack/spec";
    +import { EnvironmentArtifactSchema } from "@objectstack/spec";

    If you maintain a Cloud control-plane deployment, the cloud repository must
    be updated in lockstep to pick up the new plugin identifier strings
    (single-environment, multi-environment, objectos-environment).

Minor Changes

  • dbc4f7d: feat(ai): v1 AI capabilities — ModelRegistry, structured output, tracing, schema retrieval, and query_data tool

    This release lights up the first concrete capabilities on the slimmed AI protocol. All additions are
    non-breaking — new contract methods are optional and existing callers keep working unchanged.

    What's new

    • ModelRegistry (`@objectstack...
Read more