The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agents-api	Ready	Preview, Comment	Apr 1, 2026 4:45pm
agents-docs	Ready	Preview, Comment	Apr 1, 2026 4:45pm
agents-manage-ui	Ready	Preview, Comment	Apr 1, 2026 4:45pm

⚠️ No Changeset found

Latest commit: f7c05d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

TL;DR — Upgrades drizzle-orm to 1.0.0-beta.20, drizzle-kit to 1.0.0-beta.20, and drizzle-zod to 1.0.0-beta.14. The v1 API introduces a new defineRelations() pattern that replaces the inline relations() calls — this PR extracts all relation definitions into dedicated files, migrates every drizzle() call site to the v1 config-object API, and replaces db.query.* relational queries with explicit db.select().from() calls across the entire data-access layer.

Key changes

• Upgrade drizzle-orm, drizzle-kit, and drizzle-zod to v1 RC — Pins all three packages to 1.0.0-beta.20 / 1.0.0-beta.14 across agents-core, agents-api, create-agents-template, and root package.json.
• Extract relations into manage-relations.ts and runtime-relations.ts — New files using defineRelations() replace the inline relations() calls that remain in the schema files under the drizzle-orm/_relations compat import.
• Migrate all drizzle() calls to v1 config-object API — Every drizzle(pool, { schema }) call becomes drizzle({ client: pool, schema, relations }) across production clients, test clients, ref-scope.ts, and branchScopedDb.ts.
• Replace db.query.* with explicit db.select().from() queries — 32 data-access files rewritten to use the select builder instead of the relational query API, with manual joins where with: was previously used.
• Fix JSONB type inference for drizzle-zod v1 — Adds explicit .extend() overrides on createSelectSchema/createInsertSchema for columns using $type<>() (e.g. conversationHistoryConfig, render, expectedOutput, conversationIds).
• Regenerate all migration snapshots in drizzle-kit v1 format — Migrations move from meta/NNNN_snapshot.json flat files to TIMESTAMP_name/snapshot.json directories with per-migration snapshots. The meta/ journals and old snapshots are deleted.
• Update database client types — AgentsManageDatabaseClient and AgentsRunDatabaseClient now carry both schema and relations generic parameters.
• Export new relation modules from @inkeep/agents-core — Adds ./db/manage-relations and ./db/run-relations package exports for downstream consumers.

_{Summary ｜ 275 files ｜ 2 commits ｜ base: main ← claude/drizzle-orm-v1-rc-2UebQ}

Drizzle v1 RC dependency upgrade

Before: drizzle-orm@^0.44.4, drizzle-kit@^0.31.x, drizzle-zod@^0.8.2
After: [email protected], [email protected], [email protected]

All three Drizzle packages are pinned to exact v1 RC versions (no caret ranges) across four package.json files. The lockfile diff reflects the resolution changes.

packages/agents-core/package.json · agents-api/package.json · package.json

Relation definitions extracted to dedicated files

Before: Relations defined inline in manage-schema.ts and runtime-schema.ts using relations() from drizzle-orm
After: Relations defined in manage-relations.ts and runtime-relations.ts using defineRelations() from drizzle-orm v1; schema files import legacy relations from drizzle-orm/_relations

The new defineRelations() API takes the full schema object and a callback that declaratively maps every table's relationships. The existing relations() calls in the schema files are kept for backward compat but now import from drizzle-orm/_relations.

Why keep the old relations() calls in schema files?

The old relations() calls remain under the drizzle-orm/_relations compat import so that existing code referencing these symbols doesn't break during the transition. The new defineRelations() is what the database clients actually use at runtime.

manage-relations.ts · runtime-relations.ts · manage-schema.ts

Database client initialization migrated to v1 API

Before: drizzle(pool, { schema }) — positional arguments
After: drizzle({ client: pool, schema, relations: manageRelations }) — config object with explicit relations

All four production clients, both test clients, three withRef call sites in ref-scope.ts, and the branchScopedDb middleware are updated. The AgentsManageDatabaseClient and AgentsRunDatabaseClient types now carry a second generic parameter for the relations object.

manage-client.ts · runtime-client.ts · ref-scope.ts · branchScopedDb.ts

Data-access layer rewritten from db.query.* to db.select().from()

Before: db.query.agents.findFirst({ where, with: { defaultSubAgent: true } }) — relational query API
After: db.select().from(agents).where(...).limit(1) with manual follow-up queries for related entities

32 data-access files across both manage and runtime domains are rewritten. Where the old API used with: to eagerly load relations, the new code performs explicit secondary queries.

Why not use the new relational query API?

The v1 relational query API (db.query) has a different shape and the defineRelations integration is still in beta. Using the select builder is the most stable path for the v1 RC and avoids coupling to APIs that may change before GA.

agents.ts · schemas.ts · entities.ts

JSONB type overrides for drizzle-zod v1

Before: createSelectSchema(table) inferred correct types for $type<>() JSONB columns
After: createSelectSchema(table).extend({ col: z.custom<T>() }) — explicit overrides needed because drizzle-zod v1 infers z.ZodType<T, $strip> for typed columns, breaking cross-package inference

Affects SubAgentSelectSchema (conversationHistoryConfig), DataComponentSelectSchema / ArtifactComponentSelectSchema (render), DatasetItemSelectSchema (expectedOutput), and ScheduledTriggerInvocationSelectSchema (conversationIds, ref, resolvedPayload).

schemas.ts · entities.ts

Migration snapshots regenerated in drizzle-kit v1 format

Before: Flat meta/NNNN_snapshot.json files alongside a meta/_journal.json index
After: Each migration lives in a TIMESTAMP_name/ directory containing both migration.sql and snapshot.json; meta/ journals and old snapshots are deleted

This accounts for the vast majority of the diff volume (~146 files, ~291k insertions / ~163k deletions). The actual SQL migration content is unchanged — only the directory structure and snapshot format differ.

  ^{｜ View workflow run ｜ Triggered by Pullfrog ｜ Using Claude Opus ｜ 𝕏}

Ito Test Report ✅

17 test cases ran. 3 additional findings, 14 passed.

Overall, 14 of 17 test cases passed in local regression coverage, confirming stable project/agent/external-agent/skills/datasets/evaluations routing under refresh and back/forward navigation, safe malformed-ID handling and recovery, authorization/XSS protections, idempotent rapid-save/create behavior, concurrent-tab convergence, mobile CRUD operability, and scheduled-trigger views with nullable conversation data. The three high-severity failures identified two real production regressions: playground chat thread continuity breaks after refresh because conversation IDs are regenerated instead of persisted, and /run/api/chat incorrectly returns bad_request when defaultSubAgentId is missing instead of matching /run/v1/chat/completions fallback behavior.

✅ Passed (14)

Category	Summary	Screenshot
Adversarial	Tampered tenant/project/agent/external-agent/trigger URLs consistently returned deny/not-found behavior (UI 404, API 403) and did not expose cross-tenant data.
Adversarial	Injected payloads (<script> and onerror img) were stored and rendered as inert text in form/list views across refresh; no execution/dialog triggered, and API returned payload as plain string content.
Adversarial	Malformed deep-link IDs failed safely with controlled error handling, no data leakage, and normal navigation remained functional afterward.
Adversarial	Two-tab stale writes converged deterministically after refresh (last-write-wins), with no silent data corruption.
Edge	Rapid repeated save/create actions remained idempotent; one final description value and one qa-agent-race-edge1 record persisted after refresh and API verification.
Edge	Rapid create and Enter re-submissions did not create duplicates; exactly one qa-agent-race-edge2 record persisted with stable list/API results.
Edge	Repeated back/forward traversal across projects, agent list, and agent detail stayed stable without persistent broken state.
Logic	Unknown and malformed IDs produced controlled not-found/unauthorized behavior, and the app recovered to valid project and agent pages without crashing.
Logic	Scheduled trigger invocations list/detail rendered safely and the corrected invocations endpoint returned a valid payload without null-related crashes.
Logic	Dataset and evaluation route reads remained stable with controlled empty states and no UI/runtime crash.
Mobile	Mobile 390x844 critical CRUD flow stayed operable: project navigation, agent edit-save, and agent creation all succeeded.
Happy-path	Project list and project settings detail loaded and remained stable after hard refresh with populated UI state.
Happy-path	Agent list/detail route and full agent definition retrieval succeeded, including post-refresh recovery after beforeunload confirmation.
Happy-path	External agents, skills, datasets, and evaluations pages loaded and refreshed stably after baseline project setup.

ℹ️ Additional Findings (3)

These findings are unrelated to the current changes but were observed during testing.

Category	Summary	Screenshot
Edge	⚠️ Mid-conversation refresh cannot reliably continue in the same UI thread.
Logic	⚠️ Fallback is inconsistent: /run/v1/chat/completions falls back to the first sub-agent, but /run/api/chat returns bad_request when defaultSubAgentId is missing.
Happy-path	⚠️ Refresh breaks reliable reuse of the active playground conversation thread.

playgroundConversationId: generateId(),

resetPlaygroundConversationId() {
  set({ playgroundConversationId: generateId() });
},

partialize(state) {
  return {
    jsonSchemaMode: state.jsonSchemaMode,
    isSidebarPinnedOpen: state.isSidebarPinnedOpen,
    hasTextWrap: state.hasTextWrap,
  };
}

aiChatSettings={{
  aiAssistantAvatar: {
    light: '/assets/inkeep-icons/icon-blue.svg',
    dark: '/assets/inkeep-icons/icon-sky.svg',
  },
  isChatHistoryButtonVisible: false,
  isViewOnly: hasHeadersError,
  conversationId,
  baseUrl: PUBLIC_INKEEP_AGENTS_API_URL,
}}

const agentKeys = Object.keys((fullAgent.subAgents as Record<string, any>) || {});
const firstAgentId = agentKeys.length > 0 ? agentKeys[0] : '';
defaultSubAgentId = (fullAgent.defaultSubAgentId as string) || firstAgentId; // Use first agent if no defaultSubAgentId

if (!defaultSubAgentId) {
  throw createApiError({
    code: 'not_found',
    message: 'No default agent found in agent',
  });
}

const defaultSubAgentId = agent.defaultSubAgentId;
const agentName = agent.name;

if (!defaultSubAgentId) {
  throw createApiError({
    code: 'bad_request',
    message: 'Agent does not have a default agent configured',
  });
}

const initialAgentState: AgentStateData = {
  nodes: [],
  edges: [],
  dirty: false,
  history: [],
  future: [],
  isSidebarSessionOpen: true,
  variableSuggestions: [],
  hasOpenModelConfig: false,
  playgroundConversationId: generateId(),
};

persist(agentState, {
  name: 'inkeep:agent',
  partialize(state) {
    return {
      jsonSchemaMode: state.jsonSchemaMode,
      isSidebarPinnedOpen: state.isSidebarPinnedOpen,
      hasTextWrap: state.hasTextWrap,
    };
  },
})

const { resetPlaygroundConversationId } = useAgentActions();
const conversationId = useAgentStore(({ playgroundConversationId }) => playgroundConversationId);

<ChatWidget
  conversationId={conversationId}
  resetPlaygroundConversationId={resetPlaygroundConversationId}
  startPolling={startPolling}
  stopPolling={stopPolling}
  agentId={agentId}
  projectId={projectId}
  tenantId={tenantId}
/>

Commit: f7c05d3

View Full Run

Tell us how we did: Give Ito Feedback