### Install Continuum from Source (Windows) Source: https://github.com/redstone-md/continuum/blob/main/README.md Build Continuum from source on Windows using the provided PowerShell installation script. This installs the adapter and daemon into ~/.cargo/bin. ```powershell powershell scripts/install.ps1 ``` -------------------------------- ### Install Continuum from Git Repository Source: https://github.com/redstone-md/continuum/blob/main/docs/releasing.md Install the continuum-adapter directly from the Git repository using cargo install, bypassing any registry. ```shell cargo install --git https://github.com/Rxflex/Continuum continuum-adapter ``` -------------------------------- ### Install Continuum from Source (Linux/macOS) Source: https://github.com/redstone-md/continuum/blob/main/README.md Build Continuum from source on Linux or macOS using the provided installation script. This installs the adapter and daemon into ~/.cargo/bin. ```shell sh scripts/install.sh ``` -------------------------------- ### Install and Run Continuum MCP Server Source: https://github.com/redstone-md/continuum/blob/main/npm/README.md Use this command to install and run the Continuum MCP server using npx. This command downloads prebuilt binaries for your platform and launches the MCP adapter. ```json { "command": "npx", "args": ["-y", "continuum-mcp"] } ``` -------------------------------- ### Install Continuum from Release Asset Source: https://github.com/redstone-md/continuum/blob/main/docs/releasing.md Install the Continuum npm wrapper directly from a release asset URL without needing an npm registry account. ```shell npx https://github.com/Rxflex/Continuum/releases/download/vX.Y.Z/continuum-mcp-X.Y.Z.tgz ``` -------------------------------- ### Install Continuum Binaries with Cargo Source: https://github.com/redstone-md/continuum/blob/main/README.md Install the Continuum adapter and daemon directly using Cargo. This method is suitable if you have a Rust toolchain installed and prefer managing dependencies via Cargo. ```shell cargo install --path crates/continuum-adapter ``` ```shell cargo install --path crates/continuum-daemon ``` -------------------------------- ### Configure Continuum Adapter via OpenCode JSON Source: https://github.com/redstone-md/continuum/blob/main/docs/agent-setup.md Configure the continuum adapter for OpenCode in `opencode.json` or `~/.config/opencode/opencode.json`. This setup enables the local adapter. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "continuum": { "type": "local", "command": ["/abs/path/continuum-adapter"], "enabled": true } } } ``` -------------------------------- ### Build, Test, and Lint Project Source: https://github.com/redstone-md/continuum/blob/main/CONTRIBUTING.md Run these commands to build, test, and lint the entire workspace. CI performs the same checks, so ensure these pass locally before submitting changes. ```sh cargo build --workspace cargo test --workspace cargo fmt --all cargo clippy --workspace --all-targets -- -D warnings ``` -------------------------------- ### Configure Windows Build for LLVM-MinGW Source: https://github.com/redstone-md/continuum/blob/main/README.md Set up a Rust configuration to build Continuum for Windows using the LLVM-MinGW toolchain when the MSVC linker is unavailable. This involves adding a target and a Cargo configuration file. ```toml # .cargo/config.toml [build] target = "x86_64-pc-windows-gnu" [target.x86_64-pc-windows-gnu] linker = "x86_64-w64-mingw32-gcc" rustflags = ["-C", "target-feature=+crt-static"] ``` -------------------------------- ### Publish npm Wrapper Source: https://github.com/redstone-md/continuum/blob/main/docs/releasing.md Navigate to the npm directory and publish the npm package. Use '--access public' for the first publish. ```shell cd npm npm publish # add --access public on the first publish ``` -------------------------------- ### Connect Agent to Continuum Binary Source: https://github.com/redstone-md/continuum/blob/main/README.md Configure an AI agent to connect to a locally built Continuum adapter. Specify the absolute path to the adapter executable. The adapter will automatically spawn the daemon. ```json { "command": "/absolute/path/to/continuum-adapter", "args": [] } ``` -------------------------------- ### Project Directory Structure Source: https://github.com/redstone-md/continuum/blob/main/README.md This outlines the main directories within the project and their respective responsibilities, covering core domain types, transport layers, graph representation, indexing, memory, search, the daemon, and adapter. ```plaintext crates/ continuum-core shared domain types, DTOs, protocol continuum-transport JSON-RPC + MCP wire types, IPC framing, stdio proxy continuum-graph in-memory code knowledge graph continuum-indexer tree-sitter parsing + filesystem watcher continuum-memory SQLite-backed agent memory continuum-search semantic search — embeddings + in-memory vector index continuum-daemon the workspace daemon (binary) continuum-adapter the thin MCP adapter (binary) ``` -------------------------------- ### Configure Continuum Adapter via Codex TOML Source: https://github.com/redstone-md/continuum/blob/main/docs/agent-setup.md Configure the continuum adapter in `~/.codex/config.toml` using TOML format. The adapter will be registered under the 'continuum' key. ```toml [mcp_servers.continuum] command = "/abs/path/continuum-adapter" args = [] ``` -------------------------------- ### Handoff & Memory (Continuity) Tools Source: https://github.com/redstone-md/continuum/blob/main/DESIGN.md Tools for managing project memory and continuity, including storing design decisions, reading project guidelines, logging agent intents, retrieving recent changes, and managing scratchpad entries. ```APIDOC ## Handoff & Memory (Continuity) ### `store_architectural_decision` **Description:** Saves a design decision to the project's lore. **Signature:** `(topic: string, description: string)` **Effect:** Stores architectural decision. ``` ```APIDOC ### `read_project_guidelines` **Description:** Retrieves all active architectural rules and project lore. **Signature:** `()` **Returns:** All project guidelines. ``` ```APIDOC ### `commit_intent` **Description:** Logs an agent's actions, intent, and the files affected. **Signature:** `(agent_id: string, intent: string, files_touched: string[])` **Effect:** Logs agent activity. ``` ```APIDOC ### `get_recent_changes` **Description:** Fetches the most recent intents logged by previous agents. **Signature:** `(limit: int)` **Returns:** Recent change logs. ``` ```APIDOC ### `write_scratchpad` **Description:** Appends a new entry to the scratchpad log. **Signature:** `(agent_id: string, message: string)` **Effect:** Appends to scratchpad log. ``` ```APIDOC ### `read_scratchpad` **Description:** Retrieves the last N entries from the scratchpad log. **Signature:** `(limit: int)` **Returns:** Scratchpad entries. ``` -------------------------------- ### Add Continuum Adapter via Claude CLI Source: https://github.com/redstone-md/continuum/blob/main/docs/agent-setup.md Add the continuum adapter using the Claude CLI command. Ensure the adapter path is correctly specified. ```bash claude mcp add continuum -- /abs/path/continuum-adapter ``` -------------------------------- ### Add Continuum Adapter via Codex CLI Source: https://github.com/redstone-md/continuum/blob/main/docs/agent-setup.md Register the continuum adapter using the Codex CLI, specifying the transport as stdio and providing the command path. ```bash codex mcp add continuum --transport stdio --command "/abs/path/continuum-adapter" ``` -------------------------------- ### MCP Tools Overview Source: https://github.com/redstone-md/continuum/blob/main/README.md This table lists the available MCP tools and their primary purposes, ranging from code search and analysis to project management and agent interaction. ```markdown `search_code` | Ranked symbol search — hybrid lexical + semantic ``` ```markdown `find_text` | Literal or regex text search across every file — line-precise grep ``` ```markdown `get_file_outline` | File structure — definitions with bodies folded ``` ```markdown `get_symbol_definition` | Full source + docstring of a symbol ``` ```markdown `find_callers` | Every call site of a symbol ``` ```markdown `get_local_graph` | Recursive tree of what a symbol calls ``` ```markdown `store_architectural_decision` | Persist a design decision / ADR ``` ```markdown `read_project_guidelines` | Read all stored decisions and lore ``` ```markdown `commit_intent` | Log what an agent did and expects next ``` ```markdown `get_recent_changes` | Recent agent intents ``` ```markdown `write_scratchpad` | Append to the shared scratchpad ``` ```markdown `read_scratchpad` | Read recent scratchpad entries ``` ```markdown `get_stats` | Index health — graph size, semantic-search state, uptime ``` -------------------------------- ### Configure Continuum Adapter via Claude MCP JSON Source: https://github.com/redstone-md/continuum/blob/main/docs/agent-setup.md Use this JSON configuration in your project's `.mcp.json` file to register the continuum adapter. ```json { "mcpServers": { "continuum": { "command": "/abs/path/continuum-adapter", "args": [] } } } ``` -------------------------------- ### Continuum Crate Dependency Direction Source: https://github.com/redstone-md/continuum/blob/main/DESIGN.md Illustrates the dependency flow between Continuum's Rust crates. This structure ensures no circular dependencies and clarifies which crates rely on others, promoting modularity and maintainability. ```text continuum-core ← everyone continuum-transport ← core continuum-graph ← core continuum-indexer ← core, graph continuum-memory ← core continuum-daemon ← core, transport, graph, indexer, memory continuum-adapter ← core, transport (stays thin — no graph/memory/indexer) ``` -------------------------------- ### Build Continuum Release Binaries Source: https://github.com/redstone-md/continuum/blob/main/README.md Compile Continuum in release mode to obtain optimized binaries. The resulting executables will be located in the target/release/ directory. ```shell cargo build --release ``` -------------------------------- ### Rust Crate Layout for Continuum Source: https://github.com/redstone-md/continuum/blob/main/DESIGN.md This outlines the directory structure and organization of the Continuum project within a Cargo workspace. It details the purpose of each crate and their interdependencies, emphasizing encapsulation and a clear dependency direction. ```text continuum/ ├── Cargo.toml # [workspace] └── crates/ ├── continuum-core/ # domain models, DTOs, error types, protocol consts ├── continuum-transport/ # MCP JSON-RPC, TCP IPC server, stdio proxy, Transport trait ├── continuum-graph/ # CodeGraph + heuristic resolver ├── continuum-indexer/ # FS watcher + tree-sitter parsing + .scm queries ├── continuum-memory/ # SQLite writer-actor ├── continuum-daemon/ # [[bin]] daemon — wires everything └── continuum-adapter/ # [[bin]] thin client — transport + core only ``` -------------------------------- ### Code Navigation & Search Tools Source: https://github.com/redstone-md/continuum/blob/main/DESIGN.md Tools for navigating and searching through the codebase, including symbol search, text search, file outlines, symbol definitions, caller identification, and local dependency graphs. ```APIDOC ## Code Navigation & Search ### `search_code` **Description:** Performs a hybrid lexical and semantic symbol search. **Signature:** `(query: string, limit?: int, kind?: string)` **Returns:** One compact row per hit. ``` ```APIDOC ### `find_text` **Description:** Line-precise literal or regex search over every file. **Signature:** `(pattern: string, regex?: bool, ignore_case?: bool, limit?: int)` **Returns:** Search results. ``` ```APIDOC ### `get_file_outline` **Description:** Retrieves the structure of a file, including classes and function signatures, with bodies omitted. **Signature:** `(path: string)` **Returns:** File structure. ``` ```APIDOC ### `get_symbol_definition` **Description:** Fetches the full source code and docstring for a given symbol. **Signature:** `(symbol_name: string, file_hint?: string)` **Returns:** Symbol definition. ``` ```APIDOC ### `find_callers` **Description:** Identifies the files and line numbers where a specific symbol is invoked. **Signature:** `(symbol_name: string)` **Returns:** List of call locations. ``` ```APIDOC ### `get_local_graph` **Description:** Generates a dependency tree showing what a symbol calls internally. **Signature:** `(symbol_name: string, depth: int)` **Returns:** Dependency tree. ``` -------------------------------- ### Diagnostics Tools Source: https://github.com/redstone-md/continuum/blob/main/DESIGN.md Tools for monitoring the health and status of the indexer and graph. ```APIDOC ## Diagnostics ### `get_stats` **Description:** Provides index health statistics, including graph size, semantic search state, and server uptime. **Signature:** `()` **Returns:** System statistics. ``` -------------------------------- ### Tag and Push Git Release Source: https://github.com/redstone-md/continuum/blob/main/docs/releasing.md Tag the current commit with a version number and push the tag to the remote repository. ```shell git tag vX.Y.Z git push origin vX.Y.Z ``` -------------------------------- ### Daemon Lockfile Structure Source: https://github.com/redstone-md/continuum/blob/main/DESIGN.md The daemon.lock file stores essential information for the adapter to connect to the running daemon, including PID, endpoint, and security token. It's crucial for managing the daemon's lifecycle and ensuring secure communication. ```json { "pid": 12345, "endpoint": "127.0.0.1:49213", "token": "a1b2c3...", "protocol_version": 1 } ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.