Argus Decision Mcp

io.github.commet由 GitHub 账号 commet 发布v2.1.0更新于 Oct 29, 2026

Preserve a user-authorized judgment and append later answers. No model verdict or human score.

发布方自己的服务:Argus: Belgian tender insights

已验证STDIO仅桌面效率与工作流知识与记忆

概览

AI 生成的概览

本地优先的决策账本,让助手记录你的决定、可证伪的预测与确认日期,并在现实能回答时把它们带回来。

可以做什么
  • 记录决定及其由用户陈述的背景,最多保留一条关键前提
  • 保存一条可证伪的预测及其确认日期,并如实标注撰写者
  • 列出已到期或当前需要关注的未结记录
  • 追加你明确陈述的实际结果,不做评分或评判
  • 读取进行中的决定、判断回执、时间线与反复出现的模式
  • 读取或更新语言、提醒与显式同步设置
适用场景
适合在多次对话中做出重要且可验证的判断,并希望把原始措辞、确认日期和实际结果保存在一起的场景。它对琐碎、可逆或已结束的事项保持沉默,也不会替你下结论。
运行要求
需要 Node.js 18 或更高版本(已测试 Node 20 LTS),通过 npx 以 stdio 在本地运行。无需账号或 API 密钥。可选环境变量:ARGUS_DIR 指定账本目录,ARGUS_TZ 指定判断确认日期何时成为今天的时区,ARGUS_TOKEN 仅在需要账号同步时使用。
安装前请注意
记录是以 .argus 目录下的纯文本追加文件形式保存在磁盘上,直到你删除为止。同步默认关闭;通过 ARGUS_TOKEN 或 connect 命令开启后,记录会发送到 Argus 网页服务,请谨慎授权。命令行还提供 archive-export、archive-restore 与 local-purge,删除记录前需要显式确认参数。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Argus Decision Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Argus Decision MCP

English | 한국어

Argus carries a consequential decision across conversations: the user-adopted prediction, what reality should show, when to return, and what actually happened. The result becomes context for the next judgment. Argus never scores the person or invents a verdict.

Part of Argus · web app at argus.voyage · MIT licensed.

What using it looks like

You talk normally. Argus offers to keep one testable thing, then brings it back when reality can answer.

text
2026-08-19you    We're going with Postgres over DynamoDB — the join patterns kill us otherwise.
       ┌ Save this as a prediction?          (your host renders the form)       │ "Postgres handles our join patterns without a read-replica through Q4"       │ check by 2026-10-01       └ accept as written · edit the wording or the date · decline
… six weeks later, in a different conversation …
2026-10-01argus  One check is due — you saved this on 2026-08-19:       "Postgres handles our join patterns without a read-replica through Q4"       What actually happened?
you    We added a read replica in September. Analytics queries, not joins.
       Recorded. The original sentence stays exactly as you wrote it, your       answer is appended next to it, and nothing is scored.

Nothing is saved without you accepting it, and Argus never fills in the outcome for you.

Install

Requirements: Node.js 18 or newer — Node 20 LTS is the tested version (node --version; get it from nodejs.org). No API key and no account: records are local files from the first call.

Pick your host. Every path below installs the same server.

Claude Code

The plugin wires this server for you and adds the decision commands on top:

text
/plugin marketplace add commet/Argus/plugin install argus@argus

Restart Claude Code, then /argus:settings doctor confirms the wiring.

Want the server alone, without the commands? Add it directly:

bash
claude mcp add argus -- npx -y argus-decision-mcp          # this project onlyclaude mcp add -s user argus -- npx -y argus-decision-mcp  # every project

claude mcp add defaults to the current project — use -s user if you want Argus everywhere.

Claude Desktop

Settings → Developer → Edit Config opens the file directly. It lives at:

  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows — %APPDATA%\Claude\claude_desktop_config.json

Add Argus to it, then quit Claude Desktop completely and reopen it (a window close is not enough):

json
{  "mcpServers": {    "argus-decision": {      "command": "npx",      "args": ["-y", "argus-decision-mcp"],      "env": {        "ARGUS_DIR": "/absolute/path/to/where/records/should/live/.argus"      }    }  }}

ARGUS_DIR is optional here too — a desktop app has no "current project", so records go to your personal home ledger (~/.argus) by default rather than scattering. Set it when you want them somewhere specific. On Windows, escape the backslashes ("C:\\Users\\you\\decisions\\.argus").

Windows: server does not appear
  • Run the command by hand first. npx -y argus-decision-mcp in a normal terminal prints a short help card and exits — that means the binary works (assistants launch it over a pipe, where it stays running as a server). A crash or error text instead of the card is the real problem.
  • npx failing while it works in your terminal usually means npm is not installed globally. Check that %APPDATA%\npm exists; if not, run npm install -g npm.
  • If the log mentions an unexpanded ${APPDATA}, add "APPDATA": "C:\\Users\\you\\AppData\\Roaming\\" to the env block above.
  • Logs: %APPDATA%\Claude\logs\mcp*.log (macOS: ~/Library/Logs/Claude).

Codex (CLI or app)

bash
codex mcp add argus-decision -- npx -y argus-decision-mcpcodex mcp list        # argus-decision should be listed and enabled

Restart Codex afterwards. A conversation opened before mcp add does not gain newly registered tools — quit and reopen the app, or start a new CLI session.

Codex: the confirmation form does not appear

Argus confirms a prediction with a one-tap form before saving it. Codex renders that form under its default approval policy. If yours is never, or approval_policy.granular.mcp_elicitations = false, Codex returns a protocol decline without ever showing the form. MCP supplies no marker that separates that policy response from a fast intentional decline, so Argus has to respect it as a decline. Enable MCP elicitations and retry if you want the form.

An AI-drafted premise has a chat fallback: when the confirm window cannot reach you, the draft comes back in the response, and once you approve it in conversation the assistant records it by calling again with chat_confirmed: true. Provenance stays ai_surfaced either way.

Any other MCP host

json
{  "mcpServers": {    "argus-decision": {      "command": "npx",      "args": ["-y", "argus-decision-mcp"],      "env": {        "ARGUS_DIR": "/absolute/path/to/your/project/.argus"      }    }  }}

Install once; there is nothing to update by hand. Leave the version off, as above — npx re-resolves a bare package name on every launch, so each session starts the current build.

Why no version range — and why that matters

Do not write a range like @^2. A range is satisfied by whatever already sits in the npx cache, so it never consults the registry again and the wire can stay frozen on an old build for weeks while everything looks healthy. Measured 2026-07-29, same spec string both times, cache holding an older version the range still allowed:

speclaunched
argus-decision-mcpthe current release
argus-decision-mcp@^2.0.0the stale cached build

An exact pin is correct but freezes there until someone edits it. argus_check_in reports the version actually running (data.server_version) if you ever need to confirm which build answered.

Where your records live

On your disk from the first call — nothing to set up.

ARGUS_DIR is optional. The default follows one rule — project evidence decides where the ledger lives:

  • the working directory is inside a git repo, or already has an .argus folder → <that-project>/.argus (per-project isolation, unchanged)
  • otherwise (a temp folder, or an app that creates a fresh folder per conversation — the Codex desktop app does this) → the personal home ledger (~/.argus), so records accumulate across conversations instead of fragmenting into per-conversation orphans

A per-call absolute argus_dir overrides everything; ARGUS_DIR overrides the rule.

Argus never scans other projects. Existing home-level ledgers are not migrated or merged silently; point ARGUS_DIR at one explicitly if you need to inspect it.

Optional: account sync

Off until you turn it on. Nothing leaves the machine before you approve it in a browser:

bash
npx argus-decision-mcp connect       # one browser approval, credential stored locallynpx argus-decision-mcp disconnect    # revoke it here

Add --headless on a machine with no browser to get a device-code flow. For CI, set ARGUS_TOKEN to a sync token from the web app's settings page instead of running connect. With no credential, sync is a silent no-op — the local record is unaffected.

Your data

The records are plain append-only files under .argus/. They are yours: copy that folder to back it up, delete it to remove it. Uninstalling the server never touches it.

For the durable home that survives moves and worktrees, the CLI also has archive-export, archive-restore, and local-purge. Each one requires explicit arguments — --repository-id, an absolute --archive-dir, and a verbatim --confirm-repository before anything is deleted. That is deliberate: erasing judgment records should never be a one-word command. Run one without arguments and it names the argument it wants.

Tools

The complete callable surface is six tools:

ToolPurpose
argus_captureCapture a decision and its user-owned context.
argus_predictRecord one falsifiable claim and its check date.
argus_check_inRead records that need attention now.
argus_resolveAppend an outcome the user explicitly stated.
argus_patternsRead decisions, receipts, timelines, and patterns.
argus_settingsRead or update language, reminders, and explicit sync.

Names from pre-2.0 releases are not callable aliases. A cached call to one of them returns UNKNOWN_TOOL, so hosts cannot accidentally keep using obsolete contracts.

Design boundaries

  • Local-first, append-only records.
  • Project isolation by default.
  • User wording and AI-surfaced wording retain distinct provenance.
  • Recorded text is treated as untrusted data.
  • No verdict, grade, accuracy score, streak, or leaderboard.
  • Network sync is explicit; anonymous telemetry is off unless ARGUS_TELEMETRY=1.
  • Unexpected errors are logged server-side and returned as a generic message, avoiding path or stack disclosure to the model.

Development

bash
npm installnpm run typechecknpm testnpm run buildnpm pack --dry-run

The published package contains one bundled runtime entrypoint. Internal implementation and experimental modules are not shipped as separate callable or importable files.

See SECURITY.md for reporting and trust-boundary details.

来源:argus-mcp/README.md,提交 2ef3771

工具

6

argus_capture

결정 다루기 · Work with a decision

결정을 대신 내리지 않고, 그 결정이 어떤 전제 위에 서 있는지와 아직 열린 질문을 사용자의 말 그대로 포착합니다. 기록된 결정의 전제·현재 사실·예측 문장·상태도 관리합니다. Capture a decision and its user-stated context without deciding for the user. Preserve at most one load-bearing assumption; tag an AI-drafted premise as ai_surfaced. A decision the user has closed or told you not to revisit is never capture material — acknowledge it and move on; recording it re-opens it.

输入参数idrefnotesteptextstepsaction必填sourcestakesvalueschangedfinding另有 25 个

argus_predict

예측 저장 · Seal a prediction

현실이 확인할 수 있는 예측과 확인일을 저장하고 작성 주체를 정직하게 기록합니다. Record one falsifiable prediction and when reality can answer it. Use the user’s words and offer confirmation once.

输入参数id必填basischeck_by必填questionargus_dirpredicate必填confidencehuman_onlyconfirm_draftreal_questionhuman_judgmentpredicate_owner必填另有 2 个

argus_check_in

확인할 기록 보기 · Check what is due

확인일이 됐거나 다시 살펴볼 결정·전제·미결 질문을 보여줍니다. Show only open records that need attention now. Reads open records; the first call may initialize the ledger folder.

输入参数argus_dirinclude_upcoming_days

argus_resolve

실제 결과 기록 · Settle against reality

확인일이 된 예측에 실제로 일어난 일을 기록합니다. Argus는 결과를 평가하지 않습니다. Record an outcome the user explicitly stated for a tracked prediction. Reality answers; Argus never grades.

输入参数id必填outcomedefer_toargus_dirwhat_happenedoutcome_sourcebroken_premise_ref

argus_patterns

판단 기록 보기 · View judgment history

진행 중인 결정, 전체 기록, 판단 영수증, 전제, 누적 기록을 읽고, 당신이 쓴 예측·전제와 그 결과를 되읽는 회고를 봅니다. Read active decisions, receipts, timelines, and recurring patterns. Read-only; history is context, never a verdict.

输入参数idviewargus_dir

argus_settings

Argus 설정 · Argus settings

언어와 알림, 전제 동기화 설정을 관리하고 필요할 때 계정 기록을 동기화합니다. Read or update language, reminders, and explicit sync settings. Argus initializes the current project on first use.

输入参数action必填localedue_onlyargus_dirpush_localambient_mutepremise_syncimport_settlements

版本历史

2
  1. v2.1.0最新Oct 21, 2026
  2. v2.0.23Sep 16, 2026

评分

已满足适用检查项的 80%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。

其他 Argus 集成