Search the Governance Graph

> Save 98% of your context window. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and native Cursor v1.7+ hook routing for context protection.

> Save 98% of your context window. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and native Cursor v1.7+ hook routing for context protection. context-mode is an MCP server + hook bundle that keeps long-running Cursor agent sessions from blowing through their context window. Three pillars: - Sandboxed execution — ctxexecute, ctxexecutefile, ctxbatchexecute run code in 11 languages (Node, Python, Bun, Deno, Ruby, Go, Rust, Java, C, C++, Shell). Only stdout

<!-- Brief: what changed, why, and implementation approach. Link issue: Fixes #000 -->

- [ ] Claude Code - [ ] Cursor - [ ] VS Code Copilot (GitHub Copilot) - [ ] JetBrains Copilot - [ ] Gemini CLI - [ ] Qwen Code - [ ] OpenCode - [ ] KiloCode - [ ] Codex CLI - [ ] OpenClaw (Pi Agent) - [ ] Pi - [ ] Kiro - [ ] Antigravity - [ ] Zed - [ ] All platforms - [ ] Tests added/updated (TDD: red → green) - [ ] npm test passes - [ ] npm run typecheck passes - [ ] Docs updated if needed (README, platform-support.md) - [ ] No Windows path regressions (forward slashes only) - [ ] Targets next

> Benchmarked against real outputs from popular Claude Code MCP servers, Skills, and dev tools.

> Benchmarked against real outputs from popular Claude Code MCP servers, Skills, and dev tools. > All fixtures captured from actual tool invocations — not synthetic data. | Metric | Value | |--------|-------| | Total scenarios | 21 | | Tools benchmarked | ctxexecutefile (summarize) + ctxindex/ctxsearch (knowledge retrieval) | | Large output handling | Auto-externalize to FTS5 (>100 KB → pointer) | | Total raw data processed | 376 KB | | Total context consumed | 16.5 KB | | Overall context

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via ctxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Intercepted and replaced with

context-mode MCP tools are installed for this agy session. Use them when the task analyzes, counts, filters, compares, searches, parses, transforms, fetches, or otherwise processes data. Raw bytes should stay in the sandbox; only the derived answer should enter the conversation. Do NOT use context-mode/ctxexecutefile or ctxexecute to print a whole file or a full method/config (e.g. print(FILECONTENT), cat config.yaml, dumping a 281-line file). That defeats the purpose: on agy the tool's stdout

context-mode MCP tools are available in agy as context-mode/. Use these tools directly. Do not inspect cached schema files under /.gemini/antigravity-cli/mcp/context-mode/.json, and do not run ctxexecute just to discover tool names or schemas. If agy uses the generic MCP wrapper, call callmcptool with: - ServerName: "context-mode" - ToolName: one of the tool names below - Arguments: the JSON arguments for that tool - context-mode/ctxexecute: run JavaScript, TypeScript, Python, shell, or other

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Antigravity has NO hooks — these instructions are ONLY enforcement. Follow strictly.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Antigravity has NO hooks — these instructions are ONLY enforcement. Follow strictly. Analyze/count/filter/compare/search/parse/transform data: write code via mcpcontext-modectxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess).

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via ctxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Intercepted and replaced with

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Codex CLI hooks provide runtime enforcement when features.hooks = true; these instructions remain mandatory model-side enforcement. Follow strictly.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Codex CLI hooks provide runtime enforcement when [features].hooks = true; these instructions remain mandatory model-side enforcement. Follow strictly. Analyze/count/filter/compare/search/parse/transform data: write code via ctxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript —

One-command install of the context-mode MCP server (and routing skill) into GitHub Copilot CLI, with no context-mode upgrade / agent call required: This registers: - MCP server (.mcp.json) — exposes the ctx tools (ctxexecute, ctxbatchexecute, ctxsearch, ctxfetchandindex, …). The server is launched with CONTEXTMODEPLATFORM=copilot-cli, so it self-identifies as Copilot regardless of any other CLI installed on the machine — ctxupgrade and platform detection resolve copilot-cli, never a

context-mode MCP tools are available in GitHub Copilot CLI. These rules protect the context window from flooding — one unrouted command can dump tens of KB into the conversation. Follow them strictly. Analyze / count / filter / compare / search / parse / transform data: write code via ctxexecute(language, code) and console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, do not COMPUTE it by reading. One script replaces ten tool calls. - curl / wget — dumps raw

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via mcpcontext-modectxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Shell curl/wget

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via ctxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Terminal curl/wget intercepted

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via context-modectxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Shell curl/wget

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via @context-mode/ctxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Shell curl/wget

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. context-mode delivers via MCP for OMP; native OMP pre/post tool-call hooks are not yet wired by this adapter, so these rules are the only enforcement path. Treat them as MUST. Analyze/count/filter/compare/search/parse/transform data: write code via ctxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via context-modectxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Shell curl/wget

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via context-modectxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Shell curl/wget

Use ctx tools. The extension injects routing rules — follow them. Note for Pi users: if this project also has CLAUDE.md, Pi.dev reads both files and duplicates routing instructions in context — remove one.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via mcpcontext-modectxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Bash curl/wget

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via ctxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess). try/catch, handle null/undefined. One script replaces ten tool calls. Terminal curl/wget intercepted

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Zed has NO hooks — these instructions are ONLY enforcement. Follow strictly.

context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Zed has NO hooks — these instructions are ONLY enforcement. Follow strictly. Analyze/count/filter/compare/search/parse/transform data: write code via mcp:context-mode:ctxexecute(language, code), console.log() only the answer. Do NOT read raw data into context. PROGRAM the analysis, not COMPUTE it. Pure JavaScript — Node.js built-ins only (fs, path, childprocess).

This project is licensed under the Elastic License 2.0 ELv2 and moves forward with your support. Every issue, every PR, every idea matters.

This project is licensed under the Elastic License 2.0 (ELv2) and moves forward with your support. Every issue, every PR, every idea matters. Don't overthink it. Don't ask yourself "is my PR good enough?" or "is this issue too small?" -- just send it. A rough draft beats a perfect plan that never ships. If you found a bug, report it. If you have an idea, open an issue. If you wrote a fix, submit the PR. That said, I'm a solo maintainer with limited time. The best way to help me help you: follow

Setup guide for using context-mode with Kimi Code CLIhttps://moonshotai.github.io/kimi-code/en/customization/hooks.html.

Setup guide for using context-mode with Kimi Code CLI. Kimi Code CLI uses a JSON stdin/stdout hook paradigm similar to Claude Code and Codex CLI, with TOML-based configuration in /.kimi-code/config.toml. - Kimi Code CLI installed (kimi binary in PATH) - context-mode installed globally: | Feature | Status | |---------|--------| | PreToolUse | Deny only (exit code 2 or permissionDecision: "deny") | | PostToolUse | Yes | | SessionStart | Yes (session continuity DB only; see note) | | SessionEnd

context-mode plugin for the OpenClawhttps://github.com/openclaw gateway, targeting Pi Agent sessions.

context-mode plugin for the OpenClaw gateway, targeting Pi Agent sessions. OpenClaw is the gateway/platform that manages agent sessions, extensions, and tool routing. Pi Agent is OpenClaw's coding agent — it runs within OpenClaw and provides Read, Write, Edit, and Bash tools for software development tasks. The context-mode adapter hooks into Pi Agent sessions specifically, intercepting tool calls to route data-heavy operations through the sandbox and tracking session events for compaction

- Status: Accepted - Date: 2026-05-14 - Version: v1.0.130 - Supersedes: the v1.0.128 single-writer guard and its v1.0.129 hotfix - Reviewers: 10 parallel grill verdicts (UX, SQLite, Security, Perf, Architect, Test, SRE, PM, Data, DevEx) v1.0.128 introduced two new defenses inside SQLiteBase (the shared ctor for SessionDB and ContentStore): 1. acquireDbLock(dbPath) — an OEXCL .lock file containing the owning PID. Subsequent openers that found a live PID inside the lockfile threw

- Status: Accepted - Date: 2026-05-24 - PR: #683 (substitutes #654) - Supersedes: organic, undocumented description drift - Reviewers: owner Mert, empirical A/B (38 trials × 6 probes on Haiku + Sonnet) context-mode registers 11 ctx MCP tools via server.registerTool() in src/server.ts. Each tool description is read by every host LLM (Claude / GPT / Gemini / Llama / …) at tool-selection time. Over many releases the corpus drifted toward forbidding language — MANDATORY:, NEVER, Do NOT, REFUSAL

- Status: Accepted — amended 2026-05-24 (PR #683 follow-up) to drop the "NOT a network restriction" negation prescription; see §Amendment. - Date: 2026-05-24 - PR: #683 (substitutes #654) - Motivating bug: kerneltoast / @noctivoro / Mert reproduced on Opus 4.6 - Reviewers: owner Mert hooks/core/routing.mjs returns deny reasons for intercepted Bash, Read, Grep, and WebFetch calls. These reasons are displayed to the agent at runtime and shape the agent's next-action decision. PR

- Status: Accepted - Date: 2026-05-24 - PR: #685 (v1.0.148 hotfix) - Supersedes: v1.0.134 SLICE B (incidental fix in commit ce62275) - Acknowledgement: 7-agent EM ops audit (Git Archaeologist, DB Architect, Math Engineer, QA Engineer, PO/UX Engineer, Edge Case Engineer, Architect) produced the converged verdict ratified here. The per-conversation Section 1 Without context-mode / With context-mode bar in ctxstats quietly drifted from "honest compression ratio" to "infrastructure-size

Setup guide for using context-mode with JetBrains IDEs IntelliJ IDEA, WebStorm, PyCharm, etc. via the GitHub Copilot plugin.

Setup guide for using context-mode with JetBrains IDEs (IntelliJ IDEA, WebStorm, PyCharm, etc.) via the GitHub Copilot plugin. - Node.js 18+ (node --version) - JetBrains IDE — any JetBrains IDE (IntelliJ IDEA, WebStorm, PyCharm, GoLand, Rider, CLion, etc.) - GitHub Copilot plugin v1.5.57+ — install from Settings > Plugins > Marketplace, search "GitHub Copilot" JetBrains configures MCP servers via the Settings UI, not a file. 1. Open your JetBrains IDE. 2. Go to Settings > Tools > AI Assistant >

This document provides a comprehensive comparison of all platforms supported by context-mode, including their hook paradigms, capabilities, configuration, and known limitations.

This document provides a comprehensive comparison of all platforms supported by context-mode, including their hook paradigms, capabilities, configuration, and known limitations. context-mode supports 17 client platforms, plus the OpenClaw gateway integration, across three hook paradigms: | Paradigm | Platforms | |----------|-----------| | JSON stdin/stdout | Claude Code, Gemini CLI, VS Code Copilot, JetBrains Copilot, GitHub Copilot CLI, Cursor, Codex CLI, Qwen Code, Kimi Code, Antigravity CLI

context-mode references a small set of operating-discipline skills authored by Matt Pocock (MIT). They are the operational backbone of the context-mode-ops skill (/diagnose, /tdd, /grill-me, /grill-with-docs, /improve-codebase-architecture). These skills are referenced, not vendored. Maintainers install them locally via the upstream skills CLI. Shipping them to every plugin install would pay description tokens for tools end users never invoke, so they stay out of this repo. - Repository:

The other half of the context problem. Used across teams at Every MCP tool call dumps raw data into your context window. A Playwright snapshot costs 56 KB. Twenty GitHub issues cost 59 KB. One access log — 45 KB. After 30 minutes, 40% of your context is gone. And when the agent compacts the conversation to free space, it forgets which files it was editing, what tasks are in progress, and what you last asked for. On top of that, the agent wastes output tokens on filler, pleasantries, and

You are running inside a tier-2 E2E smoke test for the context-mode plugin. The harness will read /ctx-stats afterwards and assert that ctxindex, ctxsearch, and ctxexecute were each invoked at least once and that tokenssaved is strictly positive. The corpus below is intentionally large enough that a real indexing + search round-trip produces a measurable saving; do not skip steps and do not paraphrase the corpus from memory. Step 1 — Index the following project files in this exact order using

Avoid these pitfalls when using context-mode tools. --- Problem: execute adds overhead (LLM summarization call). For small outputs, Bash is faster and cheaper. Rule: If the output fits comfortably in your context window (under 20 lines), use Bash directly. Reserve execute for outputs that would bloat context or need intelligent summarization. More examples of "just use Bash": - git status — usually 5-10 lines - ls -la — directory listing - cat .env.example — small config file - pwd, whoami,

Practical patterns for using execute with language: javascript. All examples assume Node.js runtime with native fetch (Node 18+). --- > summaryprompt: "Report overall health, list any degraded services, and highlight errors" > summaryprompt: "Summarize issue distribution by label, highlight stale issues, suggest priorities" > timeoutms: 30000 --- > summaryprompt: "Report compiler strictness, module system, and any unusual configuration" > summaryprompt: "List all configuration differences

Practical patterns for using execute with language: python. All examples use Python standard library only (no pip installs required). --- > summaryprompt: "Report user distribution, data quality issues, and any anomalies found" > summaryprompt: "List all local config overrides and flag any potentially dangerous changes" --- > summaryprompt: "Summarize transaction patterns, highlight outliers, report category distribution" > summaryprompt: "Report error rates, identify the most common failures,

Practical patterns for using execute with language: shell. Best for piping, filtering, and leveraging native OS tools. --- shell npx tsc --noEmit 2>&1 | tee /tmp/tsc-output.txt EXITCODE=${PIPESTATUS[0]} echo "=== TypeScript Check ===" echo "Exit code: $EXITCODE" TOTALERRORS=$(grep -c 'error TS' /tmp/tsc-output.txt 2>/dev/null || echo 0) echo "Total errors: $TOTALERRORS" if [ "$TOTALERRORS" -gt 0 ]; then echo "" echo "=== Errors by Code ===" grep -oP 'error TS\d+' /tmp/tsc-output.txt |

Default to context-mode for ALL commands. Only use Bash for guaranteed-small-output operations. Bash whitelist (safe to run directly): - File mutations: mkdir, mv, cp, rm, touch, chmod - Git writes: git add, git commit, git push, git checkout, git branch, git merge - Navigation: cd, pwd, which - Process control: kill, pkill - Package management: npm install, npm publish, pip install - Simple output: echo, printf Everything else → ctxexecute or ctxexecutefile. Any command that reads, queries,

Run diagnostics and display results directly in the conversation. 1. Call the ctxdoctor MCP tool directly. It runs all checks server-side and returns a plain-text status report. 2. Display the results verbatim — they are already formatted with plain-text status prefixes: [OK] PASS, [FAIL] FAIL, [WARN] WARN. Renderer-safe (no markdown task-list syntax) for cross-client compatibility (e.g., Z.ai GLM). 3. Fallback (only if MCP tool call fails): Derive the plugin root from this skill's base

Index local project content for later search. 1. Prefer the ctxindex MCP tool when it is available. 2. Ask for a path only if the user did not provide one and the current project root is ambiguous. 3. Use path, not large inline content, so file bytes do not enter the conversation. 4. For repository indexing, pass conservative bounds and a clear source label: 5. If MCP tools are unavailable, fall back to the CLI: 6. Report the indexed source label, file count or section count, and the matching

Open the hosted Insight dashboard in the user's default browser. 1. Call the ctxinsight MCP tool (no parameters). It opens in the default browser and returns a confirmation line. 2. Display the tool's output to the user. 3. Tell the user: - "Insight opened at https://context-mode.com/insight" - The landing page at context-mode.com/insight is the single source of truth for sign-in and pricing details. - If the browser did not open automatically, share the URL so they can open it

Permanently deletes session data for this project. Two scopes are supported issue #520:

Permanently deletes session data for this project. Two scopes are supported (issue #520): - Project scope (scope: "project"): wipes EVERYTHING — knowledge base, all session DB rows for every session, events markdown, and stats. - Session scope (sessionId: "" or scope: "session"): wipes ONLY the matching session's rows + FTS5 chunks. Sibling sessions, project stats, and the FTS5 store file are preserved. 1. Decide the scope first with the user: - "Wipe just one session?" → ask for the

Search indexed content without rereading raw sources into conversation context. 1. Prefer the ctxsearch MCP tool when it is available. 2. Batch all related questions in one queries array. 3. Scope with source when the user names a project or indexed label. 4. Use short, specific queries of two to four technical terms. 5. If MCP tools are unavailable, fall back to the CLI: 6. If the index is empty, tell the user to run /context-mode:ctx-index or context-mode index first.

Show context savings for the current session. 1. Call the mcpcontext-modectxstats MCP tool (no parameters needed). 2. CRITICAL: You MUST copy-paste the ENTIRE tool output as markdown text directly into your response message. Do NOT summarize, do NOT collapse, do NOT paraphrase. The user must see the full tables without pressing ctrl+o. Copy every line exactly as returned by the tool. 3. After the full output, add ONE sentence highlighting the key savings metric, e.g.: - "context-mode saved

Pull latest from GitHub and reinstall the plugin. 1. Call the ctxupgrade MCP tool directly. It returns a shell command to execute. 2. Run the returned command using your shell execution tool (Bash, shellexecute, etc.). 3. Display results as a markdown checklist: Use [x] for success, [ ] for failure. Show actual version numbers. 4. Tell the user to restart their session to pick up the new version. 5. Fallback (only if MCP tool call fails): Derive the plugin root from this skill's base

▲ Next.js 15.1.0 - Environments: .env.local Creating an optimized production build ... ✓ Compiled src/app/page.tsx (342ms) ✓ Compiled src/app/layout.tsx (128ms) ✓ Compiled src/app/loading.tsx (45ms) ✓ Compiled src/app/error.tsx (52ms) ✓ Compiled src/app/not-found.tsx (38ms) ✓ Compiled src/app/dashboard/page.tsx (456ms) ✓ Compiled src/app/dashboard/layout.tsx (189ms) ✓ Compiled src/app/dashboard/settings/page.tsx (234ms) ✓ Compiled src/app/dashboard/analytics/page.tsx

Source: https://github.com/vercel/next.js/blob/canary/docs/01-app/02-guides/migrating/app-router-migration.mdx

Source: https://github.com/vercel/next.js/blob/canary/docs/01-app/02-guides/migrating/app-router-migration.mdx Shows how to create a new page.tsx file in the app directory that acts as a Server Component by default. This component imports the Client Component and handles data fetching using the new data fetching APIs. The fetched data is then passed as props to the Client Component. -------------------------------- Source:

Source: https://react.dev/reference/react/useEffect The useEffect Hook allows you to declare side effects in functional components. It accepts a setup function and optional dependencies array, running the setup after component commits and cleanup before re-runs or unmounting. js useEffect(setup, dependencies?) js import { useState, useEffect } from 'react'; import { createConnection } from './chat.js'; function ChatRoom({ roomId }) { const [serverUrl, setServerUrl] =

Source: https://github.com/supabase/supabase/blob/master/apps/docs/content/guides/functions/unit-test.mdx

Source: https://github.com/supabase/supabase/blob/master/apps/docs/content/guides/functions/unit-test.mdx This TypeScript example demonstrates a unit test for Supabase Edge Functions using Deno. It shows how to initialize a Supabase client with environment variables, test client creation and database connectivity, and invoke an Edge Function to assert its response. Source: https://github.com/supabase/supabase/blob/master/apps/docs/content/guides/functions/connect-to-postgres.mdx Source:

Source: https://github.com/tailwindlabs/tailwindcss.com/blob/main/src/docs/responsive-design.mdx

Source: https://github.com/tailwindlabs/tailwindcss.com/blob/main/src/docs/responsive-design.mdx Demonstrates how to create a responsive layout that switches from block display on mobile to flex display on medium screens and larger. Uses md:flex to enable flexbox at the medium breakpoint, md:shrink-0 to prevent image shrinking, and md:h-full md:w-48 to constrain image dimensions on larger screens. -------------------------------- Source:

f8a3b1c 2026-02-23 Mert Koseoglu feat: add user role management with audit logging

f8a3b1c 2026-02-23 Mert Koseoglu feat: add user role management with audit logging d7e2a0b 2026-02-23 Mert Koseoglu refactor: improve UserList component with skeleton loading c6d1f9a 2026-02-23 Mert Koseoglu feat: add email magic link authentication b5c0e8f 2026-02-22 Alice Johnson fix: resolve null updatedAt in user role mutation a4b9d7e 2026-02-22 Alice Johnson test: add comprehensive billing router tests 93a8c6d 2026-02-22 Mert Koseoglu feat: add middleware route protection 82f7b5c

[GET] https://news.ycombinator.com/ => [200] [GET] https://news.ycombinator.com/news.css?u2KnqsTjKhcQjbDNi8PU => [200] [GET] https://news.ycombinator.com/y18.svg => [200] [GET] https://news.ycombinator.com/s.gif => [200] [GET] https://news.ycombinator.com/hn.js?u2KnqsTjKhcQjbDNi8PU => [200] [GET] https://news.ycombinator.com/triangle.svg => [200] [GET] https://news.ycombinator.com/y18.svg => [200]

- Page URL: https://news.ycombinator.com/ - Page Title: Hacker News

RUN v2.1.8 /Users/mert/projects/my-saas-app ✓ src/components/Button.test.tsx (3 tests) 45ms ✓ renders correctly 12ms ✓ handles click events 18ms ✓ applies variant classes 15ms ✓ src/components/Avatar.test.tsx (3 tests) 38ms ✓ renders with image 14ms ✓ renders fallback initials 11ms ✓ handles loading state 13ms ✓ src/components/Card.test.tsx (4 tests) 52ms ✓ renders children 8ms ✓ applies custom className 12ms ✓ renders header and footer 19ms ✓ handles onClick

src/components/UserList.tsx23,15: error TS2345: Argument of type 'string' is not assignable to parameter of type 'number'.

src/components/UserList.tsx(23,15): error TS2345: Argument of type 'string' is not assignable to parameter of type 'number'. src/components/UserList.tsx(45,8): error TS2339: Property 'fullName' does not exist on type 'User'. src/components/UserList.tsx(67,22): error TS2532: Object is possibly 'undefined'. src/components/UserList.tsx(89,3): error TS2741: Property 'email' is missing in type '{ name: string; }' but required in type 'User'. src/components/UserList.tsx(102,18): error TS2769: No

这是一个 UTF-8 编码测试文件 包含中文字符、日本語、한국어 特殊符号：€ £ ¥ © ® ™ → ← ↑ ↓ Emoji: 🔒 🛡️ ⚠️ ✅ ❌ 混合内容 mixed content 混在一起 第六行 line six 最后一行