jervis-agent
v0.1.2
Published
Secure local Jervis agent and dynamic ChatGPT GPT Store connector
Maintainers
Readme
jervis-agent
Secure local Jervis runtime for connecting ChatGPT and other supported clients to capabilities on your computer.
Requires Node.js 22 or newer.
Install
npm install -g jervis-agentConnect this computer to the official Jervis GPT
jervis-agent connect --url https://agent.jervis.cloudThe command creates and opens a private, one-time pairing link. After you approve it while signed in to Jervis, the device credential is saved locally, the cloud agent starts in the background, and the official Jervis GPT opens automatically.
The GPT Store URL stays fixed. The pairing link is dynamic and associates your Jervis account with your own device, so the authenticated cloud relay can route GPT requests to that device without exposing a per-user public bridge URL.
For a terminal-only setup, use --no-open. To pair without starting the background agent, use --no-start.
Run
jervis-agent run --daemonThe agent keeps an outbound connection loop to Jervis Cloud, receives capability requests for this paired device, and executes them through the existing Jervis permission/control-plane path. Omit --daemon to keep it attached to the current terminal.
Connect the official Jervis GPT
The recommended GPT Store flow is the dynamic account/device pairing above. The direct local Action bridge remains available for development or a privately configured GPT:
jervis-agent bridge --daemonThen open the official Jervis Agent from the ChatGPT GPT Store:
https://chatgpt.com/g/g-6a7ce17be58881918e11b8effa1517b5-jervis-agentTo keep the bridge attached to the current terminal instead:
jervis-agent bridgeThe bridge reads its security token and optional ngrok configuration from the existing Jervis environment. Never expose it publicly without JERVIS_BRIDGE_TOKEN.
Status
jervis-agent statusSet JERVIS_HOME or JERVIS_CLOUD_CONFIG_PATH to override the local configuration location.
Publishing
From apps/public-agent:
npm publishThe publish lifecycle runs TypeScript checks, tests, the standalone bundle build, and package validation before npm accepts the release.
