老師Roushi

Features

Twelve pillars.

The honest version of each capability. No marketing inflation.

  1. 01

    Ask, with citations

    Type a question on the homepage (or use `pnpm roushi think` / `mcp__roushi__think`). Hybrid search retrieves the top entities; an LLM grounds an answer on them and emits citation links to each entity. A gap analysis tells you what the brain doesn't know yet — directly useful as a backlog of things to ingest.

  2. 02

    Hybrid search (vector + keyword + RRF)

    Every search runs two queries in parallel: pgvector cosine over embeddings (HNSW-indexed) and Postgres tsvector keyword (GIN-indexed). Reciprocal Rank Fusion (k=60) merges the rankings. Optional LLM rerank pass via gpt-4o-mini adds ~1-2s for noticeably better top-3 quality on long queries.

  3. 03

    Typed knowledge graph

    Twelve entity types (product, tech, vendor, decision, pattern, incident, lesson, goal, person, roadmap_item, rule, skill) connected by ten typed relations (uses, depends_on, hosted_on, defined_by, led_to, applies_to, mentions, blocks, shares_pattern, supersedes). Multi-hop traversal via a recursive CTE with cycle protection.

  4. 04

    Visual graph at /graph

    Force-directed cytoscape view of every entity and edge. Color per type, search highlights matches, legend chips hide types or relations. Click-to-click selects two nodes and Dijkstra highlights the shortest path between them. Useful for spotting unintentional silos in the portfolio knowledge.

  5. 05

    PreToolUse Roushi-as-advisor hook

    Fires before every Edit/Write across every KumoKodo workspace. Detects which product the file belongs to, classifies it by path pattern (API route, Server Action, schema, etc.), and surfaces 2-4 relevant lessons/decisions/patterns/rules from the brain. Cached on disk with a 30-second TTL — repeated edits to the same file return in ~50ms.

  6. 06

    Security checklist hook

    Companion PreToolUse hook that injects a file-pattern-aware security checklist (auth-before-mutation, Zod-validate-body, no body logging, etc.). The code lands secure on the first try rather than catching the same bugs in review.

  7. 07

    Auto-synced portfolio rules

    Rules are first-class brain entities. The SessionStart hook syncs every applicable rule into the workspace's Claude memory dir. Scope: applies_to_slug (product-specific), applies_to_type (every product), or applies_to: portfolio (everywhere). Sam edits a rule once; it propagates everywhere on next session start.

  8. 08

    Self-maintenance crons

    Four scans run on schedule: decay (daily 3am UTC), audit-edges (Sundays 4am UTC), dedupe (1st of month 5am UTC), contradictions (Sundays 6am UTC). Each posts findings as a [system] goal when above threshold and auto-closes the goal when findings clear. Every run logs to maintenance_runs for full visibility.

  9. 09

    CLI + MCP (stdio and HTTPS)

    Thirty-five tools across the brain. Local stdio for low-latency access in any Claude Code session. Deployed HTTPS endpoint at /api/mcp with Bearer-token auth and per-token rate limiting — register from any remote agent with `claude mcp add roushi-remote --url https://roushi.ai/api/mcp`.

  10. 10

    Skill index + team sync

    Roushi indexes every skill in ~/.claude/skills/ as a brain entity. The `think` flow can recommend a skill in an answer; the PreToolUse advisor surfaces relevant skills on the file you're about to edit. `pnpm roushi skill pull/push/sync` mirrors skills into the repo so a team can git-track and share them.

  11. 11

    Goal lifecycle UI

    Multi-week objectives across machines. Add via the web form, CLI, or MCP. Status buttons for done/block/abandon/reopen. System goals auto-created by the maintenance crons; cron-managed goals lock manual edits to prevent fighting the loop. Recent activity panel shows every cron invocation regardless of outcome.

  12. 12

    Markdown-first, DB-indexed

    Content in git is canonical. Neon Postgres + pgvector is the searchable index. Roushi survives DB loss without losing knowledge — markdown files in `content/` are the source of truth. Pure portability: a directory of plain text remains readable when every tool changes.


Ready to put a brain behind your IDE? Roushi is in private beta.