Elydora-Infrastructure/Elydora-Open-Source
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(node-cli): confine agent runtime paths

Browse Source
This commit is contained in:
ZacharyZhang-NY committed 2026-07-19 16:45:42 -04:00
1 parent 3d2dccd8d4
commit 9ae1b77e45
6 files changed
+322 -59
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

sdks/node/README.md
+1 -1
View File
@@ -51,7 +51,7 @@ npx elydora install \
--kid agent-456-key-v1
```
The CLI reads the private key and optional API token through hidden terminal prompts. For non-interactive installation, store each secret in an owner-only file and pass `--private_key_file <path>` and `--token_file <path>`. Secret values are rejected as command-line arguments because process listings and shell history can expose them.
The CLI reads the private key and optional API token through hidden terminal prompts. For non-interactive installation, store each secret in an owner-only file and pass `--private_key_file <path>` and `--token_file <path>`. Secret values are rejected as command-line arguments because process listings and shell history can expose them. Agent IDs map to one physical directory directly under `~/.elydora`; portable filename rules and physical-directory checks apply before writes or recursive removal. Ambiguous uninstall discovery requires an explicit agent ID.
Codex performs a one-time trust review for user hooks. Run `/hooks` in Codex after installation and trust the Elydora `PreToolUse` and `PostToolUse` definitions.