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
Credential Proxy Overview
Secrets Management
Environments
env Injection
Workspaces & Teams
Projects
Agent Identity
Audit & Governance
account (init / login / logout)
server (get / set / status / reset)
secrets (set / list / delete / push / pull)
proxy (start / stop / status / logs)
call (inject requests via proxy)
env (execute commands with secrets)
workspace (list / create / switch / roles)
project (list / create / use / update)
environment (list / switch / copy / merge)
agent (register / list / tokens)
agent policy (set / get / delete)
logs (list / watch / export / verify)
mcp (serve / install / config)
status (system & session diagnostics)
Aliases & Shortcuts
docs (interactive terminal viewer)
Shell Autocompletion
keychain-auth (daemon & security)
Ecosystem Overview
Zero-Knowledge MCP Server
Integrations Overview
Claude Desktop
Cursor IDE
OpenClaw
HTTP Proxy (Any Client)
LangChain (Native)
CrewAI (Native)
CI/CD Pipeline
SDK Overview
Python SDK
Python API Reference
Python SDK Manual Testing
JavaScript SDK (Soon)
ZK-MCP Integration Guide
Server Overview
5-Layer Architecture
Self-Hosting Guide
Self-Hosting Operations Manual
Server Data Migration
Authentication & Keys
Workspaces & Teams Backend
Projects & Scope Backend
Environments Backend
Secrets & Sync Protocol
Agent Identity Resolution
Telemetry & Metrics Engine
Audit Log Sync
API Endpoint Reference
Cloud Overview & Architecture
The Dual-Engine Model
Cloud Resolver Data Plane
Workload & Agent Tokens
Egress Allowlists & Audit Streams
Cloud REST API 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.x
v2.1.0
v2.0.0
v1.4.0
v1.3.x
v1.2.0
v1.1.x
v1.0.x
Workspaces & TeamsCreating a Workspace

Creating a Workspace

Shared workspaces are the primary unit of collaboration in AgentSecrets. They allow you to group projects, configure access controls, share encrypted credentials securely, and audit agent activity across a team.


The create command

To create a new shared workspace, use the agentsecrets workspace create command. The user who runs this command is automatically assigned the Owner and Admin roles.

agentsecrets workspace create "Acme Engineering"

Under the hood, creating a workspace performs the following actions:

  • Generates a local cryptographic workspace keypair (ECDH) that will be used to encrypt and decrypt workspace secrets.
  • Registers the workspace metadata on the AgentSecrets backend.
  • Sets up the root administrator permissions for the creator.

Naming and setup

Workspace names must be alphanumeric and can contain spaces, dashes, or underscores. They should clearly represent your team or organization context.

  1. Choose a unique name: Choose a descriptive name for the workspace, such as "Acme Engineering" or "Billing Team".

    agentsecrets workspace create "Billing Team"
  2. Verify workspace creation: Listing your workspaces will show both your default personal workspace and the newly created shared workspace.

    agentsecrets workspace list

    Output:

    * personal (your-username) ← active Billing Team (shared) 1 member
  3. Switch to the new workspace: Switch to the new workspace to begin creating projects and configuring allowlists.

    agentsecrets workspace switch "Billing Team"
  4. Verify the active context: Check the active workspace and environment:

    agentsecrets status

All subsequent CLI commands (such asproject create, secrets set, and workspace allowlist) run in the context of the active workspace. Always verify your active workspace with agentsecrets status before making changes.


Inviting your first members

Once a shared workspace is created, you can invite team members immediately. Inviting a developer initiates a secure, end-to-end encrypted key exchange.

  1. Invite members via CLI: Provide the email addresses of the developers you wish to invite:

    agentsecrets workspace invite [email protected] [email protected]
  2. Wait for acceptance: Invited members will receive an email containing a secure link. They can accept it via the CLI or web dashboard. Once accepted, their local CLI generates its own keypair and exchanges public keys with your workspace.

You can only invite collaborators to aShared Workspace. Personal workspaces are restricted to solo use. If you need to share a project from a personal workspace, use agentsecrets project invite, which automatically handles the migration of that project to a new shared workspace.

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