hep-login
Sign this machine into Agentlas (opens the browser sign-in window).
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/HEAD/.claude/commands/hep-login.md -o ~/.claude/commands/hep-login.mdhep-login.md
Update fallback: 자동 업데이트가 안 되면 `hephaestus update`를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.
# /hep-login
Sign this machine into Agentlas so cloud staffing, uploads, and paid Hub calls
work. Raw request: `$ARGUMENTS`
Resolve the runner (authentication only):
```bash
RUNNER=""
for candidate in \
"$HOME/.agentlas/runtime/current/bin/hephaestus" \
"${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/bin/hephaestus}" \
"${PLUGIN_ROOT:+$PLUGIN_ROOT/bin/hephaestus}" \
"${GEMINI_EXTENSION_ROOT:+$GEMINI_EXTENSION_ROOT/bin/hephaestus}" \
"./bin/hephaestus"
do
if [ -n "$candidate" ] && [ -x "$candidate" ]; then RUNNER="$candidate"; break; fi
done
"$RUNNER" auth login --timeout 570
```
1. Run the login command above in the foreground and wait for it — it opens
the browser sign-in window and blocks until the user finishes (up to ~10
minutes). Tell the user, in their language, that a browser sign-in window
just opened and they should complete it there.
2. If the output prints an authorization URL line instead (the browser could
not be opened), show that URL to the user as a clickable link and keep the
command running — clicking it completes the same sign-in.
3. When it exits, run `"$RUNNER" auth status` and report plainly:
`authenticated` (say sign-in is done and cloud commands now work) or
`signed_out` (say it did not complete, show the exact error line, and offer
to run `/hep-login` again).
4. Never print token values. Never paste the user's credentials anywhere.
If the user asked for something else after `/hep-login` (extra words in the
raw request), treat sign-in as the prerequisite step and continue with that
request only after `authenticated`.Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Use the Agentlas browser hardpoint for browser-required work.
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Prepare explicitly named Agentlas Hub or Cloud agents.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Connect Agentlas agents or teams to Telegram.
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.