@agentvalet/register
v1.6.0
Published
Self-register AI agents with AgentValet
Maintainers
Readme
@agentvalet/register
Register your AI agent with AgentValet in 30 seconds.
Usage
npx @agentvalet/registerNo installation required. Authenticate with GitHub, and your agent is registered automatically.
What it does
- Opens your browser to authenticate with GitHub
- Creates your AgentValet account (or finds your existing one)
- Registers this machine as an agent
- Writes config and your private key to
~/.agentvalet/in your home directory (not the current directory) - Outputs the environment variables you need
Already have an agent on this machine?
An agent's private key exists only on your machine — the proxy never sees it, and there is no rotation endpoint. Overwriting it destroys that identity, along with its grants and audit continuity.
So registering while ~/.agentvalet/agent.key already belongs to a different
agent stops with an error rather than overwriting it. You have two options:
# Keep both — store the new agent under ~/.agentvalet/<label>/
npx @agentvalet/register claim <bind_secret> --label work-laptop
# Replace the existing one — a timestamped backup is written first
npx @agentvalet/register --forceRe-registering the same agent over its own key is always allowed.
Requirements
- Node.js 18+
- A GitHub account
- An internet connection
After registration
Approve your agent in the AgentValet dashboard to activate it: https://app.agentvalet.ai/agents
Commands
npx @agentvalet/register # Register a new agent (GitHub onboarding)
npx @agentvalet/register refresh # Refresh approved permissionsWhat gets written
.agentvalet/config.json— agent ID, proxy URL, registration timestamp.agentvalet/agent.key— private key (mode 0600, never shared)
.agentvalet/ is automatically added to your .gitignore.
Advanced: existing owner ID
If you already have an AgentValet owner ID, pass it directly:
AGENTVALET_OWNER=<your-owner-id> npx @agentvalet/registerGitHub OAuth App
The GitHub Device Flow uses AgentValet's OAuth App (client ID is public — the Device Flow does not use or expose the client secret). No secrets are stored on your machine.
