jev-setup
Use when Jev is not working yet, a Jev tool reports no_key or auth_failed, or the person asks to connect or fix Jev. Gets their TypeSafe or OpenRouter key into the secret store, unseen by you.
kerpopule · 站主发布
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add https://github.com/kerpopule/hermes-jev-skills/tree/e5918165f457717b388152efd26f1de32d587466/skills/jev-setup --skill "jev-setup"技能说明
name: jev-setup description: Use when Jev is not working yet, a Jev tool reports no_key or auth_failed, or the person asks to connect or fix Jev. Gets their TypeSafe or OpenRouter key into the secret store, unseen by you. version: 0.2.0 license: MIT metadata: hermes: tags: [jev, typesafe, setup, credentials]
Connect Jev (the key never passes through you)
Jev is TypeSafe's decision model. It needs one API key. You must never see, ask for, or handle that key.
The key can come from either of two places, and the same Jev answers either way:
- TypeSafe (
jev setup-key, the default): a key from console.typesafe.ai. - OpenRouter (
jev setup-key --provider openrouter): reaches Jev through OpenRouter's Decisions API. Worth offering when the person already has an OpenRouter key, because it is then one key instead of two and one bill instead of two.
If both keys exist, TypeSafe is used: an existing install never starts routing its decisions somewhere else because an OpenRouter key happened to be in the environment for a text model. jev doctor reports which one is in use under key.provider.
Rules
- Never ask the person to paste the key into the chat. If they paste one anyway, do not store it, do not repeat it, tell them that key should be replaced, and start the flow below.
- Never read the secret store,
.envfiles or~/.config/jev/credentialsto "check" the key. Usejev doctor, which reports only presence and length. - Never put the key in a command line, a URL, a config file you write, or a log.
Flow
-
Check the state:
jev doctor. Ifkey.presentis true andjev.reachableis true, you are done. -
Start the private key page:
jev setup-keyIt opens a page in the browser on the computer you are running on and prints one JSON line on stderr with a
url. The URL holds no secret. -
Tell the person, in one sentence, to paste their TypeSafe key into the page that just opened. If
browser_openedis false, or they are talking to you from another device (Telegram, phone), send them theurland tell them it only opens on the computer the agent runs on. If they have no key yet, they create one at https://console.typesafe.ai/settings/keys. -
Wait for the command to finish. It prints
{"status": "stored", "verified": true, ...}when the key was saved and the provider accepted it.rejectedmeans the key was wrong: run it again.timed_outmeans nobody used the page within ten minutes. -
Run
jev doctoronce more and report the result in a sentence.
When there is no browser
Headless server over SSH: the person runs jev setup-key --tty themselves in their own terminal. It is a hidden prompt. Do not run it for them through a tool that captures the terminal.
Remote machine on a private network (Tailscale, VPN): jev setup-key --host <private-ip> --no-open and send them the link. That traffic is plain HTTP, so use it only on a network you trust end to end. Never bind a public address.
Where the key goes
The OS secret store (macOS Keychain service Hermes TypeSafe API, or secret-tool on Linux), falling back to ~/.config/jev/credentials (mode 0600). On a Hermes machine it is also written as TYPESAFE_API_KEY into ~/.hermes/.env and every profiles/*/.env, because each Hermes lane reads its own file. Running gateways pick it up on their next restart; do not restart one without being asked.