AgentSecure Community
By ShellFrame AI
AgentSecure lets AI coding agents use credentials without exposing the real secret values to the agent.
Why AgentSecure
AI coding agents can access .env files, shell environments, MCP
configuration, and local credentials. Ignore files are not a security boundary.
AgentSecure keeps real secrets outside the agent's normal project and MCP
context.
Quick Start
Run these commands from the project you want to protect.
1. Install AgentSecure
uv tool install agentsecure
2. Optionally scan the project
agentsecure scan .
The scan is local and does not change the project.
3. Run guided setup once
For Claude Code:
agentsecure start --client claude
Follow the printed MCP configuration step, then start Claude Code normally:
claude
For Codex:
agentsecure start --client codex --install-mcp
Then start Codex normally:
codex
agentsecure start is guided one-time project setup. It initializes the
project, offers to move .env secrets into the local vault, writes persistent
agent guidance, and prints or installs the selected MCP configuration.
It is not a persistent background service. After setup finishes, start Claude
Code or Codex normally. You do not normally wrap the agent with
agentsecure run.
How It Works
- During setup, real secrets are moved into the local AgentSecure vault.
- Project files receive aliases or safe placeholders instead of real values.
- The coding agent starts and runs normally.
- Secret-bearing requests use the AgentSecure MCP tool.
- AgentSecure validates the destination and injects the real secret while sending the request outside the agent's context.
Security Boundaries
AgentSecure helps protect against:
- exposing raw secrets to the coding agent through the default MCP flow;
- keeping real secrets in agent-readable project files;
- sending protected secrets to destinations that are not approved by policy.
AgentSecure is not:
- a complete operating-system sandbox;
- a VM or container;
- protection from an attacker who already controls the local user or machine;
- a replacement for endpoint, identity, network, or cloud security controls.
The local user and machine remain inside the trust boundary. See the security model and limitations for the full threat model.
Documentation
- Default workflow
- Claude Code setup
- Codex setup
- Secret management
- MCP usage
- Network policy
- Security model and limitations
- Vault and backup behavior
- Scanner reference
- Advanced runtime mode
- CLI reference
- Implementation architecture
- Uninstall and restore
License
Licensed under the Apache License 2.0. See LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for agentsecure 0.1.23
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| agentsecure-0.1.23.tar.gz | 139.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agentsecure-0.1.23-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 280.4 kB
Release files / agentsecure-0.1.23.tar.gz
| Download URL | agentsecure-0.1.23.tar.gz |
|---|---|
| Size | 139.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80342478c7d6ae45af14e4d54328ad9515bfbde25652c537c76a08c64153f790
|
|
BLAKE2b-256 checksum How to use checksums |
393984d3ff11c181fc53835642931c1b3e888becbb447a81847192f14343bf94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.
Transparency logRelease files / agentsecure-0.1.23-py3-none-any.whl
| Download URL | agentsecure-0.1.23-py3-none-any.whl |
|---|---|
| Size | 141.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cda330241d616d91d40b3d331dc1ca2225adf2c871e9ea0361ced58d48ad9fef
|
|
BLAKE2b-256 checksum How to use checksums |
b6c8cfe528ea04245bafe28b68f9a675f9cbb5c7c101205f72c3e9a037ac00c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.
Transparency log
