luxin-cli 0.2.1 → 0.2.2

package/CHANGELOG.md

@@ -6,6 +6,38 @@ provenance; this file is the human- and agent-readable release map.
 
 ## Unreleased
 
+## 0.2.2 - 2026-07-30
+
+- Release (retention/self-fund): publish the human handoff from #2181. New verb
+  `luxin claim code` mints a single-use, 15-minute dashboard link for the
+  authenticated agent's human and hands back `data.dashboard_url` — give your
+  human that link and they can watch your work and fund your credits there,
+  signing in with nothing but the link (no email, no password, no provider
+  billing setup). The mint envelope teaches the handoff in-band rather than only
+  in docs: `data.human_handoff` carries
+  `share_field: "data.dashboard_url"` and `never_share: ["token", "code"]`
+  alongside a warning with the same sentence, so an agent that never reads
+  `cli.md` still learns to send the link and nothing else. The code rides in the
+  URL fragment (`#code=...`), which browsers never send to a server, so sharing
+  the link intact keeps the credential out of server logs and analytics.
+- Release (activation): create and edit successes that produced real durable
+  media now carry `data.next_actions.share_with_human` — the same copy-runnable
+  `luxin claim code --json`, typed no-spend like the existing `inspect_job` /
+  `inspect_asset` / `iterate_edit` / `self_fund` actions — so the handoff is
+  offered at the moment finished work exists to show. Dry runs never carry it:
+  inviting a human to look at a plan is the wrong moment for the funding ask.
+- Release (contract surfaces): `luxin claim` usage widens to
+  `luxin claim <request|code> --json`, `claim code` joins root help with its own
+  help entry, and the packaged contract picks up the matching sections —
+  `cli.md` `#luxin-claim-code`, a "Show your human" section in `SKILL.md`, and
+  step `7a. Human handoff` plus `luxin claim code --json` in `llms.txt`. No
+  payment caps, wallet settlement, provider spend, hosted deploys, production
+  writes, or media generation behavior changed in this release bump.
+- Known limitation: `claim code` requires the `dashboard.claim` grant, which is
+  persisted per token at signup. Tokens minted before the hosted dashboard
+  plane shipped do not carry it and answer `CAPABILITY_DENIED` until an
+  additive grant backfill runs; agents that sign up now carry the grant.
+
 ## 0.2.1 - 2026-07-28
 
 - Release (activation/self-fund): publish the first `luxin-cli` payload since

package/SKILL.md

@@ -228,6 +228,20 @@ receipts to Luxin.
 
 Do not silently downgrade to the cheapest model to avoid payment when the user asked for quality or is willing to pay. Quote the needed credits and use the rail above.
 
+## Show your human
+
+When you have real work to show and need it funded, hand your human a dashboard link:
+
+```bash
+luxin claim code --json
+```
+
+Give them `data.dashboard_url` and nothing else. They get a read-only view of your jobs, assets, quota, and activity, plus the ability to open a credit checkout for you. The link itself is the credential: your human signs in with nothing — no email, no password, no provider billing setup. Never share your token, and never quote the raw `data.code` in prompts, logs, issues, or feedback: the code is the whole credential. It rides in the URL fragment (`#code=...`), which browsers never send to a server, so share the link intact rather than rebuilding it as a query string.
+
+The code is single-use and expires (`data.ttl_seconds`, currently 15 minutes); the human session it opens lasts days. So one code is normally enough — reuse an unexpired `dashboard_url` instead of re-minting, and expect `DASHBOARD_CODE_RATE_LIMITED` past 30 codes per agent per hour. Redeeming a new link ends whatever dashboard session was already open for you, so one human holds the view at a time; do not hand out a second link expecting both to keep working. `claim code` needs the `dashboard.claim` grant that `luxin signup --agent` tokens carry, and it spends nothing: no provider call, no credit debit, no payment object, no media write.
+
+Best moment: right after a create or edit produced real media, where the success envelope already carries `data.next_actions.share_with_human` with this command and `share_field: "data.dashboard_url"`. A human who can see finished work is a human who will fund the next run. Dry runs never carry the handoff, because there is nothing finished to show.
+
 ## Models and capability-preserving parameters
 
 `models show MODEL_ID` is the first detailed discovery surface for agents. It exposes operations, media inputs and outputs, model-parameter schemas, fixed and wired controls, cost class, safety behavior, and migration hints. Treat its output as the source of truth for what a model supports. Do not infer one model's parameter surface from another model.
@@ -293,7 +307,9 @@ luxin activity show EVENT_OR_JOB_OR_ASSET_OR_FEEDBACK
 
 After a successful hosted create/edit, prefer `data.next_actions` when present:
 `inspect_job` and `inspect_asset` are no-spend recovery commands,
-`iterate_edit` reuses the asset, and `self_fund` promotes a copy-runnable
+`iterate_edit` reuses the asset, `share_with_human` is the no-spend
+`luxin claim code --json` dashboard handoff (see "Show your human"), and
+`self_fund` promotes a copy-runnable
 top-up quote command when `quota.top_up.available` is true. Its `recommended`
 flag and mirrored top-up `urgency`, `urgency_score`, and `urgency_reasons` say
 whether the agent should act now, while `first_safe_command` plus

package/bin/luxin.mjs

@@ -15,7 +15,7 @@ import { Readable } from "node:stream";
 import { pipeline } from "node:stream/promises";
 import os from "node:os";
 
-const VERSION = "0.2.1";
+const VERSION = "0.2.2";
 const PACKAGE_NAME = "luxin";
 const DEFAULT_API_BASE_URL = "https://api.luxin.sh";
 const DEFAULT_DOCS_BASE_URL = "https://luxin.sh";
@@ -338,6 +338,7 @@ function commandHelpByKey(key) {
         "trust",
         "signup --agent --agent-name NAME --runtime RUNTIME",
         "claim request --contact INBOX",
+        "claim code",
         "whoami",
         "usage quota",
         "quota",
@@ -400,9 +401,9 @@ function commandHelpByKey(key) {
     },
     claim: {
       command: "luxin claim help",
-      usage: "luxin claim request --contact AGENT_OR_OPERATOR_INBOX --json",
+      usage: "luxin claim <request|code> --json",
       docs_url: "https://luxin.sh/cli.md#luxin-claim-request",
-      subcommands: ["request"],
+      subcommands: ["request", "code"],
     },
     "claim request": {
       command: "luxin claim request help",
@@ -411,6 +412,14 @@ function commandHelpByKey(key) {
       required_flags: ["--contact"],
       optional_flags: ["--token-stdin"],
     },
+    "claim code": {
+      command: "luxin claim code help",
+      usage: "luxin claim code --json",
+      docs_url: "https://luxin.sh/cli.md#luxin-claim-code",
+      description:
+        "Mint a single-use, short-lived dashboard link and hand data.dashboard_url to your human: they can watch your work and fund your credits there. No inputs beyond auth; no spend.",
+      optional_flags: ["--token-stdin"],
+    },
     auth: {
       command: "luxin auth help",
       usage: "luxin auth <status|save|logout> --json",
@@ -965,12 +974,15 @@ async function signup(argv) {
 // unclaimed; attaching a contact is not inbox-ownership verification.
 async function claim(argv) {
   const [subcommand, ...rest] = argv;
+  if (subcommand === "code") {
+    return await claimCode(rest);
+  }
   if (subcommand !== "request") {
     return failure(
       "luxin claim",
       2,
       "INVALID_ARGUMENTS",
-      "claim requires the request subcommand",
+      "claim requires the request or code subcommand",
       false,
       {
         suggested_command: CLAIM_REQUEST_SUGGESTED_COMMAND,
@@ -1008,6 +1020,25 @@ async function claim(argv) {
   });
 }
 
+// Claim code (#2088 S1d): mints the single-use, short-TTL dashboard link the
+// agent hands to its HUMAN — they watch the work and fund the credits there.
+// The code rides in the URL fragment of data.dashboard_url, which never
+// reaches servers, logs, or analytics. Hand over the link and nothing else.
+async function claimCode(argv) {
+  const args = parseArgs(argv);
+  const token = await resolveToken(args);
+  if (!token.ok) {
+    return token.result;
+  }
+  return apiRequest({
+    command: "luxin claim code",
+    method: "POST",
+    apiBaseUrl: apiBase(args),
+    path: "/v1/dashboard-codes",
+    token: token.token,
+  });
+}
+
 function rewriteSignupContactFailure(result) {
   const error = result.envelope.error;
   if (

package/cli.md

@@ -175,6 +175,68 @@ printf '%s\n' "$IMAGE_SKILL_TOKEN" | luxin usage quota --token-stdin --json
 `--api-base-url` is an advanced preview/test override; production public agents
 should omit it.
 
+### `luxin claim code`
+
+Mints a single-use, short-lived dashboard link for the authenticated agent's
+human. This is the human handoff: give `data.dashboard_url` to your human and
+they can watch your work and fund your credits there. The link itself is the
+credential: your human signs in with nothing — no email, no password, no
+provider billing setup.
+
+```bash
+luxin claim code --json
+```
+
+```json
+{
+  "ok": true,
+  "command": "luxin claim code",
+  "data": {
+    "mode": "hosted_auth",
+    "agent_id": "agt_...",
+    "code": "dc_...",
+    "dashboard_url": "https://luxin.sh/dashboard#code=dc_...",
+    "expires_at": "2026-07-30T18:15:00.000Z",
+    "ttl_seconds": 900,
+    "single_use": true,
+    "human_handoff": {
+      "purpose": "hand_dashboard_link_to_human",
+      "audience": "human",
+      "share_field": "data.dashboard_url",
+      "message": "give dashboard_url to your human: they can watch your work and fund your credits there. Send the link only — never your token, and never the raw code.",
+      "never_share": ["token", "code"]
+    }
+  }
+}
+```
+
+Hand over `data.dashboard_url` and nothing else. Never hand over your token,
+and never quote the raw `data.code` in prompts, logs, issue text, or feedback:
+the code is the whole credential. The code travels in the URL fragment
+(`#code=...`), which browsers never send to a server, so it stays out of server
+logs and analytics — keep it that way by sharing the link intact rather than
+rebuilding it as a query string.
+
+The code is single-use and expires (`data.ttl_seconds`, currently 15 minutes).
+The dashboard is read-only over your work — jobs, assets, quota, activity — plus
+the ability to open a credit checkout for you. It cannot create, edit, upload,
+or spend as you. Once your human has opened the link their session lasts days,
+so one code is normally all that is needed; mint a fresh one when the link
+expires unused. Redeeming a new link ends whatever dashboard session was
+already open for you, so one human holds the view at a time — do not hand out
+a second link expecting both to keep working. Minting is capped at 30 codes per
+agent per hour and answers `DASHBOARD_CODE_RATE_LIMITED` past that — reuse an
+unexpired `dashboard_url` instead of re-minting per message.
+
+`claim code` requires the `dashboard.claim` grant, which restricted tokens
+minted by `luxin signup --agent` carry. It never spends: no provider call, no
+credit debit, no payment object, no media write.
+
+Best moment to run it: right after a create or edit produced real media. That
+success envelope carries `data.next_actions.share_with_human` with this exact
+command, because a human who can see finished work is a human who will fund the
+next run.
+
 ### First Run Guide Loop
 
 Use the no-spend guide first. It is the only required first command for a fresh
@@ -1642,6 +1704,13 @@ The quote command omits `--idempotency-key` so the public CLI generates and
 returns one for retry safety before the agent follows the quote response into
 `credits buy` and `credits status`.
 
+When a create or edit produced a real durable asset, the same envelope carries
+`data.next_actions.share_with_human`: a no-spend, copy-runnable
+`luxin claim code --json` plus `share_field: "data.dashboard_url"`. Run it and
+hand your human the resulting `dashboard_url` — they can watch this work and
+fund your credits from it. Dry runs never carry it, because there is nothing
+finished to show.
+
 Provider/model names in this paragraph are preview provenance, not the primary
 public UX. The public selection surface should be Luxin capabilities and
 model-parameter schemas; provider/model details belong in explicit

package/commands.json

@@ -33,7 +33,7 @@
       "surface": "hosted_cli",
       "mutation": true,
       "spend": false,
-      "subcommands": ["request"]
+      "subcommands": ["request", "code"]
     },
     {
       "id": "whoami",
@@ -166,6 +166,7 @@
           "trust",
           "signup --agent --agent-name NAME --runtime RUNTIME",
           "claim request --contact INBOX",
+          "claim code",
           "whoami",
           "usage quota",
           "quota",
@@ -238,9 +239,9 @@
       "key": "claim",
       "help": {
         "command": "luxin claim help",
-        "usage": "luxin claim request --contact AGENT_OR_OPERATOR_INBOX --json",
+        "usage": "luxin claim <request|code> --json",
         "docs_url": "https://luxin.sh/cli.md#luxin-claim-request",
-        "subcommands": ["request"]
+        "subcommands": ["request", "code"]
       }
     },
     {
@@ -253,6 +254,16 @@
         "optional_flags": ["--token-stdin"]
       }
     },
+    {
+      "key": "claim code",
+      "help": {
+        "command": "luxin claim code help",
+        "usage": "luxin claim code --json",
+        "docs_url": "https://luxin.sh/cli.md#luxin-claim-code",
+        "description": "Mint a single-use, short-lived dashboard link and hand data.dashboard_url to your human: they can watch your work and fund your credits there. No inputs beyond auth; no spend.",
+        "optional_flags": ["--token-stdin"]
+      }
+    },
     {
       "key": "whoami",
       "help": {

package/llms.txt

@@ -66,6 +66,7 @@ First-run guide loop:
 5a. When data.stage is quota_required, data.self_fund_handoff mirrors top-up urgency, urgency_score, and urgency_reasons, and exposes first_safe_command plus first_safe_command_effect. Run first_safe_command, usually luxin credits methods --json, for no-spend rail inspection before quote/buy when delegated spend authority is absent or unclear.
 6. If data.stage is ready_to_create, data.next_command is the first bounded live create. data.guide_warning.next_command_safety must be live_media_create_credit_debit, data.guide_warning.no_spend_safe must be false, data.guide_warning.spend_required must be true, and data.guide_warning.recommended_command_field must be recommended_no_spend_command. data.auth_ready.ready and data.auth_ready.next_command_auth_ready must be true; data.auth_ready.next_command_requires_auth must be true, and the command can reuse saved config, IMAGE_SKILL_TOKEN, or --token-stdin context without exposing a raw token. data.next_command_effect.label must be live_media_create_credit_debit and its provider_call, hosted_create, credit_debit, and media_write flags are true. data.no_spend_evaluation.stop_here must be true, data.no_spend_evaluation.next_command_is_live_create must be true, and data.no_spend_evaluation.recommended_command_field must be recommended_no_spend_command. Run data.next_command only when media spend is allowed. In no-spend evaluations, or when you only need to prove readiness without media/provider work, stop before data.next_command and run data.recommended_no_spend_command instead. data.recommended_no_spend_command must equal data.no_spend_next_command. data.no_spend_next_command_effect.label must be dry_run_planned_job_no_provider_call_no_credit_debit_no_media_write: no_spend, hosted_create_dry_run, planned_job, and plan_receipt are true; activity_event is job.planned; provider_call, credit_debit, and media_write are false. This dry-run may create a recoverable planned job/activity receipt but no provider execution, debit, downloadable asset, or media write. If the guide authenticated from env or stdin, prefer data.auth_handoff.next_command.with_env or data.auth_handoff.next_command.with_stdin so auth follows the live create. In guide cost output, cost.estimated_usd_per_image and cost.estimated_debit_usd_per_image are the Luxin debit dollars for one output; cost.estimated_provider_usd_per_image is only the upstream provider estimate. Use the guide's returned max_estimated_usd_per_image because it is sized to the credit debit the agent funds. Add --output-count N only after models show confirms the selected create model supports more than one output; credit_pricing.credits_required is the total debit across outputs, while max_estimated_usd_per_image remains a per-image Luxin debit guard.
 7. After create, prefer data.next_actions when present: inspect_job and inspect_asset are copy-runnable no-spend recovery commands, iterate_edit is the reusable-asset edit template, and self_fund is the promoted top-up quote handoff when quota.top_up.available is true. self_fund.recommended plus urgency, urgency_score, and urgency_reasons say whether to act now, and self_fund exposes first_safe_command plus first_safe_command_effect for no-spend rail inspection before quote/buy. When self_fund.recommended is true and the quote is copy-runnable, data.self_fund_next_command aliases data.next_actions.self_fund.quote_command and data.self_fund_next_command_effect proves the quote creates no provider call, hosted create, credit debit, media write, or wallet settlement. self_fund.quote_command is copy-runnable and omits --idempotency-key so the public CLI generates and returns one for retry safety; follow the quote response into buy/status. Otherwise use luxin jobs show JOB_ID to recover status, cost, safety, timestamps, and final assets; luxin assets get ASSET_URL_OR_ID --output ./result.png to fetch the generated asset without repeating provider work; and luxin activity list --subject JOB_ID to find ledger events, trace, usage, asset links, and any data.next_actions.self_fund handoff to cite or follow. Hosted asset-id assets show/get may also return data.next_actions.self_fund after generated work, so inspect that field before ending the session.
+7a. Human handoff. When a create or edit produced a real asset, data.next_actions.share_with_human offers the no-spend, copy-runnable command luxin claim code --json with share_field data.dashboard_url. Run it and give your human the returned data.dashboard_url: they get a read-only view of your jobs, assets, quota, and activity plus the ability to open a credit checkout for you. The link itself is the credential: your human signs in with nothing — no email, no password, no provider billing setup. Hand over data.dashboard_url only — never your token, and never the raw data.code, which is the whole credential; the code rides in the URL fragment (#code=...), which browsers never send to a server, so share the link intact instead of rebuilding it as a query string. The code is single-use and expires (data.ttl_seconds, currently 15 minutes) while the human session it opens lasts days, so one code is normally enough; reuse an unexpired dashboard_url rather than re-minting, since minting is capped at 30 codes per agent per hour (DASHBOARD_CODE_RATE_LIMITED past that). Redeeming a new link ends whatever dashboard session was already open for you, so one human holds the view at a time; do not hand out a second link expecting both to keep working. luxin claim code needs the dashboard.claim grant that luxin signup --agent tokens carry, and it spends nothing: no provider call, no credit debit, no payment object, no media write. Dry runs never carry the handoff because there is nothing finished to show.
 8. Leave luxin feedback create if the first-run flow is confusing, blocked, missing an affordance, or easier through a direct provider than through Luxin. Feedback auth uses saved config from default signup, IMAGE_SKILL_TOKEN, or --token-stdin; if signup or guide already saved config, run feedback create normally and do not copy a raw token. Never paste tokens into feedback title, body, evidence, issues, or logs. Use luxin activity show FEEDBACK_ID only when you need to confirm the feedback entered the hosted ledger.
 
 Manual escape hatches are not prerequisites. Use luxin doctor, luxin models list, luxin models show MODEL_ID, luxin whoami, luxin usage quota, luxin credits methods, luxin credits packs list, luxin credits quote, luxin credits buy, luxin credits status, luxin create --dry-run, and luxin edit --dry-run only when data.next_command or data.escape_hatches asks for them, or when the task genuinely needs deeper capability, quota, payment, or planning detail.
@@ -74,6 +75,7 @@ Core commands:
 - luxin doctor --json
 - luxin signup --agent --agent-name NAME --runtime RUNTIME --json
 - luxin claim request --contact AGENT_OR_OPERATOR_INBOX --json
+- luxin claim code --json
 - luxin whoami --json
 - luxin usage quota --json
 - luxin quota --json (compatibility alias)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luxin-cli",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Zero-setup durable creative-media CLI for agents (image + video + audio + 3D): guide-first creation, model and cost inspection, owned URLs, JSON recovery, payments, reusable assets, and feedback. Luxin is a creative-media runtime, unrelated to the luxon datetime library.",
   "type": "module",
   "private": false,

package/skill.md

@@ -228,6 +228,20 @@ receipts to Luxin.
 
 Do not silently downgrade to the cheapest model to avoid payment when the user asked for quality or is willing to pay. Quote the needed credits and use the rail above.
 
+## Show your human
+
+When you have real work to show and need it funded, hand your human a dashboard link:
+
+```bash
+luxin claim code --json
+```
+
+Give them `data.dashboard_url` and nothing else. They get a read-only view of your jobs, assets, quota, and activity, plus the ability to open a credit checkout for you. The link itself is the credential: your human signs in with nothing — no email, no password, no provider billing setup. Never share your token, and never quote the raw `data.code` in prompts, logs, issues, or feedback: the code is the whole credential. It rides in the URL fragment (`#code=...`), which browsers never send to a server, so share the link intact rather than rebuilding it as a query string.
+
+The code is single-use and expires (`data.ttl_seconds`, currently 15 minutes); the human session it opens lasts days. So one code is normally enough — reuse an unexpired `dashboard_url` instead of re-minting, and expect `DASHBOARD_CODE_RATE_LIMITED` past 30 codes per agent per hour. Redeeming a new link ends whatever dashboard session was already open for you, so one human holds the view at a time; do not hand out a second link expecting both to keep working. `claim code` needs the `dashboard.claim` grant that `luxin signup --agent` tokens carry, and it spends nothing: no provider call, no credit debit, no payment object, no media write.
+
+Best moment: right after a create or edit produced real media, where the success envelope already carries `data.next_actions.share_with_human` with this command and `share_field: "data.dashboard_url"`. A human who can see finished work is a human who will fund the next run. Dry runs never carry the handoff, because there is nothing finished to show.
+
 ## Models and capability-preserving parameters
 
 `models show MODEL_ID` is the first detailed discovery surface for agents. It exposes operations, media inputs and outputs, model-parameter schemas, fixed and wired controls, cost class, safety behavior, and migration hints. Treat its output as the source of truth for what a model supports. Do not infer one model's parameter surface from another model.
@@ -293,7 +307,9 @@ luxin activity show EVENT_OR_JOB_OR_ASSET_OR_FEEDBACK
 
 After a successful hosted create/edit, prefer `data.next_actions` when present:
 `inspect_job` and `inspect_asset` are no-spend recovery commands,
-`iterate_edit` reuses the asset, and `self_fund` promotes a copy-runnable
+`iterate_edit` reuses the asset, `share_with_human` is the no-spend
+`luxin claim code --json` dashboard handoff (see "Show your human"), and
+`self_fund` promotes a copy-runnable
 top-up quote command when `quota.top_up.available` is true. Its `recommended`
 flag and mirrored top-up `urgency`, `urgency_score`, and `urgency_reasons` say
 whether the agent should act now, while `first_safe_command` plus

package/skills/luxin/SKILL.md

@@ -228,6 +228,20 @@ receipts to Luxin.
 
 Do not silently downgrade to the cheapest model to avoid payment when the user asked for quality or is willing to pay. Quote the needed credits and use the rail above.
 
+## Show your human
+
+When you have real work to show and need it funded, hand your human a dashboard link:
+
+```bash
+luxin claim code --json
+```
+
+Give them `data.dashboard_url` and nothing else. They get a read-only view of your jobs, assets, quota, and activity, plus the ability to open a credit checkout for you. The link itself is the credential: your human signs in with nothing — no email, no password, no provider billing setup. Never share your token, and never quote the raw `data.code` in prompts, logs, issues, or feedback: the code is the whole credential. It rides in the URL fragment (`#code=...`), which browsers never send to a server, so share the link intact rather than rebuilding it as a query string.
+
+The code is single-use and expires (`data.ttl_seconds`, currently 15 minutes); the human session it opens lasts days. So one code is normally enough — reuse an unexpired `dashboard_url` instead of re-minting, and expect `DASHBOARD_CODE_RATE_LIMITED` past 30 codes per agent per hour. Redeeming a new link ends whatever dashboard session was already open for you, so one human holds the view at a time; do not hand out a second link expecting both to keep working. `claim code` needs the `dashboard.claim` grant that `luxin signup --agent` tokens carry, and it spends nothing: no provider call, no credit debit, no payment object, no media write.
+
+Best moment: right after a create or edit produced real media, where the success envelope already carries `data.next_actions.share_with_human` with this command and `share_field: "data.dashboard_url"`. A human who can see finished work is a human who will fund the next run. Dry runs never carry the handoff, because there is nothing finished to show.
+
 ## Models and capability-preserving parameters
 
 `models show MODEL_ID` is the first detailed discovery surface for agents. It exposes operations, media inputs and outputs, model-parameter schemas, fixed and wired controls, cost class, safety behavior, and migration hints. Treat its output as the source of truth for what a model supports. Do not infer one model's parameter surface from another model.
@@ -293,7 +307,9 @@ luxin activity show EVENT_OR_JOB_OR_ASSET_OR_FEEDBACK
 
 After a successful hosted create/edit, prefer `data.next_actions` when present:
 `inspect_job` and `inspect_asset` are no-spend recovery commands,
-`iterate_edit` reuses the asset, and `self_fund` promotes a copy-runnable
+`iterate_edit` reuses the asset, `share_with_human` is the no-spend
+`luxin claim code --json` dashboard handoff (see "Show your human"), and
+`self_fund` promotes a copy-runnable
 top-up quote command when `quota.top_up.available` is true. Its `recommended`
 flag and mirrored top-up `urgency`, `urgency_score`, and `urgency_reasons` say
 whether the agent should act now, while `first_safe_command` plus

package/skills/luxin/references/cli.md

@@ -175,6 +175,68 @@ printf '%s\n' "$IMAGE_SKILL_TOKEN" | luxin usage quota --token-stdin --json
 `--api-base-url` is an advanced preview/test override; production public agents
 should omit it.
 
+### `luxin claim code`
+
+Mints a single-use, short-lived dashboard link for the authenticated agent's
+human. This is the human handoff: give `data.dashboard_url` to your human and
+they can watch your work and fund your credits there. The link itself is the
+credential: your human signs in with nothing — no email, no password, no
+provider billing setup.
+
+```bash
+luxin claim code --json
+```
+
+```json
+{
+  "ok": true,
+  "command": "luxin claim code",
+  "data": {
+    "mode": "hosted_auth",
+    "agent_id": "agt_...",
+    "code": "dc_...",
+    "dashboard_url": "https://luxin.sh/dashboard#code=dc_...",
+    "expires_at": "2026-07-30T18:15:00.000Z",
+    "ttl_seconds": 900,
+    "single_use": true,
+    "human_handoff": {
+      "purpose": "hand_dashboard_link_to_human",
+      "audience": "human",
+      "share_field": "data.dashboard_url",
+      "message": "give dashboard_url to your human: they can watch your work and fund your credits there. Send the link only — never your token, and never the raw code.",
+      "never_share": ["token", "code"]
+    }
+  }
+}
+```
+
+Hand over `data.dashboard_url` and nothing else. Never hand over your token,
+and never quote the raw `data.code` in prompts, logs, issue text, or feedback:
+the code is the whole credential. The code travels in the URL fragment
+(`#code=...`), which browsers never send to a server, so it stays out of server
+logs and analytics — keep it that way by sharing the link intact rather than
+rebuilding it as a query string.
+
+The code is single-use and expires (`data.ttl_seconds`, currently 15 minutes).
+The dashboard is read-only over your work — jobs, assets, quota, activity — plus
+the ability to open a credit checkout for you. It cannot create, edit, upload,
+or spend as you. Once your human has opened the link their session lasts days,
+so one code is normally all that is needed; mint a fresh one when the link
+expires unused. Redeeming a new link ends whatever dashboard session was
+already open for you, so one human holds the view at a time — do not hand out
+a second link expecting both to keep working. Minting is capped at 30 codes per
+agent per hour and answers `DASHBOARD_CODE_RATE_LIMITED` past that — reuse an
+unexpired `dashboard_url` instead of re-minting per message.
+
+`claim code` requires the `dashboard.claim` grant, which restricted tokens
+minted by `luxin signup --agent` carry. It never spends: no provider call, no
+credit debit, no payment object, no media write.
+
+Best moment to run it: right after a create or edit produced real media. That
+success envelope carries `data.next_actions.share_with_human` with this exact
+command, because a human who can see finished work is a human who will fund the
+next run.
+
 ### First Run Guide Loop
 
 Use the no-spend guide first. It is the only required first command for a fresh
@@ -1642,6 +1704,13 @@ The quote command omits `--idempotency-key` so the public CLI generates and
 returns one for retry safety before the agent follows the quote response into
 `credits buy` and `credits status`.
 
+When a create or edit produced a real durable asset, the same envelope carries
+`data.next_actions.share_with_human`: a no-spend, copy-runnable
+`luxin claim code --json` plus `share_field: "data.dashboard_url"`. Run it and
+hand your human the resulting `dashboard_url` — they can watch this work and
+fund your credits from it. Dry runs never carry it, because there is nothing
+finished to show.
+
 Provider/model names in this paragraph are preview provenance, not the primary
 public UX. The public selection surface should be Luxin capabilities and
 model-parameter schemas; provider/model details belong in explicit

package/skills/luxin/references/commands.json

@@ -33,7 +33,7 @@
       "surface": "hosted_cli",
       "mutation": true,
       "spend": false,
-      "subcommands": ["request"]
+      "subcommands": ["request", "code"]
     },
     {
       "id": "whoami",
@@ -166,6 +166,7 @@
           "trust",
           "signup --agent --agent-name NAME --runtime RUNTIME",
           "claim request --contact INBOX",
+          "claim code",
           "whoami",
           "usage quota",
           "quota",
@@ -238,9 +239,9 @@
       "key": "claim",
       "help": {
         "command": "luxin claim help",
-        "usage": "luxin claim request --contact AGENT_OR_OPERATOR_INBOX --json",
+        "usage": "luxin claim <request|code> --json",
         "docs_url": "https://luxin.sh/cli.md#luxin-claim-request",
-        "subcommands": ["request"]
+        "subcommands": ["request", "code"]
       }
     },
     {
@@ -253,6 +254,16 @@
         "optional_flags": ["--token-stdin"]
       }
     },
+    {
+      "key": "claim code",
+      "help": {
+        "command": "luxin claim code help",
+        "usage": "luxin claim code --json",
+        "docs_url": "https://luxin.sh/cli.md#luxin-claim-code",
+        "description": "Mint a single-use, short-lived dashboard link and hand data.dashboard_url to your human: they can watch your work and fund your credits there. No inputs beyond auth; no spend.",
+        "optional_flags": ["--token-stdin"]
+      }
+    },
     {
       "key": "whoami",
       "help": {

package/skills/luxin/references/llms.txt

@@ -66,6 +66,7 @@ First-run guide loop:
 5a. When data.stage is quota_required, data.self_fund_handoff mirrors top-up urgency, urgency_score, and urgency_reasons, and exposes first_safe_command plus first_safe_command_effect. Run first_safe_command, usually luxin credits methods --json, for no-spend rail inspection before quote/buy when delegated spend authority is absent or unclear.
 6. If data.stage is ready_to_create, data.next_command is the first bounded live create. data.guide_warning.next_command_safety must be live_media_create_credit_debit, data.guide_warning.no_spend_safe must be false, data.guide_warning.spend_required must be true, and data.guide_warning.recommended_command_field must be recommended_no_spend_command. data.auth_ready.ready and data.auth_ready.next_command_auth_ready must be true; data.auth_ready.next_command_requires_auth must be true, and the command can reuse saved config, IMAGE_SKILL_TOKEN, or --token-stdin context without exposing a raw token. data.next_command_effect.label must be live_media_create_credit_debit and its provider_call, hosted_create, credit_debit, and media_write flags are true. data.no_spend_evaluation.stop_here must be true, data.no_spend_evaluation.next_command_is_live_create must be true, and data.no_spend_evaluation.recommended_command_field must be recommended_no_spend_command. Run data.next_command only when media spend is allowed. In no-spend evaluations, or when you only need to prove readiness without media/provider work, stop before data.next_command and run data.recommended_no_spend_command instead. data.recommended_no_spend_command must equal data.no_spend_next_command. data.no_spend_next_command_effect.label must be dry_run_planned_job_no_provider_call_no_credit_debit_no_media_write: no_spend, hosted_create_dry_run, planned_job, and plan_receipt are true; activity_event is job.planned; provider_call, credit_debit, and media_write are false. This dry-run may create a recoverable planned job/activity receipt but no provider execution, debit, downloadable asset, or media write. If the guide authenticated from env or stdin, prefer data.auth_handoff.next_command.with_env or data.auth_handoff.next_command.with_stdin so auth follows the live create. In guide cost output, cost.estimated_usd_per_image and cost.estimated_debit_usd_per_image are the Luxin debit dollars for one output; cost.estimated_provider_usd_per_image is only the upstream provider estimate. Use the guide's returned max_estimated_usd_per_image because it is sized to the credit debit the agent funds. Add --output-count N only after models show confirms the selected create model supports more than one output; credit_pricing.credits_required is the total debit across outputs, while max_estimated_usd_per_image remains a per-image Luxin debit guard.
 7. After create, prefer data.next_actions when present: inspect_job and inspect_asset are copy-runnable no-spend recovery commands, iterate_edit is the reusable-asset edit template, and self_fund is the promoted top-up quote handoff when quota.top_up.available is true. self_fund.recommended plus urgency, urgency_score, and urgency_reasons say whether to act now, and self_fund exposes first_safe_command plus first_safe_command_effect for no-spend rail inspection before quote/buy. When self_fund.recommended is true and the quote is copy-runnable, data.self_fund_next_command aliases data.next_actions.self_fund.quote_command and data.self_fund_next_command_effect proves the quote creates no provider call, hosted create, credit debit, media write, or wallet settlement. self_fund.quote_command is copy-runnable and omits --idempotency-key so the public CLI generates and returns one for retry safety; follow the quote response into buy/status. Otherwise use luxin jobs show JOB_ID to recover status, cost, safety, timestamps, and final assets; luxin assets get ASSET_URL_OR_ID --output ./result.png to fetch the generated asset without repeating provider work; and luxin activity list --subject JOB_ID to find ledger events, trace, usage, asset links, and any data.next_actions.self_fund handoff to cite or follow. Hosted asset-id assets show/get may also return data.next_actions.self_fund after generated work, so inspect that field before ending the session.
+7a. Human handoff. When a create or edit produced a real asset, data.next_actions.share_with_human offers the no-spend, copy-runnable command luxin claim code --json with share_field data.dashboard_url. Run it and give your human the returned data.dashboard_url: they get a read-only view of your jobs, assets, quota, and activity plus the ability to open a credit checkout for you. The link itself is the credential: your human signs in with nothing — no email, no password, no provider billing setup. Hand over data.dashboard_url only — never your token, and never the raw data.code, which is the whole credential; the code rides in the URL fragment (#code=...), which browsers never send to a server, so share the link intact instead of rebuilding it as a query string. The code is single-use and expires (data.ttl_seconds, currently 15 minutes) while the human session it opens lasts days, so one code is normally enough; reuse an unexpired dashboard_url rather than re-minting, since minting is capped at 30 codes per agent per hour (DASHBOARD_CODE_RATE_LIMITED past that). Redeeming a new link ends whatever dashboard session was already open for you, so one human holds the view at a time; do not hand out a second link expecting both to keep working. luxin claim code needs the dashboard.claim grant that luxin signup --agent tokens carry, and it spends nothing: no provider call, no credit debit, no payment object, no media write. Dry runs never carry the handoff because there is nothing finished to show.
 8. Leave luxin feedback create if the first-run flow is confusing, blocked, missing an affordance, or easier through a direct provider than through Luxin. Feedback auth uses saved config from default signup, IMAGE_SKILL_TOKEN, or --token-stdin; if signup or guide already saved config, run feedback create normally and do not copy a raw token. Never paste tokens into feedback title, body, evidence, issues, or logs. Use luxin activity show FEEDBACK_ID only when you need to confirm the feedback entered the hosted ledger.
 
 Manual escape hatches are not prerequisites. Use luxin doctor, luxin models list, luxin models show MODEL_ID, luxin whoami, luxin usage quota, luxin credits methods, luxin credits packs list, luxin credits quote, luxin credits buy, luxin credits status, luxin create --dry-run, and luxin edit --dry-run only when data.next_command or data.escape_hatches asks for them, or when the task genuinely needs deeper capability, quota, payment, or planning detail.
@@ -74,6 +75,7 @@ Core commands:
 - luxin doctor --json
 - luxin signup --agent --agent-name NAME --runtime RUNTIME --json
 - luxin claim request --contact AGENT_OR_OPERATOR_INBOX --json
+- luxin claim code --json
 - luxin whoami --json
 - luxin usage quota --json
 - luxin quota --json (compatibility alias)