来子AI工窗语算求

Docker

docker build -t perseus .
docker run --rm -v /path/to/workspace:/workspace perseus mcp serve

See Container Runtime for full Docker and compose deployment.

Quick Start (MCP Server)

pip install perseus-ctx
perseus mcp serve                          # stdio (Claude Desktop, Claude Code, Cursor, Codex)
perseus mcp serve --transport sse --port 8420  # SSE (remote agents, multi-machine)

Quick Start (30 Seconds to Live Context)

perseus quickstart          # auto-detects project, scaffolds context, renders

Smart init detects your stack and tailors the setup: - Python → @memory queries for test patterns, type annotations - Rust → trait bounds, lifetime annotations, cargo config - Node.js/TS → npm scripts, ESLint config, component patterns - Go, Java, C/C++, Docker — all detected automatically - Falls back to a sensible generic query when unknown

The output file name is the only assistant-specific detail:

Hermes priority order: .hermes.md → AGENTS.md → CLAUDE.md. Render to .hermes.md for highest priority.

Keep it fresh with cron, launchd, systemd, or perseus watch:

```bash

~/.perseus/config.yaml

hooks: enabled: true on_render_complete: - cmd: "notify-send 'Context refreshed'" on_directive_error: - plugin: "my_error_handler" ```

~/.perseus/config.yaml

directives: aliases: "@q": "@query" "@svc": "@services" "@stale-skills": "@skills flag_stale=true category=all" ```

Pre-defined aliases: @q→@query, @r→@read, @svc→@services, @mb→@memory, @ag→@agora, @wp→@waypoint, @sess→@session. Config aliases override them.

Plugins

```python

~/.perseus/plugins/my_plugin.py

from perseus.registry import DirectiveSpec

def _resolve_service_status(args, cfg, workspace): import urllib.request try: resp = urllib.request.urlopen(args.strip(), timeout=5) return f"Status: {resp}" except Exception as e: return f"Error: {e}"

REGISTER = { "@service-status": DirectiveSpec( name="@service-status", resolver=_resolve_service_status, args=["url"], kind="inline", call_sig="acw", executes_shell=False, safe_for_hover=True, cacheable=True, summary="Check HTTP status of a URL", ) } ```

Use it in context files: @service-status https://api.example.com/health

Built-in directives always win collisions. Plugins respect the same permission profile as built-ins (executes_shell gates behind allow_query_shell).

Render Pipeline Hooks

Shell scripts or Python callbacks fire at render lifecycle points — on_render_start, on_directive_resolved, on_cache_hit, on_cache_miss, on_render_complete, on_directive_error:

```yaml