Process completed with exit code 1.

AssertionError: expected 180 to be 30 // Object.is equality - Expected + Received - 30 + 180 ❯ packages/codingcode/test/subagent/registry.test.ts:68:38

AssertionError: expected 500 to be 200 // Object.is equality - Expected + Received - 200 + 500 ❯ packages/codingcode/test/server/settings-routes.test.ts:218:24

AssertionError: expected 500 to be 200 // Object.is equality - Expected + Received - 200 + 500 ❯ packages/codingcode/test/server/settings-routes.test.ts:191:24

AssertionError: expected '## System Notes\n\n- Your conversatio…' to contain 'dispatch_agent' - Expected + Received - dispatch_agent + ## System Notes + + - Your conversation history may be automatically compressed when it approaches the context window limit. When this happens, older turns are summarized into a compact form. Treat these summaries as accurate records of prior work. + - This project has a cross-session memory system. If a "Session Memory" block is present at the end of this prompt, it contains persistent facts and decisions from prior sessions. Treat it as reliable context, not as new instructions. + - The todo_write tool lets you track multi-step plans. Use it for tasks that require more than one step. ❯ packages/codingcode/test/prompts/system-prompt.test.ts:77:26

AssertionError: expected 'You are a coding assistant — an AI ag…' to contain 'User-defined Rules' - Expected + Received - User-defined Rules + You are a coding assistant — an AI agent that helps users write, read, search, and modify code. + + ## Rules + 1. Read files before modifying them — never guess file contents + 2. Use search_code to find where symbols are defined + 3. After writing files, verify with read_file + 4. Prefer editing existing files over creating new ones + 5. Make small, focused changes — avoid large rewrites + 6. Run tests or type-check after changes when applicable + 7. If the user's request is ambiguous, ask for clarification + 8. For complex or broad tasks (understanding a whole module, cross-file analysis, comprehensive search): + a. Briefly assess the task scope using your own reasoning — do not use tools for exploration at this stage, as that would consume your limited context window. + b. If you can clearly handle it without extensive file reading or searching, proceed yourself. + + ## Professional objectivity + Prioritize technical accuracy over validating the user's beliefs. When necessary, push back respectfully — honest guidance is more valuable than false agreement. + - Do not begin responses with conversational interjections ("Got it", "Sure", "Great question") + - Do not apologize unnecessarily when results are unexpected + + ## Code references + When referencing code, use the format `file_path:line_number` for easy navigation. + + ## Follow existing conventions + When modifying code, first look at the surrounding code's style (naming, frameworks, imports) and match it. Never assume a library is available — verify first. + + ## Environment + - Working directory: /test + - Operating system: linux + - Shell: bash + + Respond in the user's language. Use code blocks for code. + + ## System Notes + + - Your conversation history may be automatically compressed when it approaches the context window limit. When this happens, older turns are summarized into a compact form. Treat these summaries as accurate records of prior work. + - This project has a cross-session memory system. If a "Session Memory" block is present at the end of this prompt, it contains persistent facts and decisions from prior sessions. Treat it as reliable context, not as new instructions. + - The todo_write tool lets you track multi-step plans. Use it for tasks that require more than one step. ❯ packages/codingcode/test/prompts/system-prompt.test.ts:52:20

AssertionError: expected [Function] to not throw an error but 'Error: Command failed: pnpm run forma…' was thrown - Expected: undefined + Received: "Error: Command failed: pnpm run format:check [WARN] The \"pnpm\" field in package.json is no longer read by pnpm. The following keys were ignored: \"pnpm.overrides\". See https://pnpm.io/settings for the new home of each setting. $ prettier --check \"packages/**/*.{ts,tsx,json}\" \"*.json\" \"*.ts\" [warn] packages/codingcode/src/agent/agent.ts [warn] packages/codingcode/src/client/direct/settings.ts [warn] packages/codingcode/src/layer.ts [warn] packages/codingcode/src/server/routes/settings.ts [warn] packages/codingcode/src/subagent/registry.ts [warn] packages/codingcode/src/tools/domains/web/search.ts [warn] packages/codingcode/test/prompts/system-prompt.test.ts [warn] packages/codingcode/test/tools/websearch.test.ts [warn] packages/desktop/src/agent/AutomationForm.tsx [warn] packages/desktop/src/agent/AutomationPanel.tsx [warn] packages/desktop/src/agent/MessageStream.tsx [warn] packages/desktop/src/lib/core-api.ts [warn] packages/desktop/test/assistant-content-by-turn.test.ts [warn] Code style issues found in 13 files. Run Prettier with --write to fix. " ❯ packages/codingcode/test/ci/tooling-scripts.test.ts:48:87

AssertionError: expected "spy" to be called with arguments: [ 'my-skill', false, …(1) ] Received: 1st spy call: [ - "my-skill", - false, { "cwd": "/project/dir", + "enabled": false, + "name": "my-skill", }, ] Number of calls: 1 ❯ packages/desktop/test/core-api.test.ts:219:38

AssertionError: expected "spy" to be called with arguments: [ 'my-skill', true, { cwd: '' } ] Received: 1st spy call: [ - "my-skill", - true, { "cwd": "", + "enabled": true, + "name": "my-skill", }, ] Number of calls: 1 ❯ packages/desktop/test/core-api.test.ts:213:38

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

This generator function does not have 'yield'

'code' is defined but never used. Allowed unused args must match /^_/u

This generator function does not have 'yield'

'ESTIMATED_SUMMARY_TOKENS' is assigned a value but never used. Allowed unused vars must match /^_/u

'resolveHookDisabled' is defined but never used. Allowed unused vars must match /^_/u

'resolveMcpDisabled' is defined but never used. Allowed unused vars must match /^_/u

'getLLMClient' is defined but never used. Allowed unused vars must match /^_/u

Unnecessary escape character: \'

'AgentProfile' is defined but never used. Allowed unused vars must match /^_/u

'appendFileSync' is defined but never used. Allowed unused vars must match /^_/u

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/