Vigil 1.2.4

Fixed

• Remediation startup binds Claude's native conversation identity and attaches automatically,
  including when the background host assigns a different session ID.

Changed

• Startup shows the selected repository, profile, and configured checks. Claude reads the
  profile and explains settings or checks that affect the work.
• First verification plans require explicit evidence requirements appropriate to the case.
• Developers account for required checks before editing. Coordinators keep owner approvals
  separate for each case.
• The remediation UI enables plan updates after the developer records the initial plan and
  evidence requirements.

Install or upgrade

uv tool install --force --from https://github.com/VigilOSS/Vigil/releases/download/v1.2.4/vigil-1.2.4-py3-none-any.whl vigil
vigil install

Restart services that vigil status reports as stale. The running backend must restart to load
the verification-plan gate. End existing official client sessions before starting new sessions
on the same engagement after upgrading.

The wheel includes the CLI, backend, prompts, documentation, and prebuilt UI. Release installation
does not require Git or Node. Verify the downloaded wheel or source archive against SHA256SUMS.

Vigil 1.2.3 — Clearer assessment output and indexing activity

Install:

uv tool install --from https://github.com/VigilOSS/Vigil/releases/download/v1.2.3/vigil-1.2.3-py3-none-any.whl vigil

Upgrade: install the wheel with uv tool install --force --from <wheel-url> vigil, then run vigil install. Running services and client sessions retain their current application release until restarted.

Changes:

• Code-dispatch table values retain clear column boundaries, and truncated handoffs accurately identify omitted artifact and runtime records.
• CLI help describes supported file-search filters, collection reads, work-buffer input, finding patch requirements, and complete-inventory indexing.
• Structural indexing emits automatic, non-interactive phase messages and sparse activity counts on stderr at completed-file boundaries, roughly every 30 seconds. A single slow file can exceed that interval.
• Cleanup warnings accurately describe an unconfirmed exit outcome as unverified cleanup.

Validation: all six blocking CI jobs passed. The source-archive-to-wheel packaging path and a fresh installed-wheel smoke test against an isolated local backend passed, including ingest/index/sync, queue/handoff output, error handling, and durable-state persistence across restart. No live target or shared runtime testing was performed.

SHA256:

c6399002125c80ab76e3c228e5167e2833ab74a07ef325672f69cfadf1a9233c  vigil-1.2.3-py3-none-any.whl
cbd825817919ae110ae1370fd0727bdb59f77e0845fcf5dffba99a5025ac40bf  vigil-1.2.3.tar.gz

Vigil 1.2.2 — Safer runtime startup and smaller defaults

Install:

uv tool install --from https://github.com/VigilOSS/Vigil/releases/download/v1.2.2/vigil-1.2.2-py3-none-any.whl vigil

Upgrade: install the wheel with uv tool install --force --from <wheel-url> vigil, then run vigil install.

Changes:

• Shared Kali runtime defaults to a 2 GiB memory limit and 1 CPU.
• Runtime restarts check capacity before replacing the running container.
• Resource warnings describe configured limits and go to stderr; memory refusals give effective recovery commands.
• vigil up --allow-oversubscribe supports intentional overrides.
• vigil up has concise startup progress, and vigil up --json returns one structured startup result. Docker/UI build progress goes to stderr in JSON mode.

Existing containers keep their limits until recreated. End active runtime sessions before running vigil runtime restart. Heavy or parallel workloads can set explicit higher limits.

SHA256:

b9239daf9a01e7470eb82c2a69377f11565d0486c3ffe7d6cee8f48e122604e9  vigil-1.2.2-py3-none-any.whl
07ae7b5ae9cf44ce3e41a0e6d4cb6f76c2742ffdb45a0e4c8bb5840ec6ce6045  vigil-1.2.2.tar.gz

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 vigil

Upgrade: uv tool install --force --from <wheel-url> vigil, then vigil install.

Changes:

• vigil engagement create prints 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 up

Or 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 vigil

Upgrade 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-autoprompt opens the client without Vigil's automatic opening message. Claude -r/--resume and Codex resume keep 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 up

Existing 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