Reference

Complete CLI & MCP Reference

v1.1.0

Getting Started

gnosys init

Initialize a new .gnosys store in the current directory

Usage
gnosys init [options] Options: -d, --directory <dir> Target directory (default: cwd)
MCP Tool: gnosys_init

gnosys config

View and manage LLM provider configuration

Usage
gnosys config [command] Commands: show Show current LLM configuration set <key> <value> [extra...] Set a config value init Generate default gnosys.json Keys: provider, model, ollama-url, groq-model, openai-model, lmstudio-url, task <task> <provider> <model>

gnosys stores

Show all active stores, their layers, paths, and permissions

Usage
gnosys stores
MCP Tool: gnosys_stores

gnosys doctor

Check system health: stores, LLM connectivity, embeddings

Usage
gnosys doctor

gnosys serve

Start the MCP server (stdio mode)

Usage
gnosys serve [options] Options: --with-maintenance Run maintenance every 6 hours in background

gnosys dashboard

Show system dashboard: memory count, health, graph stats, LLM status

Usage
gnosys dashboard [options] Options: --json Output as JSON instead of pretty table
MCP Tool: gnosys_dashboard

Writing Memories

gnosys add

Add a new memory (uses LLM to structure raw input)

Usage
gnosys add [options] <input> Options: -a, --author <author> Author (human|ai|human+ai) (default: "human") --authority <authority> Authority (declared|observed|imported|inferred) (default: "declared") -s, --store <store> Target store (project|personal|global)
MCP Tool: gnosys_add

gnosys add-structured

Add a memory with structured input (no LLM needed)

Usage
gnosys add-structured [options] Options: --title <title> Memory title --category <category> Category directory name --content <content> Memory content as markdown --tags <json> Tags as JSON object (default: "{}") --relevance <keywords> Keyword cloud for discovery (default: "") -a, --author <author> Author (default: "human") --authority <authority> Authority level (default: "declared") --confidence <n> Confidence 0-1 (default: "0.8") -s, --store <store> Target store
MCP Tool: gnosys_add_structured

gnosys commit-context

Pre-compaction sweep: extract atomic memories from a context string, check novelty, commit novel ones

Usage
gnosys commit-context [options] <context> Options: --dry-run Show what would be committed without writing -s, --store <store> Target store (project|personal|global)
MCP Tool: gnosys_commit_context

gnosys bootstrap

Batch-import existing documents into the memory store

Usage
gnosys bootstrap [options] <sourceDir> Options: -p, --pattern <patterns...> File patterns to match (default: **/*.md) --skip-existing Skip files whose titles already exist -c, --category <category> Default category (default: "imported") -a, --author <author> Default author (default: "human") --authority <authority> Default authority (default: "imported") --confidence <n> Default confidence 0-1 (default: "0.7") --preserve-frontmatter Preserve existing YAML frontmatter if present --dry-run Show what would be imported without writing -s, --store <store> Target store (project|personal|global)
MCP Tool: gnosys_bootstrap

gnosys import

Bulk import structured data (CSV, JSON, JSONL) into Gnosys memories

Usage
gnosys import [options] <fileOrUrl> Options: --format <format> Data format: csv, json, jsonl --mapping <json> Field mapping as JSON --mode <mode> Processing mode: llm or structured (default: "structured") --limit <n> Max records to import --offset <n> Skip first N records --skip-existing Skip records whose titles already exist --batch-commit Single git commit for all imports (default: true) --no-batch-commit Commit each record individually --concurrency <n> Parallel LLM calls (default: 5) --dry-run Preview without writing --store <store> Target store (default: "project")
MCP Tool: gnosys_import

Reading & Search

gnosys read

Read a specific memory. Supports layer prefix (e.g., project:decisions/auth.md)

Usage
gnosys read <memoryPath>
MCP Tool: gnosys_read

gnosys discover

Discover relevant memories by keyword. Searches relevance clouds, titles, and tags — returns metadata only, no content.

Usage
gnosys discover [options] <query> Options: -n, --limit <number> Max results (default: "20")
MCP Tool: gnosys_discover

gnosys ask

Ask a natural-language question and get a synthesized answer with citations

Usage
gnosys ask [options] <question> Options: -l, --limit <n> Max memories to retrieve (default: "15") -m, --mode <mode> Search mode: keyword | semantic | hybrid (default: "hybrid") --no-stream Disable streaming output
MCP Tool: gnosys_ask

Organization

gnosys list

List all memories across all stores

Usage
gnosys list [options] Options: -c, --category <category> Filter by category -t, --tag <tag> Filter by tag -s, --store <store> Filter by store layer
MCP Tool: gnosys_list

gnosys lens

Filtered view of memories. Combine criteria to focus on what matters.

Usage
gnosys lens [options] Options: -c, --category <category> Filter by category -t, --tag <tags...> Filter by tag(s) --match <mode> Tag match mode: any or all (default: "any") --status <statuses...> Filter by status (active, archived, superseded) --author <authors...> Filter by author (human, ai, human+ai) --authority <authorities...> Filter by authority (declared, observed, imported, inferred) --min-confidence <n> Minimum confidence (0-1) --max-confidence <n> Maximum confidence (0-1) --created-after <date> Created after ISO date --created-before <date> Created before ISO date --modified-after <date> Modified after ISO date --modified-before <date> Modified before ISO date --or Combine filters with OR instead of AND
MCP Tool: gnosys_lens

gnosys tags

List all tags in the registry

Usage
gnosys tags
MCP Tool: gnosys_tags

gnosys tags-add

Add a new tag to the registry

Usage
gnosys tags-add [options] Options: --category <category> Tag category (domain, type, concern, status_tag) --tag <tag> The new tag to add
MCP Tool: gnosys_tags_add

gnosys graph

Show the full cross-reference graph across all memories

Usage
gnosys graph
MCP Tool: gnosys_graph

History & Maintenance

gnosys update

Update an existing memory's frontmatter and/or content

Usage
gnosys update [options] <memoryPath> Options: --title <title> New title --status <status> New status (active|archived|superseded) --confidence <n> New confidence (0-1) --relevance <keywords> Updated relevance keyword cloud --supersedes <id> ID of memory this supersedes --superseded-by <id> ID of memory that supersedes this one --content <content> New markdown content (replaces body)
MCP Tool: gnosys_update

gnosys reinforce

Signal whether a memory was useful, not relevant, or outdated

Usage
gnosys reinforce [options] <memoryId> Options: --signal <signal> Reinforcement signal (useful|not_relevant|outdated) --context <context> Why this signal was given
MCP Tool: gnosys_reinforce

gnosys stale

Find memories not modified within a given number of days

Usage
gnosys stale [options] Options: -d, --days <number> Days threshold (default: "90") -n, --limit <number> Max results (default: "20")
MCP Tool: gnosys_stale

gnosys history

Show version history for a memory (git-backed)

Usage
gnosys history [options] <memoryPath> Options: -n, --limit <number> Max entries (default: "20") --diff <hash> Show diff from this commit to current
MCP Tool: gnosys_history

gnosys rollback

Rollback a memory to its state at a specific commit

Usage
gnosys rollback <memoryPath> <commitHash>
MCP Tool: gnosys_rollback

gnosys timeline

Show when memories were created and modified over time

Usage
gnosys timeline [options] Options: -p, --period <period> Group by: day, week, month, year (default: "month")
MCP Tool: gnosys_timeline

gnosys stats

Show summary statistics for the memory store

Usage
gnosys stats
MCP Tool: gnosys_stats

gnosys maintain

Run vault maintenance: detect duplicates, apply confidence decay, consolidate similar memories

Usage
gnosys maintain [options] Options: --dry-run Show what would change without modifying --auto-apply Automatically apply all changes (no prompts)
MCP Tool: gnosys_maintain

gnosys reindex

Rebuild all semantic embeddings from every memory file. Downloads the model (~80 MB) on first run.

Usage
gnosys reindex
MCP Tool: gnosys_reindex

gnosys reindex-graph

Build or rebuild the wikilink graph (.gnosys/graph.json)

Usage
gnosys reindex-graph
MCP Tool: gnosys_reindex_graph

Agent Rules

Agent rules allow you to configure custom behavior and preferences for your AI agent. Rules are context directives that shape how the agent operates within your IDE or application. They're particularly useful for enforcing coding standards, specifying project conventions, and providing the agent with important context about your workflow.

Rules are stored as markdown files in your IDE configuration and are automatically included in the agent's context. Here's how to set them up for your preferred IDE:

Save to .cursor/rules/gnosys.mdc — Uses Cursor's .mdc format with YAML frontmatter for alwaysApply: true.


          

Save to CLAUDE.md at your project root — Concise imperative format with grouped tool table.