Developers

Put evidence in the development loop.

Aegis currently meets developers in VS Code, GitHub workflows, and the local CLI/API. The user interface changes by surface; the underlying trust model does not.

VS CODE

Interactive trust workspace.

Inspect claims, evidence, model provenance, verification, policy, memory, and fix state where code changes happen.

GITHUB ACTION

Pull-request policy gate.

Carry the same security decision model into CI and preserve machine-readable artifacts for review.

CLI + LOCAL API

Automation without a UI dependency.

Use the same local orchestration backend from terminal-driven and integration workflows.

Current surfaces

One trust model.
Three entry points.

These surfaces reflect the public 0.2.0 product. Hosted collaboration and broader software-agent runtime controls are not presented here as shipped capabilities.

Shipping in 0.2.0

Evidence lives next to the code that created the question.

Choose a layer in the inspector. The visual is a representative product view built from capabilities documented in the public 0.2.0 release.

Open Marketplace
Visual Studio Code · Aegis Trusted Analysislocal
fixturevulnerable_sql.pyREVIEW
SQL injectionHIGH

Untrusted request data reaches a SQL execution sink through string interpolation.

VS CODE CLIcode --install-extension aegis-security.aegis-security

You can also install Aegis directly from the VS Code Marketplace. Local setup, contribution instructions, the security policy, and the current architecture remain visible in the public repository.

Which checks ran?

A security decision should carry the checks and evidence that contributed to it, including missing or incomplete steps.

Was execution authorized?

Analysis does not imply permission to execute. Controlled validation remains separately authorized and constrained.

Did the patch actually verify?

A patch proposal and a post-change verification result are distinct lifecycle states.

Can the decision be inspected later?

Evidence, policy, integrity records, and project security memory are designed to make the reasoning traceable after the immediate run is over.