What is AgentSecrets?
The Zero-Knowledge Difference
How AgentSecrets Works
Installation
Quick Start
Migrating from .env Files
Migrating from Vault / AWS
Migrating from dotenv-vault
Production Checklist
Credential Exposure
What Zero-Knowledge Means
The Proxy Model
The Three-Layer Model
Environments
Agent Identity
Storage Modes
The No get() Principle
Secret-Level Policies
Cloud Overview & Architecture
The Dual-Engine Model
Cloud Resolver Data Plane
Workload & Agent Tokens
Egress Allowlists & Audit Streams
Cloud REST API Reference
Account (init / login)
Server & Self-Hosting (server)
Docs
Shell Autocompletion
Keychain Auth
Secrets
Environments
Credential Proxy
env Injection
Workspaces & Teams
Projects
Agent Identity
Audit & Governance
Integrations Overview
Claude Desktop
Cursor
OpenClaw
HTTP Proxy (Any)
LangChain (Soon)
CrewAI (Soon)
CI/CD Pipeline
SDK Overview
Python SDK
Python API Reference
Python SDK Manual Testing
JavaScript SDK (Soon)
Ecosystem Overview
Zero-Knowledge MCP Server
Server Overview
5-Layer Architecture
Self-Hosting Guide
Authentication & Keys
Workspaces & Teams
Projects & Scope
Environments
Secrets & Sync Protocol
Agent Identity Resolution
Telemetry & Metrics Engine
Audit Log Sync
API Endpoint Reference
Security Overview
Anti-Impersonation & Process Verification
Encryption Model
Zero-Knowledge Sync
Proxy Security Layers
Threat Model
OWASP Top 10 Mitigation
Security FAQ
Third-Party Audit
Reporting Vulnerabilities
Guides Overview
Building on the SDK
Stripe Integration
OpenAI Integration
Multi-Agent Setup
Onboarding Team
CI/CD Pipeline
Publishing ZK MCP
Rotating Credentials
Auditing Team Activity
Dev to Production
Kubernetes Deployment
Monorepo Setup
Production Proxy Hardening
vs .env Files
vs HashiCorp Vault
vs AWS Secrets Manager
vs dotenv-vault
vs Infisical
When Not to Use
Proxy Not Starting
Proxy Not Resolving
Domain Blocked
Sync Conflicts
MCP Not Connecting
Session Token Errors
Proxy Session Authorization
Keychain Storage & Backends
SSRF & Destination Rules
Installation Issues
Error Codes Reference
Frequently Asked Questions
v3.1.x
v3.0.0
v2.1.0
v2.0.0
v1.4.0
v1.3.x
v1.2.0
v1.1.x
v1.0.x
CLI ReferenceCleaning an Environment

agentsecets enviCleaning an Environment

The clean command

agentsecrets environment clean

clean deletes all secrets in the active environment, from the OS keychain locally and from the cloud.

When to use clean

Clean is useful when decommissioning a project, resetting a test environment to a known empty state, or removing stale secrets from an environment that is no longer in use.

It is not the right tool for removing individual secrets, use agentsecrets secrets delete KEY for that.

What clean does not remove

Clean does not affect:

  • other environments
  • workspace configuration
  • project configuration
  • allowlists
  • encryption keys
  • team membership
  • project metadata

Only secrets in the currently active environment are deleted.

Safety confirmation

Because clean is destructive, confirmation is required before deletion proceeds.

Example:

This will permanently delete all 12 secrets in production. This cannot be undone. Continue? (y/n):

Typing y proceeds. Anything else cancels the operation.

Irreversible operation

Clean is permanent, there is no undo. Deleted secrets cannot be recovered from AgentSecrets. If teammates have already pulled the secrets to their local keychains, those copies remain. Clean only removes the cloud blobs and your local keychain entries.

Typical cleanup workflow

agentsecrets environment switch staging agentsecrets environment clean

This resets the staging environment back to an empty state while leaving development and production untouched.

Was this helpful?
Thanks for your feedback!
Your feedback helps us improve the platform.