Skip to content

Vigils v0.1.30

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Jun 11:47
· 30 commits to main since this release
v0.1.30
d791bee

--doctor now health-checks every agent, not just Claude.

Added

  • setup --mcp --doctor now covers all four agent surfaces. The read-only launch-health preflight —
    which answers "after wrapping, can each MCP server's underlying program still start in this
    environment?" — previously checked only Claude Code's servers. It now checks Claude (user +
    per-project), Codex, Cursor, and Windsurf in one pass, each row tagged by agent. --doctor --probe
    likewise runs a real MCP-handshake test for servers across all four. It sees through Vigil's wrapping —
    it checks the underlying program (e.g. npx / uvx / python), not vigil-hub itself. This directly
    answers the most common worry after setup --all: "did wrapping break any of my tools?"

Fixed / Security

  • A broken (malformed or unreadable) config for a non-Claude agent is now reported as a counted doctor
    failure with an accurate cause (parse failure vs permission/IO error), instead of being silently
    skipped — so --doctor can no longer claim "all servers resolve" while an entire agent surface went
    unchecked. All diagnostic output (including config paths) is scrubbed before printing.

中文

--doctor 现在体检每个 agent,不再只是 Claude。

新增

  • setup --mcp --doctor 现在覆盖全部四个 agent 接入面。 这个只读的启动健康预检 —— 回答"wrap 之后,
    每个 MCP server 的底层程序在本环境还能起来吗" —— 此前只查 Claude Code 的 server。现在一次过查 Claude
    (user + 各项目)、Codex、Cursor、Windsurf,每行按 agent 标注。--doctor --probe 同样对四个面的 server
    做真实 MCP 握手测试。它看穿 Vigil 的包裹 —— 检查的是底层程序(如 npx / uvx / python)而非
    vigil-hub 自身。这直接回应 setup --all 后最常见的担忧:"wrap 之后我的工具是不是被弄坏了?"

修复 / 安全

  • 非 Claude agent 的配置坏了(无法解析 或 读不了),现在会作为计入失败的 doctor 项报告,并给出准确成因
    (解析失败 vs 权限/IO 错误),而不再被静默跳过 —— 这样 --doctor 不会在某个 agent 面整个没被检查到的情况下
    仍宣称"所有 server 都可解析"。所有诊断输出(含配置路径)在打印前都经脱敏。

Downloads — which file do I want?

  • Desktop app (most users): the installer for your OS — Windows Vigils_*_x64-setup.exe (or .msi), macOS Vigils_*.dmg, Linux .AppImage / .deb / .rpm. Gives you the GUI: Activity Feed, Approval Queue, Server Registry.
  • CLI gateway (put Vigils in front of an AI agent — Claude Code / Codex / Cursor / Zed): vigils-cli-<platform> (contains vigil-hub + vigil-native-host). This is the MCP proxy your agent connects to.
  • Browser extension (guard pasting/typing secrets into AI web apps, Chrome MV3): vigils-chrome-extension.zip — unzip, then load unpacked at chrome://extensions.
  • The .sig and Vigils.app.tar.gz files are desktop auto-updater artifacts — you do not need to download them.

New here? Full setup & agent-integration guide: https://duncatzat.github.io/vigils

Early releases are unsigned; your OS may show a Gatekeeper / SmartScreen prompt on first run.

Apache-2.0 · https://vigils.ai · Full changelog

Assets 22
Loading