Repository navigation
Releases: VigilOSS/Vigil
Release list
Vigil 1.2.1
Install:
uv tool install --from https://github.com/VigilOSS/Vigil/releases/download/v1.2.1/vigil-1.2.1-py3-none-any.whl vigilUpgrade: uv tool install --force --from <wheel-url> vigil, then vigil install.
Changes:
vigil engagement createprints the engagement key and start command the same way for every engagement type.- README and installation guide rewritten.
SHA256:
33785a0558af0c648bc385fe54f085f319d2713b9070ebb71024e46d4e2cf9f4 vigil-1.2.1-py3-none-any.whl
f8cc75bfb6797a219b66da0cb8d069cf613c40eb6e8b4b5a15532583f4245d10 vigil-1.2.1.tar.gz
Vigil 1.2.0 — Code source onboarding and usage guidance
Vigil 1.2.0 adds guided code-engagement source onboarding, cleaner client startup control, and practical model, effort, and usage guidance.
The wheel includes the CLI, backend, prompts, schemas, Docker definitions, documentation, legal files, and prebuilt frontend/report. Consumer installation needs neither Git nor Node.
Install:
uv tool install --from https://github.com/VigilOSS/Vigil/releases/download/v1.2.0/vigil-1.2.0-py3-none-any.whl vigil
vigil quickstart
vigil upOr install directly from the repository, which builds the UI locally and needs Git, Node.js, and npm:
uv tool install git+https://github.com/VigilOSS/Vigil vigilUpgrade an existing install with uv tool install --force --from <wheel-url> vigil. Running services and client sessions keep their original release assets until restarted; vigil status and vigil doctor report restart requirements.
Highlights:
- Code engagement creation prepares a
source/folder; code sessions confirm the staged source at startup and work with loose files or project folders without Git. vigil engagement start --no-autopromptopens the client without Vigil's automatic opening message. Claude-r/--resumeand Codexresumekeep their native arguments.- Database backups run from the backend scheduler and migrations.
- The README documents which models support web and code engagements, recommended reasoning effort and plan sizing, and a bug bounty workflow from source maps to web testing.
See README.md, docs/installation.md, and CHANGELOG.md in the repository for prerequisites and details.
SHA256:
58c2662dfcfd5c78c0de338fe67cd9b22a1fd7f1d4f0cbddfd322131696e3359 vigil-1.2.0-py3-none-any.whl
b37701f09f7357022817f6bb8ccf712a1b8c3e278d353961e89ccab23118e9b9 vigil-1.2.0.tar.gz
Vigil 1.1.0 — Application releases and private workspaces
Vigil 1.1.0 separates a matched application release from private operator workspaces.
The wheel includes the CLI, backend, prompts, schemas, Docker definitions, documentation, legal files, and prebuilt frontend/report. Consumer installation needs neither Git nor Node.
Install:
uv tool install --from https://github.com/VigilOSS/Vigil/releases/download/v1.1.0/vigil-1.1.0-py3-none-any.whl vigil
vigil quickstart
vigil upExisting workspaces are adopted in place without relocating engagements, evidence, databases, configuration, or custom client files. Running services and client sessions retain their original release assets until explicitly restarted. Use vigil status and vigil doctor to inspect restart requirements.
This release also fixes application source discovery, bundled documentation, dual-track mode inspection and ambiguity messages, session-mode guidance, and startup context on stderr.
See README.md, docs/installation.md, and CHANGELOG.md in the repository for prerequisites and upgrade details.
SHA256:
09930216fdc24bfc7488e670aae91731d47bbacd248b5dc63f816e9537d92bb7 vigil-1.1.0-py3-none-any.whl
c7740b6948cb7e717963d3f95f660a11cabde4d6dbe14a71d3600611d302f973 vigil-1.1.0.tar.gz