• v0.1.7 4c631a3903

    v0.1.7 — Short consent link
    All checks were successful
    CI / check (push) Successful in 44s
    Release notes / release (push) Successful in 36s
    Publish package / publish (push) Successful in 1m8s
    Publish to npmjs / publish (push) Successful in 1m11s
    Stable

    dsh released this 2026-11-12 18:26:26 +00:00 | 0 commits to master since this release

    Signed by dsh
    GPG key ID: A2B50C83F46BE316
    • The Drive consent card and the pending result now render a single short
      Markdown link, Colab Drive Auth, instead of also printing the raw
      URL (the Markdown target is still the full URL; it is just not displayed as
      text). The pending result no longer appends the JSON envelope.
    • A successful mount no longer returns data.url.
    • This is a Markdown link ([text](url)), rendered by the Web UI as an anchor;
      no <a href> markup is needed.

    Install

    dsh plugin --profile web add --registry https://git.pvlb.dev/api/packages/dsh-plugins/npm/ dsh-colab@0.1.7
    

    Forge registry: https://git.pvlb.dev/dsh-plugins/dsh-colab
    npm: https://www.npmjs.com/package/dsh-colab

    Downloads
  • v0.1.6 b120a2ecf3

    v0.1.6 — Consent question before Enter
    All checks were successful
    CI / check (push) Successful in 49s
    Publish package / publish (push) Successful in 46s
    Release notes / release (push) Successful in 18s
    Publish to npmjs / publish (push) Successful in 1m13s
    Stable

    dsh released this 2026-11-12 17:11:37 +00:00 | 2 commits to master since this release

    Signed by dsh
    GPG key ID: A2B50C83F46BE316
    • colab_drive_auth now asks a blocking Next/Cancel question while the CLI
      waits at its Enter prompt. The clickable link lives in the question's
      Markdown detail (the title is plain text); Enter is sent only after Next.
      Cancel terminates the child and returns auth_pending with the URL. This
      fixes the 400 from auto-propagating credentials before the operator consented.
    • colab_run forwards the calling agent, so the same question works inside a
      recipe.
    • Verified with a real CPU session on srvbtw: fresh session, real
      colab_drive_auth mounted /content/drive (attempts: 1, verified), a real
      colab_ls listed MyDrive, and the session was stopped. The account consent
      was already on file, so that mount did not need a prompt; the Next/Cancel card
      path was exercised in the Web UI against the fake CLI backend.

    Install

    dsh plugin --profile web add --registry https://git.pvlb.dev/api/packages/dsh-plugins/npm/ dsh-colab@0.1.6
    

    Forge registry: https://git.pvlb.dev/dsh-plugins/dsh-colab
    npm: https://www.npmjs.com/package/dsh-colab

    Downloads
  • v0.1.5 1e80cd0726

    v0.1.5 — Pending consent is a link, not buried JSON
    All checks were successful
    CI / check (push) Successful in 51s
    Release notes / release (push) Successful in 47s
    Publish to npmjs / publish (push) Successful in 1m11s
    Publish package / publish (push) Successful in 1m14s
    Stable

    dsh released this 2026-11-12 13:47:42 +00:00 | 5 commits to master since this release

    Signed by dsh
    GPG key ID: A2B50C83F46BE316
    • colab_drive_auth and colab_run render an auth_pending result with a
      clickable [Approve Google Drive access](…) link plus the bare URL, because a
      web-hosted DSH cannot open a tab in a remote operator's browser. Other results
      keep the JSON envelope.
    • A system-prompt section tells the agent to present that link and retry the
      tool, never to describe the pending consent as a timeout.
    • driveOpenBrowser still tries a host-side opener; data.browser.reason
      explains no-display/not-installed when it cannot.

    Install

    dsh plugin --profile web add --registry https://git.pvlb.dev/api/packages/dsh-plugins/npm/ dsh-colab@0.1.5
    

    Forge registry: https://git.pvlb.dev/dsh-plugins/dsh-colab
    npm: https://www.npmjs.com/package/dsh-colab

    Downloads
  • v0.1.4 03718e45de

    v0.1.4 — Drive consent UX
    All checks were successful
    CI / check (push) Successful in 46s
    Release notes / release (push) Successful in 1m7s
    Publish package / publish (push) Successful in 1m55s
    Publish to npmjs / publish (push) Successful in 2m4s
    Stable

    dsh released this 2026-11-12 10:43:43 +00:00 | 7 commits to master since this release

    Signed by dsh
    GPG key ID: A2B50C83F46BE316
    • colab_drive_auth now returns auth_pending with the consent URL after the
      first attempt that needs approval instead of waiting out timeout_s in
      silence. Pass wait_for_consent: true for the old one-call retry loop.
    • Best-effort browser launch on the DSH host (xdg-open/open); the result
      reports data.browser: {opened, reason} so a headless host is diagnosable.
      Disable with driveOpenBrowser: false.
    • The consent URL is recovered from colab log events when the CLI output does
      not show it, and data.last_tail carries the redacted automation tail.
    • Docs: CLI 0.7.5 never opens the consent page (it only prints the URL); 0.8.0
      does, but stores its token in the OS keyring, so headless hosts need a keyring
      backend or --auth adc.

    Install

    dsh plugin --profile web add --registry https://git.pvlb.dev/api/packages/dsh-plugins/npm/ dsh-colab@0.1.4
    

    Forge registry: https://git.pvlb.dev/dsh-plugins/dsh-colab
    npm: https://www.npmjs.com/package/dsh-colab

    Downloads
  • v0.1.3 9ce6715106

    v0.1.3 — Real-VM timeout fixes
    All checks were successful
    CI / check (push) Successful in 40s
    Release notes / release (push) Successful in 30s
    Publish package / publish (push) Successful in 45s
    Publish to npmjs / publish (push) Successful in 48s
    Stable

    dsh released this 2026-11-11 22:54:56 +00:00 | 9 commits to master since this release

    Signed by dsh
    GPG key ID: A2B50C83F46BE316
    • colab_drive_auth no longer polls colab ls while the drivemount
      automation holds the kernel. It waits for the automation to exit, then
      verifies the mount; the old 5 s listing budget turned a busy kernel into a
      spurious cli_timeout on a fresh VM (#10).
    • Listings use a configurable listTimeoutMs (default 60 s) instead of a
      hardcoded 5 s, and transfers keep using commandTimeoutMs (default 180 s).
      A CLI timeout during upload/download now returns transfer_failed with a
      clear hint instead of a bare cli_timeout (#11).
    • Regression tests: a slow drivemount automation plus a blocking ls, a 6 s
      upload verification, and a timed-out transfer mapping.

    Install

    dsh plugin --profile web add --registry https://git.pvlb.dev/api/packages/dsh-plugins/npm/ dsh-colab@0.1.3
    

    Forge registry: https://git.pvlb.dev/dsh-plugins/dsh-colab
    npm: https://www.npmjs.com/package/dsh-colab

    Downloads
  • v0.1.2 79419e23e7

    v0.1.2 — Forgejo registry via authorized integration
    All checks were successful
    CI / check (push) Successful in 29s
    Release notes / release (push) Successful in 28s
    Publish to npmjs / publish (push) Successful in 41s
    Publish package / publish (push) Successful in 44s
    Stable

    dsh released this 2026-11-11 21:53:39 +00:00 | 12 commits to master since this release

    Signed by dsh
    GPG key ID: A2B50C83F46BE316
    • publish.yml now uses the forge's authorized integration: it enables OIDC,
      exchanges the runner token for a short-lived JWT with the audience from the
      AUDIENCE repository variable, and authenticates the npm publish with it
      (basic, bearer retry; masked in the log). NPM_TOKEN remains a fallback.
    • The manual trigger verifies the token path and runs npm pack --dry-run
      without uploading.
    • Context: the v0.1.1 registry job failed because the automatic Actions token is
      not accepted by npm registry auth (401); the release page and npmjs stage were
      unaffected.

    Install

    dsh plugin --profile web add dsh-colab@0.1.2
    

    Forge registry: https://git.pvlb.dev/dsh-plugins/dsh-colab
    npm: https://www.npmjs.com/package/dsh-colab

    Downloads
  • v0.1.1 922db80afd

    v0.1.1 — Forgejo publish auth
    Some checks failed
    CI / check (push) Successful in 35s
    Release notes / release (push) Successful in 25s
    Publish package / publish (push) Failing after 44s
    Publish to npmjs / publish (push) Successful in 48s
    Stable

    dsh released this 2026-11-11 21:42:44 +00:00 | 17 commits to master since this release

    Signed by dsh
    GPG key ID: A2B50C83F46BE316
    • publish.yml now authenticates the pvlb.dev npm registry with the runner's
      authorized integration (the automatic Actions token) and keeps NPM_TOKEN as
      an optional override. The v0.1.0 registry job failed because that secret was
      empty; the release page and the npmjs stage from v0.1.0 are unaffected.

    Install

    dsh plugin --profile web add dsh-colab@0.1.1
    

    Forge registry: https://git.pvlb.dev/dsh-plugins/dsh-colab
    npm: https://www.npmjs.com/package/dsh-colab

    Downloads
  • v0.1.0 6014665e6a

    v0.1.0 — First working plugin
    Some checks failed
    CI / check (push) Successful in 39s
    Release notes / release (push) Successful in 17s
    Publish package / publish (push) Failing after 42s
    Publish to npmjs / publish (push) Successful in 46s
    Stable

    dsh released this 2026-11-11 21:39:12 +00:00 | 19 commits to master since this release

    Signed by dsh
    GPG key ID: A2B50C83F46BE316
    • CLI wrapper over google-colab-cli 0.7.5–0.8.x: typed errors, bounded output,
      secret redaction, wall-clock and idle timeouts, detached child so the Drive
      prompt reads our stdin instead of a terminal.
    • Session lifecycle: colab_session_new, colab_sessions,
      colab_session_status, colab_session_stop (explicit, idempotent),
      colab_session_restart, colab_usage, colab_log.
    • Drive handoff: colab_drive_auth surfaces the consent URL, presses Enter,
      retries until the mount exists, and never wedges a child.
    • Transfer: colab_upload, colab_download, colab_ls with bounded retries and
      post-verification.
    • Recipe: colab_run (session → Drive → bundle → setup → attached exec →
      artifact invariant → downloads → stop), guaranteed cleanup on every path.
    • Diagnostics: colab_plugin_info.
    • Optional beta Colab API MCP adapter: colab_mcp_status, colab_mcp_refresh,
      dynamic mcp__colab__* tools, bearer/command token modes.
    • Offline fake-CLI test harness; opt-in live smoke script.
    • CI/CD: the house four-workflow release layout (ci, Forgejo publish, staged
      npmjs publish, release notes) plus a tested scripts/release-notes.mjs.

    Install

    dsh plugin --profile web add dsh-colab@0.1.0
    

    Forge registry: https://git.pvlb.dev/dsh-plugins/dsh-colab
    npm: https://www.npmjs.com/package/dsh-colab

    Downloads