Run jobs on Windows runners (windows-* labels) under native pwsh. Native Windows build and process checks contribute to the pull-request all checks passed verdict; Wine runs Windows Node on hosted Linux only in ci-master.yml. Python runtime CI checks Linux/Windows x64 on pull requests and Linux ARM64 plus both macOS architectures on master pushes; releases retain all five targets (platform policy). ci.yml is pull-request-only. Master-only platform checks, Linux/Windows self-hosted standbys, and manual runner benchmarks live in ci-master.yml, which listens to master…
This workspace owns @deepseek-ai/node-addon-system: the Linux landlock-run confinement executable and the POSIX system.node binding. It shares the root pnpm workspace and lockfile; native packages have one independent version and release workflow. packages/entry/ owns JavaScript, types, and auditable C sources. Platform packages hold only binaries and metadata. scripts/ owns native builds, packing, validation, and release; test/ owns real process and lock behavior. Run pnpm build:ts, pnpm build:native, pnpm build:test-oracle, pnpm typecheck, and pnpm test in this directory. Linux full builds require…
Rules for packages/client/* (the browser side of the dsh web GUI) plus its build entry apps/web. They supplement the repo-wide conventions and the package rules. Read the current Web Client architecture, Slots reference, and Conversation reference before changing the corresponding layer. Packages here are named with the directory prefix: @deepseek-ai/dsh-client-<name>. The Slots reference owns the current design; these are the rules you must not violate when writing or reviewing client code: How live data reaches render code,
These rules supplement the package rules. The experimental publication decision owns the publication policy; the Agent Teams package decision owns dependency isolation and promotion rationale.
Gate scripts invoke pnpm shell-free, normalize repository-relative glob paths to / at ingestion, and keep platform adaptation in the gate that needs it instead of a shared platform layer. Source-ownership gates use syntax-aware discovery, guard against an empty or narrowed corpus, and test every admitted/excluded form that changes their detection boundary. Script specs run in forked workers beside the rest of the suite and beside the other gate processes in their job, so own every port, temporary path, and child…
This tree contains only tests whose committed session JSONL is replay input and expected persisted output. Keep non-session ARIA, geometry, generator, CLI, and unit expected output with its owning app, script, or package; use test:expected, test:web, or test for its owning tier. Every process under test starts through the dsh CLI with a shipped profile and optional scenario patches. Test clients may drive a public protocol or browser interface; do not add another application entrypoint, hidden CLI mode, or executable…
Follow the root instructions, the documentation standard, and the documentation workflow. website/ owns only VitePress configuration, presentation assets, and the publication manifest. This file is the only maintained Markdown file in this subtree. Keep canonical prose and generated catalogs in their owning docs/ tier, then expose selected pages through docs.ts. Never add locale, route, API, or copied documentation trees such as website/zh-CN/, website/en/, or website/api/. The projector writes disposable Markdown to the ignored website/.generated/ directory. Never edit or commit .generated/,…
This file provides guidance on how to work with the n8n repository. n8n is a workflow automation platform written in TypeScript, using a monorepo structure managed by pnpm workspaces. It…
Shared n8n skills live in .agents/skills. These are the canonical source for skills that should work across Claude Code, OpenCode, and future agent harnesses. Claude plugin skills should usually be…
This file provides instructions for AI coding agents working with the VS Code codebase. For detailed project overview, architecture, coding guidelines, and validation steps, see the Copilot Instructions.
Custom personas with specific tools, instructions, and behaviors. Use for orchestrated workflows with role-based tool restrictions. Use reasoning-effort to set the reasoning level for the custom agent's model: The selected model must support the configured level. If omitted, the runtime resolves the effort from the model configuration and, when applicable, the parent agent. Sources: built-in aliases, specific tools, MCP servers (<server>/*), extension tools. Special: [] = no tools, omit = defaults. Body reference: #tool:<name> To discover available tools, check your…
This folder contains the Copilot CLI integration for VS Code Chat. It enables users to open a new Chat window and interact with a Copilot CLI agent instance directly within VS Code. VS Code provides the UI, Copilot CLI SDK provides the smarts. Important: The Copilot CLI agent functionality is powered by the @github/copilot/sdk package. See the SDK package for full type definitions. The integration follows VS Code's platform layering pattern with three layers:
IAuthenticationService manages GitHub and Copilot authentication. It provides GitHub sessions (OAuth tokens) and Copilot tokens (CAPI tokens). getGitHubSession requires a kind parameter. Choose thoughtfully: Returns AuthenticationSession (never undefined). Throws if the user cancels. Requires createIfNone with a StrictAuthenticationPresentationOptions containing a localized detail string explaining why auth is needed: Same as above but forces re-authentication even if a session exists. Use when the current token has lost authorization: Returns AuthenticationSession | undefined. Never shows UI. Use when auth is optional: For…
Node runtime service construction is documented separately in node/serviceBootstrapping.md. Host startup timings, process-lifetime correlation, and session workload counts are documented in PERFORMANCE.md. Status: COMPLETE (2026-07-01) All waves A–D and gates G-B1, G-C1, G-C2, G-D1 are done. Codex, Claude, and Copilot all use the unified orchestrator path. Codex advertises multipleChats: { fork: true, sideChat: true }. Model-backed peer, fork, and side-chat parity scenarios run in deterministic replay. The operational chat surface (send/abort/model/agent/history) is fully chat-addressed and uniform across harnesses. Session ownership…