28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
---
|
|
description: Set up or control the grok-glance phone dashboard (status, enrol a device, approval policy)
|
|
argument-hint: [status | up | stop | enroll | set-origin <url> | devices | revoke <id> | approval off|risky|all | logs]
|
|
---
|
|
|
|
Run the grok-glance CLI and report the result plainly.
|
|
|
|
The CLI lives at `$GROK_PLUGIN_ROOT/bin/glance`. The user asked for: **$ARGUMENTS**
|
|
|
|
If no argument was given, treat it as `status`.
|
|
|
|
Then:
|
|
|
|
1. Run `node "$GROK_PLUGIN_ROOT/bin/glance" $ARGUMENTS`.
|
|
2. If it says the plugin is not built, run `npm install && npm run build` in `$GROK_PLUGIN_ROOT`
|
|
(this takes a minute or two) and try again.
|
|
3. Report what came back. For `enroll`, show the URL and the code verbatim — the user needs to
|
|
type them on their phone, so do not paraphrase or reformat them.
|
|
4. If the output mentions that no public origin is configured, explain the Tailscale Serve setup:
|
|
`tailscale serve --bg 127.0.0.1:8791`, then
|
|
`node "$GROK_PLUGIN_ROOT/bin/glance" set-origin https://<box>.<tailnet>.ts.net`.
|
|
|
|
For anything beyond running the command — troubleshooting a failed passkey prompt, explaining the
|
|
approval modes, or a first-time setup — read the `glance` skill and follow it.
|
|
|
|
Do not change the approval policy unless that is what was asked. Warn before running `set-origin`
|
|
on a setup that already has devices enrolled: the RP ID changes and existing passkeys stop working.
|