@theronap/cortex-mcp 0.9.78 → 0.9.79

package/lib/uninstall.mjs

@@ -3,7 +3,7 @@ import { homedir } from 'os'
 import { join } from 'path'
 import { execFileSync } from 'child_process'
 
-// Full uninstall — the reverse of setup.mjs. Removes EVERY touch-point Agnoclast writes onto a machine:
+// Full uninstall — the reverse of setup.mjs. Removes EVERY touch-point Cortex writes onto a machine:
 //   1. ~/.claude.json          → mcpServers.cortex
 //   2. ~/.claude/settings.json → Stop/SessionStart/PreCompact cortex hooks
 //   3. ~/.codex/config.toml    → [mcp_servers.cortex] + [mcp_servers.cortex.env]
@@ -34,7 +34,7 @@ export function runUninstall(argv = []) {
   const act = (msg) => plan.push(msg)
   const write = (path, data) => { if (!dry) { backup(path); writeFileSync(path, data) } }
 
-  process.stdout.write(dry ? '\nAgnoclast uninstall — DRY RUN (nothing will change):\n\n' : '\nAgnoclast uninstall — removing all wiring…\n\n')
+  process.stdout.write(dry ? '\nCortex uninstall — DRY RUN (nothing will change):\n\n' : '\nCortex uninstall — removing all wiring…\n\n')
 
   // 1. MCP server out of ~/.claude.json
   editJson(CLAUDE_JSON, (cfg) => {
@@ -144,7 +144,7 @@ export function runUninstall(argv = []) {
     }
   }
 
-  if (plan.length === 0) { process.stdout.write('  Nothing to remove — this machine has no Agnoclast wiring.\n\n'); return }
+  if (plan.length === 0) { process.stdout.write('  Nothing to remove — this machine has no Cortex wiring.\n\n'); return }
   process.stdout.write(plan.join('\n') + '\n\n')
   if (dry) {
     process.stdout.write('DRY RUN — nothing changed. Re-run without --dry-run to apply.\n')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theronap/cortex-mcp",
-  "version": "0.9.78",
+  "version": "0.9.79",
   "description": "Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.",
   "type": "module",
   "bin": {

package/skills/author-docs/SKILL.md

@@ -1,22 +1,22 @@
 ---
 name: cortex-author-docs
-description: Push new/changed documentation (specs, plans, design docs) from disk into Agnoclast as authored wiki pages. Run after writing a spec/plan/design doc, when the user asks to sync docs to Agnoclast, or as part of session close-out.
+description: Push new/changed documentation (specs, plans, design docs) from disk into Cortex as authored wiki pages. Run after writing a spec/plan/design doc, when the user asks to sync docs to Cortex, or as part of session close-out.
 ---
 
-> **Agnoclast-managed skill.** This file is installed and kept up to date by Agnoclast. Local edits are
+> **Cortex-managed skill.** This file is installed and kept up to date by Cortex. Local edits are
 > restored on the next session (a backup of your version is saved alongside). Don't rely on changes here.
 
 ## Why this exists
 
 Specs, plans, and design docs get written to disk (a repo's `docs/`, skill-generated design docs)
-and never reach Agnoclast — so the org brain misses its richest artifacts. A spec IS a page: this
+and never reach Cortex — so the org brain misses its richest artifacts. A spec IS a page: this
 skill turns pending docs into authored wiki pages. You (the live session) are the pipe — you read
 the doc and author a synthesis. Never dump raw markdown into a page.
 
 ## When to use
 
 - Right after you write or substantially update a spec/plan/design/runbook doc on disk.
-- When the user asks to push/sync docs to Agnoclast.
+- When the user asks to push/sync docs to Cortex.
 - During session close-out (`/cortex-log` runs this as a sweep step).
 
 ## Steps
@@ -67,7 +67,7 @@ the doc and author a synthesis. Never dump raw markdown into a page.
 ## Safety rules
 
 - Do NOT register or sweep the local brain repo (`~/Documents/brain`) while the Robin parity soak
-  is running — the experiment forbids re-syncing Robin into Agnoclast mid-window.
+  is running — the experiment forbids re-syncing Robin into Cortex mid-window.
 - Respect tiers: if a doc is clearly personal/sensitive, author it `confidential` or ask; default
   for work docs is the author path's normal default.
 - This skill writes wiki pages via the `author` tool only. It never sends external messages and

package/skills/context/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: cortex-context
-description: Automatically hydrate Agnoclast context at the start of a substantive session. Use when Agnoclast MCP is available and the user has made a real request, so the first answer is grounded in query-centered org context instead of the static baseline alone.
+description: Automatically hydrate Cortex context at the start of a substantive session. Use when Cortex MCP is available and the user has made a real request, so the first answer is grounded in query-centered org context instead of the static baseline alone.
 ---
 
-> **Agnoclast-managed skill.** This file is installed and kept up to date by Agnoclast. Local edits are
+> **Cortex-managed skill.** This file is installed and kept up to date by Cortex. Local edits are
 > restored on the next session (a backup of your version is saved alongside). Don't rely on changes here.
 
 ## When to use
@@ -14,12 +14,12 @@ chit-chat and requests where org context is obviously irrelevant.
 ## Steps
 
 1. Call `session_context` with the user's opening request, preserving the actual topic in their words.
-2. Use that returned block as the primary Agnoclast grounding for the first response.
+2. Use that returned block as the primary Cortex grounding for the first response.
 3. If `session_context` is unavailable or errors, fall back to `my_context`.
 4. If the conversation materially changes topics later, call `session_context` again for the new topic.
 
 ## Safety rules
 
-- Do not fabricate Agnoclast context if the tool fails.
+- Do not fabricate Cortex context if the tool fails.
 - Prefer the query-centered `session_context` over static `my_context` whenever the user's topic is clear.
 - Do not call `session_context` for every tiny follow-up; refresh only when the topic meaningfully shifts.

package/skills/log/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: cortex-log
-description: Close out a work session into Agnoclast — summarize what happened, confirm it reached the org, and surface anything teammates should know. Run at or near the end of any working session.
+description: Close out a work session into Cortex — summarize what happened, confirm it reached the org, and surface anything teammates should know. Run at or near the end of any working session.
 ---
 
-> **Agnoclast-managed skill.** This file is installed and kept up to date by Agnoclast. Local edits are
+> **Cortex-managed skill.** This file is installed and kept up to date by Cortex. Local edits are
 > restored on the next session (a backup of your version is saved alongside). Don't rely on changes here.
 
 ## Model: session-primary, daily-derived
 
-The **session is the primary atomic unit** — one session = one durable Agnoclast record (via
+The **session is the primary atomic unit** — one session = one durable Cortex record (via
 `log_session`, keyed by `sessionId`), which is also the per-record privacy unit (`set_record_privacy`
 is per record). Any "what happened today / this week" view is a **derived rollup** over those session
 records, never a separately-authored primary. This mirrors records(atomic) → digests(derived); the
@@ -16,7 +16,7 @@ personal `/log` skill follows the same shape against the local brain.
 
 ## When to use
 
-At the end of a Claude Code session, or after finishing a meaningful phase of work. Agnoclast keeps a
+At the end of a Claude Code session, or after finishing a meaningful phase of work. Cortex keeps a
 background auto-capture as a fallback, but this skill is the *authoritative* close-out: it composes a
 clean, structured summary and persists THAT as the session's durable record (superseding the
 auto-capture's raw-transcript re-derivation).
@@ -33,7 +33,7 @@ No arguments. Read the conversation context.
    These are the things a teammate or manager would want to know without reading the whole transcript.
 3. **Persist it as the durable record** — call the `log_session` MCP tool with your curated `summary`
    (plus `project`, and the Claude Code `sessionId` if you know it). This writes YOUR summary as the
-   session's authoritative Agnoclast record (`capture_source='skill'`). The background auto-capture is a
+   session's authoritative Cortex record (`capture_source='skill'`). The background auto-capture is a
    fallback and will not overwrite it; passing the same `sessionId` the auto-capture uses dedupes them
    onto one record. This — not the raw-transcript re-derivation — is the canonical record going forward.
 4. **Confirm + flag privacy** — `log_session` returns a confirmation; if it errors, tell the user to
@@ -72,7 +72,7 @@ No arguments. Read the conversation context.
    > verify a write; the result you already have in hand is the strongest.
    >
    > **What replaces it — at the moment of each write, not at the end:** a rejected `author` comes back
-   > as an ORDINARY tool result with **no error flag** — `Could not author "<page>": Agnoclast API 409:
+   > as an ORDINARY tool result with **no error flag** — `Could not author "<page>": Cortex API 409:
    > <reason>` — and `No change to "<page>"` is a **200 OK that wrote nothing**. Neither is an error at
    > the protocol level, so nothing will interrupt you. **Read the result text of every write; never
    > skim it.** That inline read is where this step's value actually was.

package/skills/walkthrough/SKILL.md

@@ -3,7 +3,7 @@ name: cortex-walkthrough
 description: Run the guided Agnoclast walkthrough for someone new. Use when the person asks for the walkthrough, a tutorial, or getting started — "give me the walkthrough", "walk me through this", "how do I use this", "show me around", "what can this do", "remind me how this works" — or when a brand-new user needs orienting for the first time.
 ---
 
-> **Agnoclast-managed skill.** This file is installed and kept up to date by Agnoclast. Local edits are
+> **Cortex-managed skill.** This file is installed and kept up to date by Cortex. Local edits are
 > restored on the next session (a backup of your version is saved alongside). Don't rely on changes here.
 
 # The Agnoclast walkthrough

package/lib/use_brain.mjs

@@ -1,82 +0,0 @@
-import { fetchCortex, classify, resolveBase } from './diagnose.mjs'
-import { resolveToken } from './doctor.mjs'
-
-// `use-brain` — set (or show) which brain this machine's unattended session captures land in.
-//
-// WHY A SUBCOMMAND EXISTS AT ALL. The server side of this shipped 2026-08-09 with NO client surface:
-// no CLI, no MCP tool, no console setting. The only way to set a capture default was a raw
-// authenticated HTTP call, which meant the only people who could fix a broken capture were the ones
-// who could hand-write a curl with a bearer token. Three real users needed it; one of them is not
-// technical. A fix only its author can operate is not a fix.
-//
-// Pairs with the SessionStart notice: the notice tells you captures are being held and names this
-// command, so the loop from "something is wrong" to "it is fixed" is one paste with no docs.
-
-function out(m) { process.stdout.write(m + '\n') }
-
-export async function runUseBrain(args) {
-  const base = resolveBase(process.env.CORTEX_URL)
-  const { token } = resolveToken()
-  if (!token) {
-    out('Agnoclast: no token found. Run: npx -y @theronap/cortex-mcp setup <token>')
-    return 1
-  }
-
-  // Everything after the subcommand is the brain, joined — so an unquoted multi-word name still
-  // works. `use-brain Real estate` is what a person actually types; refusing it over a missing pair
-  // of quotes would be the same species of unhelpfulness this command exists to remove.
-  const wanted = (args ?? []).filter((a) => !a.startsWith('--')).join(' ').trim()
-  const url = `${base}/api/brain/capture-default`
-
-  if (!wanted) {
-    // No argument: report the current state rather than erroring. "What is it set to?" is a fair
-    // question and the answer is one GET away.
-    try {
-      const res = await fetchCortex(url, { headers: { Authorization: `Bearer ${token}` } })
-      if (!res.ok) {
-        const body = await res.text()
-        out(`Agnoclast: could not read your capture settings — ${classify(res.status, res.headers.get('content-type'), body, res.headers.get('x-vercel-id')).message}`)
-        return 1
-      }
-      const { defaults } = await res.json()
-      if (!defaults?.length) {
-        out('Agnoclast: no capture brain set. Your unattended session captures land in a brain only if')
-        out('  you belong to exactly one; otherwise they are HELD outside every brain until you set this.')
-        out('  Set one:  npx -y @theronap/cortex-mcp use-brain "<brain name or org id>"')
-        return 0
-      }
-      for (const d of defaults) out(`Agnoclast: ${d.sourceType} captures land in "${d.orgName}" (${d.orgId})`)
-      return 0
-    } catch (e) {
-      out(`Agnoclast: could not reach the server (${e?.message ?? String(e)})`)
-      return 1
-    }
-  }
-
-  try {
-    const res = await fetchCortex(url, {
-      method: 'POST',
-      headers: { Authorization: `Bearer ${token}`, 'Content-Type': 'application/json' },
-      body: JSON.stringify({ sourceType: 'claude-code', brain: wanted }),
-    })
-    const body = await res.text()
-    if (!res.ok) {
-      let msg = classify(res.status, res.headers.get('content-type'), body, res.headers.get('x-vercel-id')).message
-      // The server's own error text is better than a generic one here: a 404 names the brain that was
-      // not found, and a 409 lists the org ids of an ambiguous name — which is the whole remedy.
-      try { const j = JSON.parse(body); if (j.error) msg = j.error } catch { /* keep the classified message */ }
-      out(`Agnoclast: ${msg}`)
-      return 1
-    }
-    const j = JSON.parse(body)
-    out(`Agnoclast: ✓ your Claude Code sessions now land in "${j.brain}".`)
-    // Say plainly what this does NOT do. The setter's own server-side note makes the same point,
-    // because "I fixed it" reading as "and the backlog is handled" is how held records stay held.
-    out('  Sessions captured BEFORE now are still held — they keep their original dates until sorted.')
-    out('  Ask your assistant to file them (they may not all belong in the same brain).')
-    return 0
-  } catch (e) {
-    out(`Agnoclast: could not reach the server (${e?.message ?? String(e)})`)
-    return 1
-  }
-}