Bug fixes from real-machine testing of the Claude Code / Codex integration.
- Desktop Activity Feed now reflects CLI-written events (DEF-001). Root cause was a
ledger-path mismatch: the integration guide pointed atledger.sqlitewhile the desktop
readsledger.sqlite3, so the CLI and the desktop used two different files and the feed
stayed empty (the live watcher itself was fine). Fixed the bilingual integration guide;
serve/wrapnow print the resolved ledger absolute path at startup and warn loudly when
an in-memory ledger is used (which the desktop cannot see). setup --mcpno longer nests-wraps Vigil's own server (DEF-002). The documented
vigil-hub serveself-entry was mis-classified as wrappable, producing a wrap-around-serve
nested gateway.setupnow skips Vigil's own serve/wrap entries, and already-wrapped
detection no longer depends on the binary's filename, so a renamed/versioned binary's wrap
isn't double-wrapped. Reversible via--uninstall. Adversarially reviewed.
No changes to the production protection paths (firewall / redaction / audit). Build
provenance + checksums on every artifact as usual.
中文
真机测试 Claude Code / Codex 接入时发现的缺陷修复。
- 桌面 Activity Feed 现在能反映 CLI 写入的事件(DEF-001)。根因是账本路径不一致:接入指南
指向ledger.sqlite,而桌面读ledger.sqlite3,导致 CLI 与桌面用了两个不同文件、Feed 一直空
(实时监听本身正常)。已订正双语接入指南;serve/wrap启动时打印解析后的账本绝对路径,使用
内存账本(桌面看不到)时响亮警告。 setup --mcp不再嵌套 wrap Vigil 自身的 server(DEF-002)。文档里的vigil-hub serve
自指条目曾被误判为可包裹,产生 wrap 套 serve 的嵌套网关。setup现在跳过 Vigil 自身的 serve/wrap
条目,且"已包裹"检测不再依赖二进制文件名(改名/带版本号的二进制写出的 wrap 不会被二次包裹)。
可经--uninstall还原。已对抗审查。
生产防护路径(firewall / redaction / audit)无变更。每个产物照例带 build provenance + 校验和。
Downloads — which file do I want?
- Desktop app (most users): the installer for your OS — Windows
Vigils_*_x64-setup.exe(or.msi), macOSVigils_*.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>(containsvigil-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 atchrome://extensions. - The
.sigandVigils.app.tar.gzfiles 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