feat: initialize StackOne TypeScript agent with configs and examples #9

hiskudin · 2026-01-26T10:25:21Z

This pull request introduces a new TypeScript-based StackOne AI Agent example application that uses the Vercel AI SDK and supports dynamic tool creation from StackOne's MCP endpoint. The agent allows direct tool invocation (without a meta-tool) and features an interactive CLI for user interaction. The implementation includes configuration, dependencies, agent logic, and TypeScript project setup.

The most important changes are:

New Application: StackOne TypeScript Agent

Added a new stackone-typescript-agent app, including configuration files (.env.example, package.json, tsconfig.json) and a complete agent implementation in src/agent.ts. [1] [2] [3] [4]

Agent Implementation and Features (src/agent.ts):

Implements dynamic discovery and creation of tools for all linked accounts via StackOne MCP, mapping each tool to its account and provider.
Provides an interactive CLI mode with conversation history, dynamic provider-aware system prompts, and contextual example queries based on connected services.
Integrates with the Vercel AI SDK and Anthropic's Claude model for natural language processing and tool invocation, supporting multi-step workflows and error handling.

Project Configuration and Dependencies:

Adds a .env.example for required environment variables, including API keys for StackOne and Anthropic.
Sets up package.json with necessary dependencies (@ai-sdk/anthropic, ai, dotenv, zod, etc.) and scripts for running and type-checking the agent.
Configures TypeScript via tsconfig.json for strict typing, ES module support, and output settings.

Summary by cubic

Adds a TypeScript StackOne agent example that discovers tools from MCP for each linked account and calls them directly via the Vercel SDK. Includes an interactive CLI with history and a provider-aware system prompt.

New Features
- Discovers tools per linked account via MCP and exposes them as Vercel SDK tools.
- Namespaces tool keys by provider and account to avoid collisions.
- Converts MCP JSON Schema to Zod for tool parameters, with a safe fallback for unsupported cases.
- Direct tool calls (no meta-tool); supports multi-step workflows and error handling.
- Interactive CLI with conversation history, a /clear command, and dynamic examples.
- Provider-aware system prompt built from available tools.
Dependencies
- .env.example with STACKONE_API_KEY and ANTHROPIC_API_KEY.
- package.json adds required SDKs and scripts: agent, check-types.
- Strict TypeScript config via tsconfig.json.

^{Written for commit 1f9f779. Summary will update on new commits.}

…on and example

Copilot

Pull request overview

Introduces a new stackone-typescript-agent example app that uses the Vercel AI SDK + Anthropic to dynamically discover StackOne MCP tools and run an interactive CLI agent.

Changes:

Added a new TypeScript app with scripts, TS config, and environment variable example.
Implemented an interactive CLI agent that discovers linked accounts, lists MCP tools per account, and enables direct tool invocation via generateText.
Added dynamic system prompt and example queries based on connected providers.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 6 comments.

File	Description
apps/stackone-typescript-agent/src/agent.ts	Implements MCP account/tool discovery, tool execution wiring, prompt building, and CLI loop.
apps/stackone-typescript-agent/package.json	Adds dependencies and scripts for running/typechecking the agent.
apps/stackone-typescript-agent/tsconfig.json	TypeScript compiler configuration for the new app.
apps/stackone-typescript-agent/.env.example	Documents required environment variables for running the agent.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

apps/stackone-typescript-agent/.env.example

Copilot · 2026-01-26T10:30:24Z

apps/stackone-typescript-agent/src/agent.ts

+function createVercelTool(mcpTool: McpTool): CoreTool {
+  const toolName = mcpTool.name;
+
+  return {
+    description: mcpTool.description || `Call the ${toolName} tool`,
+    parameters: z.record(z.unknown()).describe("Arguments for the tool"),
+    execute: async (args: Record<string, unknown>) => {


McpTool includes inputSchema, but createVercelTool currently uses a generic z.record(z.unknown()) and ignores the provided schema. This loses parameter shape information and removes any validation/guidance for the model. Consider translating inputSchema into a Zod schema when available (and falling back to a permissive schema only when it’s missing).

Copilot · 2026-01-26T10:30:24Z

apps/stackone-typescript-agent/src/agent.ts

+        toolToAccount.set(mcpTool.name, account.id);
+        tools[mcpTool.name] = createVercelTool(mcpTool);


tools[mcpTool.name] and toolToAccount.set(mcpTool.name, …) will silently overwrite when multiple linked accounts expose the same MCP tool name (e.g., two Gmail accounts). That can route tool calls to the wrong account. Consider namespacing tool names (e.g., include account id/provider in the exposed tool name) or storing multiple accounts per tool and requiring disambiguation.

Suggested change

toolToAccount.set(mcpTool.name, account.id);

tools[mcpTool.name] = createVercelTool(mcpTool);

// Ensure tool names are unique across accounts to avoid silent overwrites.

const baseName = mcpTool.name;

let uniqueToolName = baseName;

if (tools[uniqueToolName]) {

// First try namespacing by provider.

uniqueToolName = `${account.provider}_${baseName}`;

}

if (tools[uniqueToolName]) {

// If still colliding (e.g., multiple accounts with same provider),

// append a numeric suffix until we find an available name.

let counter = 2;

let candidate = `${uniqueToolName}_${counter}`;

while (tools[candidate]) {

counter += 1;

candidate = `${uniqueToolName}_${counter}`;

}

uniqueToolName = candidate;

}

toolToAccount.set(uniqueToolName, account.id);

tools[uniqueToolName] = createVercelTool(mcpTool);

Copilot · 2026-01-26T10:30:24Z

apps/stackone-typescript-agent/src/agent.ts

+        tools[mcpTool.name] = createVercelTool(mcpTool);
+      }
+
+      providerCounts[account.provider] = mcpTools.length;


providerCounts[account.provider] = mcpTools.length overwrites counts when there are multiple active accounts for the same provider; the summary and system prompt will be inaccurate. Accumulate counts per provider (e.g., providerCounts[provider] = (providerCounts[provider] ?? 0) + mcpTools.length).

Suggested change

providerCounts[account.provider] = mcpTools.length;

providerCounts[account.provider] =

(providerCounts[account.provider] ?? 0) + mcpTools.length;

apps/stackone-typescript-agent/src/agent.ts

apps/stackone-typescript-agent/package.json

Co-authored-by: Copilot <[email protected]>

cubic-dev-ai

2 issues found across 4 files

Prompt for AI agents (all issues)


Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="apps/stackone-typescript-agent/src/agent.ts">

<violation number="1" location="apps/stackone-typescript-agent/src/agent.ts:105">
P2: Using `||` here discards valid falsy tool results (0/""/false) and returns the wrapper object instead. Use nullish coalescing to preserve legitimate results.</violation>

<violation number="2" location="apps/stackone-typescript-agent/src/agent.ts:174">
P2: Tools from multiple linked accounts can overwrite each other because they’re keyed only by tool name. For users with multiple accounts on the same provider, the last account silently wins and tool calls may be routed to the wrong account.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

apps/stackone-typescript-agent/src/agent.ts

cubic-dev-ai

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (all issues)


Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name=".gitignore">

<violation number="1" location=".gitignore:40">
P2: Avoid ignoring lock files globally. Lockfiles should be committed so installs are reproducible across machines and CI.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

.gitignore

Copilot

Pull request overview

Copilot reviewed 4 out of 5 changed files in this pull request and generated 7 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-01-26T11:17:50Z

apps/stackone-typescript-agent/src/agent.ts

+    headers: {
+      Authorization: `Basic ${Buffer.from(STACKONE_API_KEY + ":").toString("base64")}`,
+      "x-account-id": accountId,
+      "Content-Type": "application/json",
+      Accept: "application/json, text/event-stream",
+    },
+    body: JSON.stringify({
+      jsonrpc: "2.0",
+      id: `req-${method}-${Date.now()}`,


The request advertises Accept: application/json, text/event-stream but the response is always parsed via response.json(). If the server chooses text/event-stream (SSE), this will fail at runtime. Either request only JSON here or add handling for SSE responses.

apps/stackone-typescript-agent/src/agent.ts

Copilot · 2026-01-26T11:17:51Z

apps/stackone-typescript-agent/package.json

@@ -0,0 +1,22 @@
+{
+    "name": "stackone-typescript-agent",
+    "version": "1.0.0",


This app's package.json is missing "private": true. Other example apps in this repo (e.g. apps/oauth-redirect-proxy/package.json) mark themselves private to prevent accidental publication to npm.

Suggested change

"version": "1.0.0",

"version": "1.0.0",

"private": true,

Copilot · 2026-01-26T11:17:51Z

apps/stackone-typescript-agent/package.json

+    "scripts": {
+      "agent": "tsx src/agent.ts",
+      "typecheck": "tsc --noEmit"
+    },


This app defines a typecheck script, but the repo's root uses turbo run check-types (see turbo.json + root package.json). As-is, this app won't participate in the standard type-check task. Rename/add a check-types script (and optionally keep typecheck as an alias) to integrate with the monorepo workflows.

Copilot · 2026-01-26T11:17:52Z

apps/stackone-typescript-agent/src/agent.ts

+    // For mixed enums, use union of literals
+    const literals = schema.enum.map((v) => z.literal(v as string | number | boolean));
+    const zodUnion = z.union(literals as [z.ZodTypeAny, z.ZodTypeAny, ...z.ZodTypeAny[]]);


For non-string enums, this builds a z.union(...) from schema.enum. If the enum has only 1 value (e.g., [1] or [null]), z.union will throw because it requires at least 2 options. Handle single-value enums by returning z.literal(value) (and include null as a supported literal type).

Suggested change

// For mixed enums, use union of literals

const literals = schema.enum.map((v) => z.literal(v as string | number | boolean));

const zodUnion = z.union(literals as [z.ZodTypeAny, z.ZodTypeAny, ...z.ZodTypeAny[]]);

// For mixed enums, use literals; handle single-value enums without z.union

const literals = schema.enum.map((v) =>

z.literal(v as string | number | boolean | null),

);

if (literals.length === 1) {

const singleLiteral = literals[0];

return schema.description

? singleLiteral.describe(schema.description)

: singleLiteral;

}

const zodUnion = z.union(

literals as [z.ZodTypeAny, z.ZodTypeAny, ...z.ZodTypeAny[]],

);

apps/stackone-typescript-agent/src/agent.ts

Co-authored-by: Copilot <[email protected]>

…cript

…age-lock.json for stackone-typescript-agent

StuBehan

LGTM, some of the co-pilot comments might be actionable but not gonna block for them

Copilot

Pull request overview

Copilot reviewed 4 out of 6 changed files in this pull request and generated 6 comments.

Files not reviewed (1)

apps/stackone-typescript-agent/package-lock.json: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-01-29T13:54:51Z

apps/stackone-typescript-agent/src/agent.ts

+  const accountId = toolToAccount.get(toolName);
+  if (!accountId) {


callTool() looks up toolToAccount by the tool name it receives. However tools are registered under a namespaced key (provider:accountId:...) while createVercelTool() uses the underlying mcpTool.name. This will cause Unknown tool at runtime. Fix by keying lookups on the registered tool key and keeping a separate mapping for the MCP tool name.

Suggested change

const accountId = toolToAccount.get(toolName);

if (!accountId) {

// First, try direct lookup (in case the map is keyed by the raw tool name)

let accountId = toolToAccount.get(toolName);

// If not found, attempt to resolve by matching the suffix of a namespaced key

if (!accountId) {

for (const [registeredKey, mappedAccountId] of toolToAccount.entries()) {

const registeredName = registeredKey.split(":").pop();

if (registeredName === toolName) {

accountId = mappedAccountId;

break;

}

}

}

if (!accountId) {

Copilot · 2026-01-29T13:54:51Z

apps/stackone-typescript-agent/src/agent.ts

+  const result = (await mcpRequest(
+    "tools/call",
+    { name: toolName, arguments: args },
+    accountId


In tools/call, you send { name: toolName }. If toolName is the namespaced key, MCP will likely not recognize it; if it’s the raw MCP name, it won’t match your toolToAccount keys. Store { accountId, mcpName } per registered tool key and use mcpName in the MCP request.

Copilot · 2026-01-29T13:54:51Z

apps/stackone-typescript-agent/src/agent.ts

+ */
+function createVercelTool(mcpTool: McpTool): CoreTool {
+  const toolName = mcpTool.name;


createVercelTool() binds toolName to mcpTool.name, but the tool is actually exposed to the model under a different key (provider:accountId:...). Pass the exposed tool key into createVercelTool (for logging/description) so what the model calls matches what you display.

Suggested change

*/

function createVercelTool(mcpTool: McpTool): CoreTool {

const toolName = mcpTool.name;

*

* @param mcpTool - The underlying MCP tool definition.

* @param exposedToolKey - The key under which this tool is exposed to the model

* (e.g. "provider:accountId:toolName"). Used for logging

* and descriptions so they match what the model calls.

*/

function createVercelTool(mcpTool: McpTool, exposedToolKey?: string): CoreTool {

const toolName = exposedToolKey ?? mcpTool.name;

Copilot · 2026-01-29T13:54:52Z

apps/stackone-typescript-agent/src/agent.ts

+Tool names follow the pattern: provider_action (e.g., gmail_list_messages, drive_list_files).
+Use tool names and descriptions to understand their capabilities.
+You have conversation history - you can reference previous results.


The system prompt says tool names follow provider_action (e.g. gmail_list_messages), but the actual registered tool keys are provider:accountId:mcpTool.name. This mismatch can cause the model to call non-existent tools. Update the prompt to describe the real naming scheme (and include an example that matches).

apps/stackone-typescript-agent/src/agent.ts

Copilot · 2026-01-29T13:54:52Z

apps/stackone-typescript-agent/src/agent.ts

+    // Add response to history
+    conversationHistory.push({ role: "assistant", content: text });
+


Conversation history only persists user/assistant text (conversationHistory.push({ role: "assistant", content: text })) and does not store tool calls/results, but the system prompt claims prior results are available. Persist tool outputs (or a trimmed summary) into conversationHistory after each run so follow-up questions can reference them reliably.

Co-authored-by: Copilot <[email protected]>

Copilot

Pull request overview

Copilot reviewed 4 out of 6 changed files in this pull request and generated 3 comments.

Files not reviewed (1)

apps/stackone-typescript-agent/package-lock.json: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

apps/stackone-typescript-agent/src/agent.ts

Copilot · 2026-01-29T15:04:55Z

apps/stackone-typescript-agent/src/agent.ts

+      Authorization: `Basic ${Buffer.from(STACKONE_API_KEY + ":").toString("base64")}`,
+      "x-account-id": accountId,
+      "Content-Type": "application/json",
+      Accept: "application/json, text/event-stream",


The request advertises Accept: application/json, text/event-stream but the response is always parsed via response.json(). If the MCP endpoint responds with text/event-stream (SSE), this will throw. Either remove text/event-stream from Accept or branch on the Content-Type and implement SSE parsing.

Suggested change

Accept: "application/json, text/event-stream",

Accept: "application/json",

text/event-stream is required when fetching from https://api.stackone.com/mcp

apps/stackone-typescript-agent/src/agent.ts

Co-authored-by: Copilot <[email protected]>

hiskudin · 2026-01-29T15:12:18Z

Refactored the code and reviewed via Copilot a couple of times; it's definitely cleaner now. Thanks for pointing it out @StuBehan, didn't really look at the comments well.

It seems the merge is still blocked, though. Needs a "reviewer with write access"

feat: initialize StackOne TypeScript agent with essential configurati…

ff5f032

…on and example

Copilot AI review requested due to automatic review settings January 26, 2026 10:25

Copilot started reviewing on behalf of hiskudin January 26, 2026 10:25 View session

Copilot AI reviewed Jan 26, 2026

View reviewed changes

hiskudin and others added 3 commits January 26, 2026 10:34

Update apps/stackone-typescript-agent/package.json

e6ee8a2

Co-authored-by: Copilot <[email protected]>

Update apps/stackone-typescript-agent/src/agent.ts

54aec9b

Co-authored-by: Copilot <[email protected]>

Update apps/stackone-typescript-agent/.env.example

99baf87

Co-authored-by: Copilot <[email protected]>

cubic-dev-ai bot reviewed Jan 26, 2026

View reviewed changes

apps/stackone-typescript-agent/src/agent.ts Outdated Show resolved Hide resolved

apps/stackone-typescript-agent/src/agent.ts Outdated Show resolved Hide resolved

feat: enhance JSON Schema handling in McpTool

a59f672

hiskudin requested a review from Copilot January 26, 2026 11:12

Copilot started reviewing on behalf of hiskudin January 26, 2026 11:12 View session

chore: update .gitignore to include lock files for package management

f8eb7d3

cubic-dev-ai bot reviewed Jan 26, 2026

View reviewed changes

.gitignore Outdated Show resolved Hide resolved

Copilot AI reviewed Jan 26, 2026

View reviewed changes

hiskudin and others added 6 commits January 26, 2026 11:18

Update apps/stackone-typescript-agent/src/agent.ts

f69867a

Co-authored-by: Copilot <[email protected]>

fix: update Accept header in mcpRequest to remove text/event-stream

7434043

Update apps/stackone-typescript-agent/src/agent.ts

88db30b

Co-authored-by: Copilot <[email protected]>

Update apps/stackone-typescript-agent/src/agent.ts

feaaa86

Co-authored-by: Copilot <[email protected]>

chore: update package.json to set private flag and rename typecheck s…

faa3f1c

…cript

chore: update .gitignore to maintain .pem file exclusion and add pack…

fa587dc

…age-lock.json for stackone-typescript-agent

hiskudin self-assigned this Jan 27, 2026

StuBehan approved these changes Jan 29, 2026

View reviewed changes

hiskudin requested a review from Copilot January 29, 2026 13:47

Copilot started reviewing on behalf of hiskudin January 29, 2026 13:48 View session

Copilot AI reviewed Jan 29, 2026

View reviewed changes

hiskudin and others added 2 commits January 29, 2026 14:07

Update apps/stackone-typescript-agent/src/agent.ts

f1f8f5b

Co-authored-by: Copilot <[email protected]>

Refactor tool management in agent.ts

99a6f6a

hiskudin requested a review from Copilot January 29, 2026 14:57

Copilot started reviewing on behalf of hiskudin January 29, 2026 14:57 View session

Copilot AI reviewed Jan 29, 2026

View reviewed changes

hiskudin and others added 2 commits January 29, 2026 15:08

Update apps/stackone-typescript-agent/src/agent.ts

6e3b443

Co-authored-by: Copilot <[email protected]>

Update apps/stackone-typescript-agent/src/agent.ts

1f9f779

Co-authored-by: Copilot <[email protected]>

		toolToAccount.set(mcpTool.name, account.id);
		tools[mcpTool.name] = createVercelTool(mcpTool);

-        toolToAccount.set(mcpTool.name, account.id);
-        tools[mcpTool.name] = createVercelTool(mcpTool);
+        // Ensure tool names are unique across accounts to avoid silent overwrites.
+        const baseName = mcpTool.name;
+        let uniqueToolName = baseName;
+        if (tools[uniqueToolName]) {
+          // First try namespacing by provider.
+          uniqueToolName = `${account.provider}_${baseName}`;
+        }
+        if (tools[uniqueToolName]) {
+          // If still colliding (e.g., multiple accounts with same provider),
+          // append a numeric suffix until we find an available name.
+          let counter = 2;
+          let candidate = `${uniqueToolName}_${counter}`;
+          while (tools[candidate]) {
+            counter += 1;
+            candidate = `${uniqueToolName}_${counter}`;
+          }
+          uniqueToolName = candidate;
+        }
+        toolToAccount.set(uniqueToolName, account.id);
+        tools[uniqueToolName] = createVercelTool(mcpTool);

	providerCounts[account.provider] = mcpTools.length;
	providerCounts[account.provider] =
	(providerCounts[account.provider] ?? 0) + mcpTools.length;

-    // For mixed enums, use union of literals
-    const literals = schema.enum.map((v) => z.literal(v as string | number | boolean));
-    const zodUnion = z.union(literals as [z.ZodTypeAny, z.ZodTypeAny, ...z.ZodTypeAny[]]);
+    // For mixed enums, use literals; handle single-value enums without z.union
+    const literals = schema.enum.map((v) =>
+      z.literal(v as string | number | boolean | null),
+    );
+    if (literals.length === 1) {
+      const singleLiteral = literals[0];
+      return schema.description
+        ? singleLiteral.describe(schema.description)
+        : singleLiteral;
+    }
+    const zodUnion = z.union(
+      literals as [z.ZodTypeAny, z.ZodTypeAny, ...z.ZodTypeAny[]],
+    );

		const accountId = toolToAccount.get(toolName);
		if (!accountId) {

-  const accountId = toolToAccount.get(toolName);
-  if (!accountId) {
+  // First, try direct lookup (in case the map is keyed by the raw tool name)
+  let accountId = toolToAccount.get(toolName);
+  // If not found, attempt to resolve by matching the suffix of a namespaced key
+  if (!accountId) {
+    for (const [registeredKey, mappedAccountId] of toolToAccount.entries()) {
+      const registeredName = registeredKey.split(":").pop();
+      if (registeredName === toolName) {
+        accountId = mappedAccountId;
+        break;
+      }
+    }
+  }
+  if (!accountId) {

- */
-function createVercelTool(mcpTool: McpTool): CoreTool {
-  const toolName = mcpTool.name;
+ *
+ * @param mcpTool - The underlying MCP tool definition.
+ * @param exposedToolKey - The key under which this tool is exposed to the model
+ *                         (e.g. "provider:accountId:toolName"). Used for logging
+ *                         and descriptions so they match what the model calls.
+ */
+function createVercelTool(mcpTool: McpTool, exposedToolKey?: string): CoreTool {
+  const toolName = exposedToolKey ?? mcpTool.name;

		// Add response to history
		conversationHistory.push({ role: "assistant", content: text });

	Accept: "application/json, text/event-stream",
	Accept: "application/json",

feat: initialize StackOne TypeScript agent with configs and examples #9

Are you sure you want to change the base?

feat: initialize StackOne TypeScript agent with configs and examples #9

Conversation

hiskudin commented Jan 26, 2026 • edited by cubic-dev-ai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by cubic

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

StuBehan left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

hiskudin commented Jan 26, 2026 •

edited by cubic-dev-ai bot

Loading

hiskudin commented Jan 29, 2026 •

edited

Loading