chore: remove neuledge-context skill and multiple kyberforge skills
Deletes the neuledge-context skill (.agents/skills/) and four kyberforge plugin skills — marketplace-architect, plugin-create, promptfoo, and write-agent — along with associated docs (adding-agents.md, plugin-marketplace-architecture.md). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,12 +0,0 @@
|
||||
```yaml
|
||||
version: "1.2"
|
||||
updated: 2026-06-21
|
||||
|
||||
when: Invoked when the user asks to install @neuledge/context, wire it as a Claude Code MCP server, manage documentation packages from the registry or custom sources, configure custom registry servers, or manage private registry auth. Also invoked when the user wants to scope an MCP session to specific libraries via --libs.
|
||||
|
||||
references:
|
||||
# README — source for references/context-cli-reference.md, references/http-mode.md, references/install-notes.md
|
||||
- https://github.com/neuledge/context
|
||||
# Download Server API spec — source for self-hosted registry section in references/install-notes.md
|
||||
- https://github.com/neuledge/context/blob/main/SERVER_SPEC.md
|
||||
```
|
||||
@@ -1,127 +0,0 @@
|
||||
---
|
||||
name: neuledge-context
|
||||
description: "Use when the user wants to install @neuledge/context, register it as a Claude Code MCP server, manage documentation packages (install, browse, add, remove, list), configure custom registries, or manage auth for private registries. Do NOT use when the user wants to install a different MCP server, wants to query docs from an already-running context server (call `get_docs` directly), or is setting up @neuledge/context for Cursor, VS Code Copilot, or Claude Desktop rather than Claude Code."
|
||||
metadata:
|
||||
category: cross-cutting
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
- Edit
|
||||
---
|
||||
|
||||
<requirements>
|
||||
|
||||
## Required inputs
|
||||
|
||||
- **Task type** — install / register-mcp / package-management / auth / upgrade / uninstall; inferred from user request, ask if ambiguous
|
||||
- **Package name(s)** (package management only) — name(s) to install, add, or remove; ask if not stated
|
||||
- **Library list** (project MCP scope only) — space-separated lib names for `--libs`; ask if not stated
|
||||
- **Domain** (auth only) — domain to authenticate against; ask if not stated
|
||||
- **Credential reference** (auth only) — environment variable or secret manager path holding the token or cookie; never the raw value
|
||||
|
||||
## Constraints
|
||||
|
||||
- Run `scripts/setup-neuledge-context.sh <VERSION>` for install and upgrade — never run `npm install -g @neuledge/context@latest`
|
||||
- Run `scripts/secure-context-config.sh` immediately after every `context auth add` — never skip the permissions step
|
||||
- Check `git --version` before running `context add` on a URL or GitHub source; skip the check for local `.db` file paths
|
||||
- Never echo, repeat, or log auth token or cookie values — reference the environment variable name only
|
||||
- Scope all steps to stdio mode; HTTP/Docker mode is documented in `references/http-mode.md`, not covered here
|
||||
- State what you are about to do before running `setup-neuledge-context.sh` — it modifies global npm and Claude Code MCP config
|
||||
|
||||
</requirements>
|
||||
|
||||
<steps>
|
||||
|
||||
## Process
|
||||
|
||||
1. **Identify task.** Infer the task type from the user's request. If the request spans multiple tasks (e.g. install + package install), execute them in the order listed below.
|
||||
|
||||
2. **Install.** (Skip if `context --version` already returns the target version.)
|
||||
- State: "I will run `scripts/setup-neuledge-context.sh` from the ai-development repo root — this installs `@neuledge/context` globally at the pinned version."
|
||||
- Run: `bash scripts/setup-neuledge-context.sh` from `/root/ai-development/`
|
||||
- Verify: `context --version`
|
||||
- See `references/install-notes.md` for prerequisites and native SQLite build tool requirements.
|
||||
|
||||
3. **Register global MCP server.** (One-time per machine. Skip if already registered at user scope.)
|
||||
- Check: `claude mcp list | grep '^context '` — if output is non-empty, skip.
|
||||
- Run: `claude mcp add -s user context -- context serve`
|
||||
- Confirm: `claude mcp list`
|
||||
- Note: the default scope for `claude mcp add` is `local` (machine-specific, not shared). Always pass `-s user` for global availability across all projects.
|
||||
- Note: MCP tools (`search_packages`, `get_docs`, `download_package`) only appear in the active session after `/reload-plugins` or starting a new session — they are not immediately available mid-session after registration.
|
||||
|
||||
4. **Scope MCP to specific libraries (optional, per-project).** (When user wants to restrict the MCP session to pre-approved libraries for a project.)
|
||||
- Collect the library list from the user if not stated.
|
||||
- Verify each identifier: run `context list` — copy the identifier **exactly** as shown, including any version suffix (e.g., `claude-code-docs@latest`, not `claude-code-docs`). The `--libs` filter does an exact string match; a bare name without the suffix will silently exclude the package and `get_docs` will return "Package not found". For registry packages not yet installed, use `context browse <name>` to find the name, then install and re-run `context list`.
|
||||
- Run: `claude mcp add -s project context -- context serve --libs <verified-id1> <verified-id2> ...`
|
||||
- This writes to `.mcp.json` in the project root — commit this file to share the scope with the team.
|
||||
- `.mcp.json` can also be edited directly if the identifier list needs updating. Changes take effect only in a new Claude Code session — `/reload-plugins` reloads skill manifests but does not restart stdio MCP server processes.
|
||||
- If both user and project scopes exist for the same server name, Claude Code will warn about dual registration — this is expected. Project scope overrides user scope within the project directory.
|
||||
- Note: with `--libs`, the `search_packages` and `download_package` MCP tools are hidden; only `get_docs` is available for the listed libraries.
|
||||
|
||||
5. **Manage packages.**
|
||||
- **Browse registry:** `context browse <name>` — shows available versions. The public registry is JS/frontend-focused; key AI/agent packages (Anthropic SDK, Claude Code, MCP SDK) are absent — use `context add` for those.
|
||||
- **Install from registry:** `context install <registry/name> [version]` — e.g. `context install npm/react`.
|
||||
- **Add from source (for registry gaps):** Many docs sites publish `llms.txt`; prefer that over cloning. Check `<url>/llms.txt` or `<url>/llms-full.txt` before falling back to GitHub. Check `git --version` first if source is a GitHub repo URL.
|
||||
```bash
|
||||
context add https://docs.anthropic.com --name claude-docs # llms.txt site
|
||||
context add https://modelcontextprotocol.io --name mcp-docs # llms.txt site
|
||||
context add https://github.com/org/repo --path docs --name mylib # GitHub repo
|
||||
```
|
||||
See `references/context-cli-reference.md` for all flags.
|
||||
- **List installed:** `context list` — shows name, version, size, and section count. Section count is a health signal: a package with 0 or very few sections relative to its KB size was probably not indexed correctly.
|
||||
- **Remove:** `context remove <name>@<version>` to target a specific version; `context remove <name>` removes all versions — confirm with the user before removing all.
|
||||
- **Rebuild (when a package returns no query results):** A package can install successfully but produce no FTS5 search results if the source URL returned sparse content (e.g., a redirect page instead of the actual docs). Diagnose by checking section count in `context list` — a large KB size with few sections is a sign of a bad crawl. Fix: `context remove <name>` (confirm first), then re-add from a better source. Try `<url>/llms-full.txt` before `<url>/llms.txt` before the GitHub repo — `llms-full.txt` produces the most sections. After rebuild, verify with `context list` that section count has increased and spot-check with `context query <name> <topic>`.
|
||||
|
||||
6. **Configure auth.** (Private registries or subscriber-only content.)
|
||||
- Run: `context auth add <domain> --header "Authorization: Bearer $TOKEN"` — use the environment variable name, not the value.
|
||||
- Immediately run: `bash scripts/secure-context-config.sh` from `/root/ai-development/`
|
||||
|
||||
7. **Configure custom registry.** (Self-hosted registry server.)
|
||||
- Read `~/.context/config.json`. Add a server entry following the schema in `references/context-cli-reference.md`.
|
||||
- Test: `context browse <package> --server <name>`
|
||||
|
||||
8. **Upgrade.** Run `bash scripts/setup-neuledge-context.sh <TARGET_VERSION>` from `/root/ai-development/`. The script checks the current version and skips if already at target.
|
||||
|
||||
9. **Uninstall.**
|
||||
- Run: `npm uninstall -g @neuledge/context`
|
||||
- Ask the user before removing downloaded packages: `rm -rf ~/.context` deletes all installed documentation and config — confirm before running.
|
||||
|
||||
## Output format
|
||||
|
||||
No structured output file. The skill produces terminal confirmation of each completed step. Artifacts:
|
||||
- `@neuledge/context` installed globally at pinned version
|
||||
- MCP server entry in user config (global, `-s user`) or `.mcp.json` in project root (project-scoped, `-s project`, committed to repo)
|
||||
- Downloaded `.db` packages in `~/.context/packages/`
|
||||
- Modified `~/.context/config.json` (auth entries, registry config)
|
||||
|
||||
</steps>
|
||||
|
||||
<checks>
|
||||
|
||||
## Failure handling
|
||||
|
||||
- `scripts/setup-neuledge-context.sh` not found — stop; instruct user to run from `/root/ai-development/`
|
||||
- `context` binary not found after install — report npm error; check `node --version` is ≥18
|
||||
- MCP registration fails — run `claude mcp list` to check for name conflicts; if `context` is registered with different args or at the wrong scope, remove with `claude mcp remove context -s <scope>` and re-add at the correct scope
|
||||
- MCP tools not visible after registration — `claude mcp add` mid-session does not immediately expose tools; run `/reload-plugins` or start a new session
|
||||
- Dual-scope warning after adding project scope — expected when user and project scopes both define `context`; project takes precedence in the project directory. Remove the unwanted scope with `claude mcp remove context -s <scope>`
|
||||
- `context add` fails with "git not found" — advise `apt-get install git` (Debian/Ubuntu) or equivalent; re-run after install
|
||||
- Native SQLite build failure — Context falls back to WASM automatically; advise installing build tools for better performance: `apt-get install -y python3 make g++` on Debian/Ubuntu. See `references/install-notes.md` for known gotchas.
|
||||
- `get_docs` returns "Package not found" for a package that appears in `context list` — two causes: (1) `--libs` identifier mismatch: the identifier in `.mcp.json` must exactly match `context list` output including version suffix; edit `.mcp.json` and start a new session to apply; (2) bad crawl: the package indexed 0 or very few sections — rebuild per the Rebuild workflow in step 5.
|
||||
- `get_docs` returns results via CLI (`context query`) but not via MCP — the MCP server process is using the old `--libs` config from when the session started; changes to `.mcp.json` require a new session, `/reload-plugins` is not sufficient.
|
||||
|
||||
## Self-check
|
||||
|
||||
- [ ] Task type identified before any commands run
|
||||
- [ ] `setup-neuledge-context.sh` announced before execution
|
||||
- [ ] `claude mcp list` checked before `claude mcp add` — skipped if already registered at correct scope
|
||||
- [ ] `-s user` used for global registration; `-s project` used for `--libs` project scope — never relied on default (`local`) scope
|
||||
- [ ] `context list` used to get authoritative identifiers before composing `--libs` — identifiers copied verbatim including version suffix (e.g., `name@latest`)
|
||||
- [ ] `.mcp.json` noted for commit when project scope is added
|
||||
- [ ] `git --version` checked before `context add` on a URL or GitHub source
|
||||
- [ ] Auth step: `secure-context-config.sh` run immediately after every `context auth add`
|
||||
- [ ] No credential values echoed or logged — environment variable references only
|
||||
- [ ] `context remove <name>@<version>` used (not bare name) when targeting a specific version
|
||||
- [ ] `rm -rf ~/.context` confirmed with user before running
|
||||
|
||||
</checks>
|
||||
@@ -1,248 +0,0 @@
|
||||
# Context CLI Reference
|
||||
|
||||
Binary: `context`
|
||||
Package: `@neuledge/context`
|
||||
|
||||
---
|
||||
|
||||
## `context add <source>`
|
||||
|
||||
Build and install a documentation package from any source.
|
||||
|
||||
**Arguments:**
|
||||
- `<source>` — Package source. Auto-detected type:
|
||||
- Local `.db` file path → copies directly
|
||||
- HTTP(S) URL ending in `.db` → downloads
|
||||
- GitHub URL or git repo URL → clones and builds
|
||||
- Local directory path → builds from local docs
|
||||
- Website URL → fetches `llms.txt` and builds
|
||||
|
||||
**Options:**
|
||||
|
||||
| Flag | Description |
|
||||
|------|-------------|
|
||||
| `--tag <tag>` | Git tag to checkout (for git repos) |
|
||||
| `--pkg-version <version>` | Custom version label for the built package |
|
||||
| `--path <path>` | Path to docs folder within the repo or directory |
|
||||
| `--name <name>` | Custom package name (overrides auto-detected name) |
|
||||
| `--save <path>` | Save a copy of the built `.db` file to this location |
|
||||
| `--lang <code>` | Language filter: `all` for all languages, or ISO code (`en`, `de`, etc.) |
|
||||
|
||||
**Examples:**
|
||||
```bash
|
||||
context add https://github.com/prisma/prisma
|
||||
context add ./my-local-docs --name mylib --pkg-version 2.0
|
||||
context add https://mysite.com/docs --lang en
|
||||
context add /tmp/react-19.0.db
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## `context install <package> [version]`
|
||||
|
||||
Download and install a pre-built package from the registry.
|
||||
|
||||
**Arguments:**
|
||||
- `<package>` — Package identifier, e.g. `npm/next` or `next`
|
||||
- `[version]` — Specific version (latest used if omitted)
|
||||
|
||||
**Options:**
|
||||
|
||||
| Flag | Description |
|
||||
|------|-------------|
|
||||
| `--server <name>` | Named server from config (default: `neuledge`) |
|
||||
|
||||
**Examples:**
|
||||
```bash
|
||||
context install npm/next
|
||||
context install npm/react 18.0.0
|
||||
context install prisma --server myserver
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## `context browse <package>`
|
||||
|
||||
Search for packages available on the registry.
|
||||
|
||||
**Arguments:**
|
||||
- `<package>` — Package name or `registry/name`, e.g. `npm/next` or just `react`
|
||||
|
||||
**Options:**
|
||||
|
||||
| Flag | Description |
|
||||
|------|-------------|
|
||||
| `--server <name>` | Named server from config |
|
||||
|
||||
**Examples:**
|
||||
```bash
|
||||
context browse react
|
||||
context browse npm/next
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## `context list`
|
||||
|
||||
Display all installed packages with sizes and section counts.
|
||||
|
||||
```bash
|
||||
context list
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## `context remove <name>`
|
||||
|
||||
Remove an installed documentation package.
|
||||
|
||||
**Arguments:**
|
||||
- `<name>` — Package name or name with version, e.g. `next` or `next@v16.2.0`
|
||||
|
||||
**Examples:**
|
||||
```bash
|
||||
context remove next
|
||||
context remove next@v16.2.0
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## `context serve`
|
||||
|
||||
Start the MCP server.
|
||||
|
||||
**Options:**
|
||||
|
||||
| Flag | Description |
|
||||
|------|-------------|
|
||||
| `--http [port]` | Run as HTTP server (default port: 8080) instead of stdio |
|
||||
| `--host <host>` | Binding address for HTTP mode (default: `127.0.0.1`) |
|
||||
| `--libs <names...>` | Restrict session to specific libraries; hides search/download tools |
|
||||
|
||||
**Examples:**
|
||||
```bash
|
||||
context serve # stdio mode (for Claude Code, Cursor, etc.)
|
||||
context serve --http # HTTP on port 8080
|
||||
context serve --http 3000 # HTTP on port 3000
|
||||
context serve --http --host 0.0.0.0 # HTTP accessible on all interfaces
|
||||
context serve --libs react next # locked to react and next only
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## `context query <library> <topic>`
|
||||
|
||||
Query documentation from an installed package via CLI (no MCP needed).
|
||||
|
||||
**Arguments:**
|
||||
- `<library>` — Installed package in `name@version` format, e.g. `nextjs@15.0`
|
||||
- `<topic>` — Documentation topic, e.g. `createServer`, `cors middleware`
|
||||
|
||||
**Examples:**
|
||||
```bash
|
||||
context query nextjs@15.0 "app router"
|
||||
context query react@18.0 useState
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## `context auth`
|
||||
|
||||
Manage per-domain authentication for subscriber-only or private content.
|
||||
|
||||
### `context auth add <domain>`
|
||||
|
||||
Add or update authentication for a domain.
|
||||
|
||||
**Arguments:**
|
||||
- `<domain>` — Domain to authenticate against
|
||||
|
||||
**Options:**
|
||||
|
||||
| Flag | Description |
|
||||
|------|-------------|
|
||||
| `--cookies <cookies>` | Cookie header value |
|
||||
| `--header <header>` | Custom HTTP header (e.g. `Authorization: Bearer token`) |
|
||||
|
||||
**Example:**
|
||||
```bash
|
||||
context auth add docs.example.com --header "Authorization: Bearer mytoken"
|
||||
context auth add private.site.com --cookies "session=abc123"
|
||||
```
|
||||
|
||||
### `context auth list`
|
||||
|
||||
Display all configured authentication entries.
|
||||
|
||||
### `context auth remove <domain>`
|
||||
|
||||
Delete authentication for a domain.
|
||||
|
||||
---
|
||||
|
||||
## Config File
|
||||
|
||||
Location: `~/.context/config.json`
|
||||
Format: JSON
|
||||
|
||||
```json
|
||||
{
|
||||
"servers": [
|
||||
{
|
||||
"name": "neuledge",
|
||||
"url": "https://api.context.neuledge.com",
|
||||
"default": true
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
**Config keys:**
|
||||
|
||||
| Key | Type | Default | Description |
|
||||
|-----|------|---------|-------------|
|
||||
| `servers` | array | single Neuledge entry | Registry server configurations |
|
||||
| `servers[].name` | string | `"neuledge"` | Identifier used with `--server` flag |
|
||||
| `servers[].url` | string | `"https://api.context.neuledge.com"` | Server endpoint |
|
||||
| `servers[].default` | boolean | `true` | Primary server used when `--server` is omitted |
|
||||
|
||||
To add a self-hosted registry server:
|
||||
```json
|
||||
{
|
||||
"servers": [
|
||||
{ "name": "neuledge", "url": "https://api.context.neuledge.com", "default": true },
|
||||
{ "name": "myorg", "url": "https://context.myorg.internal" }
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Environment Variables
|
||||
|
||||
None documented. Config is file-based (`~/.context/config.json`).
|
||||
|
||||
---
|
||||
|
||||
## MCP Tool Reference (server-side)
|
||||
|
||||
When running `context serve`, these MCP tools are registered:
|
||||
|
||||
### `get_docs`
|
||||
Primary documentation lookup. Use before web searches when the library is installed.
|
||||
- `library` — `name@version`, e.g. `react@18.0`
|
||||
- `topic` — Short API name or keyword, e.g. `useState`, `cors middleware`
|
||||
|
||||
### `search_packages`
|
||||
Find available packages in a registry.
|
||||
- `registry` — `npm`, `pip`, `cargo`, `go`
|
||||
- `name` — Package name
|
||||
- `version` (optional) — Specific version
|
||||
- `server` (optional) — Named server from config
|
||||
|
||||
### `download_package`
|
||||
Download and install a package from the registry.
|
||||
- `registry` — Registry identifier
|
||||
- `name` — Package name
|
||||
- `version` — Version string
|
||||
- `server` (optional) — Named server from config
|
||||
@@ -1,53 +0,0 @@
|
||||
# HTTP / Docker Mode
|
||||
|
||||
`context serve` can run as an HTTP MCP server instead of stdio. Use this when you need to share a single context server across multiple agents, run it in a container, or expose it to remote clients.
|
||||
|
||||
## Start as HTTP server
|
||||
|
||||
```bash
|
||||
# Localhost only (default)
|
||||
context serve --http
|
||||
|
||||
# Specific port
|
||||
context serve --http 3000
|
||||
|
||||
# All interfaces (for Docker or remote access)
|
||||
context serve --http 8080 --host 0.0.0.0
|
||||
```
|
||||
|
||||
## Docker
|
||||
|
||||
```bash
|
||||
docker run -p 8080:8080 \
|
||||
-v ~/.context:/root/.context \
|
||||
neuledge/context \
|
||||
context serve --http 8080 --host 0.0.0.0
|
||||
```
|
||||
|
||||
The volume mount (`-v ~/.context:/root/.context`) reuses packages already downloaded on the host. Omit it if you want an isolated container with its own package store.
|
||||
|
||||
## Client configuration
|
||||
|
||||
Point remote agents at `http://<host>:8080` as an HTTP MCP server. For Claude Desktop, Cursor, or VS Code Copilot, use the same JSON structure as stdio mode but set `url` instead of `command`:
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"context": {
|
||||
"url": "http://localhost:8080"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Security note
|
||||
|
||||
HTTP mode has no built-in authentication. Do not expose `--host 0.0.0.0` on a public interface without a reverse proxy or firewall rule. On shared systems, bind to `127.0.0.1` (the default) and use an SSH tunnel if remote access is needed.
|
||||
|
||||
## Scope restriction
|
||||
|
||||
`--libs` works in HTTP mode the same as in stdio mode:
|
||||
|
||||
```bash
|
||||
context serve --http 8080 --host 0.0.0.0 --libs react next typescript
|
||||
```
|
||||
@@ -1,72 +0,0 @@
|
||||
# Install Notes
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Node.js LTS (≥18)
|
||||
- npm — pnpm/yarn also work
|
||||
|
||||
No other system dependencies are required. The package uses a WASM SQLite fallback (`sql.js-fts5`) if the native `better-sqlite3` module fails to build — but native mode is significantly faster.
|
||||
|
||||
**For native SQLite (recommended on Linux servers):**
|
||||
```bash
|
||||
apt-get install -y python3 make g++ # Debian/Ubuntu
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## File Locations
|
||||
|
||||
| Path | Purpose |
|
||||
|------|---------|
|
||||
| `~/.context/packages/` | Downloaded/built SQLite package files (`name@version.db`) |
|
||||
| `~/.context/config.json` | Server configuration (registries, auth credentials) |
|
||||
|
||||
Both directories are created automatically on first use.
|
||||
|
||||
---
|
||||
|
||||
## Self-Hosted Registry Server
|
||||
|
||||
Anyone can operate a compatible registry implementing the [Download Server API](https://github.com/neuledge/context/blob/main/SERVER_SPEC.md):
|
||||
|
||||
- `GET /search?registry=<r>&name=<n>[&version=<v>]` — search packages
|
||||
- `GET /packages/<registry>/<name>/<version>` — package metadata
|
||||
- `GET /packages/<registry>/<name>/<version>/download` — download `.db` file
|
||||
- `POST /packages/<registry>/<name>/<version>` — publish (requires Bearer token)
|
||||
|
||||
Register a custom server in `~/.context/config.json` and reference it with `--server <name>`.
|
||||
|
||||
---
|
||||
|
||||
## Upgrade / Uninstall
|
||||
|
||||
```bash
|
||||
# Upgrade — pass the target version to the install script
|
||||
bash scripts/setup-neuledge-context.sh <VERSION>
|
||||
|
||||
# Uninstall binary
|
||||
npm uninstall -g @neuledge/context
|
||||
|
||||
# Remove all downloaded packages and config (optional — confirm with user first)
|
||||
rm -rf ~/.context
|
||||
```
|
||||
|
||||
No migration needed on upgrade — `.db` package files are not affected by CLI version changes.
|
||||
|
||||
---
|
||||
|
||||
## Known Gotchas
|
||||
|
||||
1. **Native build failure** — If `better-sqlite3` fails to compile (missing Python/g++), Context falls back to WASM automatically. Queries still work but are slower. Install build tools to fix.
|
||||
|
||||
2. **Package naming** — `context remove next` removes all versions of `next`. Use `next@v16.2.0` to target a specific version.
|
||||
|
||||
3. **`context add` for git repos** — Requires `git` to be installed. Clones the full repo; use `--path` to limit to a docs subdirectory and `--tag` to pin a version.
|
||||
|
||||
4. **Registry package IDs** — Registry identifiers follow `<ecosystem>/<name>` format (e.g. `npm/react`, `pip/fastapi`, `cargo/tokio`). The `browse` command accepts bare names (`react`) and infers the registry.
|
||||
|
||||
5. **`--libs` restriction** — When `context serve --libs react next`, the `search_packages` and `download_package` MCP tools are hidden from the agent. Only `get_docs` is available, scoped to the listed libraries.
|
||||
|
||||
6. **No releases on GitHub** — The project publishes via npm directly. Check `npm view @neuledge/context version` for the current version.
|
||||
|
||||
7. **Auth cookies/headers** — Stored in `~/.context/config.json` as plain JSON. File permissions matter — always run `scripts/secure-context-config.sh` after `context auth add`.
|
||||
Reference in New Issue
Block a user