privateer-agent 0.3.2 → 0.3.3

package/README.md

@@ -12,6 +12,9 @@
   <a href="https://www.npmjs.com/package/privateer-agent">
     <img src="https://img.shields.io/npm/v/privateer-agent" alt="npm" />
   </a>
+  <a href="https://github.com/privateer-agent/privateer-agent/releases">
+    <img src="https://img.shields.io/badge/changelog-what's%20new-5b8def" alt="Changelog" />
+  </a>
   <img src="https://img.shields.io/badge/node-%E2%89%A522.19-brightgreen" alt="Node >= 22.19" />
   <img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License" />
   <img src="https://img.shields.io/badge/permissions-safe%20by%20default-2ea44f" alt="Safe by default" />
@@ -247,6 +250,12 @@ npm run typecheck
 npm test
 ```
 
+## Changelog
+
+Release notes and what's new in each version live on the
+[**GitHub releases page**](https://github.com/privateer-agent/privateer-agent/releases).
+Privateer keeps its startup clean — the app won't dump a changelog into your terminal.
+
 ## License
 
 [MIT](LICENSE) © Patrick

package/bin/privateer-tui

@@ -59,15 +59,27 @@ shim pi-subagents      "$REPO/node_modules/pi-subagents/src/extension/index.ts"
 
 CLI="$REPO/node_modules/@earendil-works/pi-coding-agent/dist/cli.js"
 export PI_CODING_AGENT_DIR="$AGENT_DIR"
+# Suppress Pi's upstream "Update Available — run `pi update`" banner. It's noise on a
+# Privateer install (our banner is the startup surface), it leaks the "pi" name, and
+# `pi update` would fight our npm-managed install. PI_SKIP_VERSION_CHECK disables ONLY
+# the version fetch — unlike PI_OFFLINE it still lets fd/rg download on first run.
+export PI_SKIP_VERSION_CHECK=1
 NODE_BIN="$(pick_node)"
 
-# Quiet Pi's built-in startup resource listing ([Extensions]/[Context]/[Skills]/…) by
-# default — our banner is the intended startup surface, and the extension list is noise.
-# Only set it when unset, so a later `--verbose` or a user's own settings toggle sticks.
+# Quiet Pi's built-in startup chatter so our banner is the only greeting. Each key is
+# set only when unset, so a user's own settings.json toggle (or --verbose) still wins:
+#   quietStartup       — hide the [Extensions]/[Context]/[Skills]/… resource listing
+#   collapseChangelog  — never dump Pi's "What's New" changelog wall into the chat
+#   lastChangelogVersion — sentinel so Pi finds no "new" entries to show on upgrade;
+#                          release notes live in the npm README / GitHub releases instead
 "$NODE_BIN" -e '
 const fs = require("fs"), p = process.argv[1];
 let s = {}; try { s = JSON.parse(fs.readFileSync(p, "utf8")); } catch {}
-if (s.quietStartup === undefined) { s.quietStartup = true; fs.writeFileSync(p, JSON.stringify(s, null, 2) + "\n"); }
+let m = false;
+if (s.quietStartup === undefined) { s.quietStartup = true; m = true; }
+if (s.collapseChangelog === undefined) { s.collapseChangelog = true; m = true; }
+if (s.lastChangelogVersion === undefined) { s.lastChangelogVersion = "9999.0.0"; m = true; }
+if (m) fs.writeFileSync(p, JSON.stringify(s, null, 2) + "\n");
 ' "$AGENT_DIR/settings.json" 2>/dev/null || true
 
 # Default model: when signed in to a Privateer account, default to GLM 5.1 on the

package/extensions/privateer-brand.ts

@@ -9,12 +9,15 @@
 //      device-code flow the account channel needs.
 //
 // Pi already owns /login and /logout for PROVIDER auth (and /whoami), so we do NOT
-// shadow them. /signin drives the Privateer *account* device flow directly — which
-// has to exist separately, because the `privateer` inference provider only registers
-// once credentials exist, so a first-time user can't reach it through provider auth.
+// shadow them. The account provider now registers unconditionally (see
+// makeAccountProvider), so Privateer appears under Pi's /login "Use a subscription"
+// list and a first-time user CAN sign in through provider auth. /signin remains as a
+// friendlier, dedicated shortcut that drives the same account device-code flow
+// directly — one obvious command instead of /login → pick a provider.
 //
 // On a successful /signin we hot-register the account provider so privateer/* models
-// appear immediately, without a restart.
+// appear immediately (the account catalog refreshes to the live listing without a
+// restart).
 
 import { readFileSync } from "node:fs";
 import { homedir } from "node:os";
@@ -54,7 +57,7 @@ const ANCHOR = [
   "  .-----.  ", // lock body top (the shackle's base)
   "  |  o  |  ", // lock body + keyhole
   "  '--+--'  ", // lock body base, shank exits
-  "  ---+---  ", // stock (crossbar)
+  "  /\\ | /\\  ", // stock — arms flare from the shank (each \\ is one backslash)
   "  \\  |  /  ", // arms
   "   \\_|_/   ", // flukes
 ];
@@ -150,7 +153,6 @@ function accountBadge(): string {
 export default function privateerBrand(pi: any): void {
   let currentModelProvider: string | undefined;
   let ctxRef: any = null;
-  let greeted = false;
 
   const setHeader = (ctx: any) =>
     ctx?.ui?.setHeader?.(() => headerComponent(currentModelProvider));
@@ -227,13 +229,8 @@ export default function privateerBrand(pi: any): void {
     if (!ctx?.hasUI) return; // headless (print/json): no banner or prompts
     ctx?.ui?.setTitle?.("Privateer");
     refresh(ctx);
-    if (!priv.hasCredentials() && !greeted) {
-      greeted = true;
-      ctx?.ui?.notify?.(
-        "Not signed in — run /signin to connect your Privateer account (adds hosted models + remote access).",
-        "info",
-      );
-    }
+    // No startup notify here: the banner's account line already surfaces the
+    // "not signed in · /signin" prompt, so a second line would just be noise.
   });
 
   // Keep the header's account line in sync with the picked model (the "this model

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "privateer-agent",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Privateer — a provider-agnostic, safe-by-default terminal coding agent with TEE/Tinfoil attestation, rebuilt on the Pi toolkit. Bring your own model across 20 providers.",
   "type": "module",
   "license": "MIT",

package/src/providers/account.ts

@@ -136,8 +136,16 @@ export async function accountPosture(modelId: string): Promise<AccountPosture> {
   }
 }
 
-// Extension factory: registers the account provider when a machine login exists. No
-// login → nothing registered (BYO-key only).
+// Extension factory: registers the account provider so `/login` can offer it.
+//
+// We register UNCONDITIONALLY (not only when a machine login already exists). Pi's
+// `/login` builds its "Use a subscription" list from the OAuth providers registered
+// here (authStorage.getOAuthProviders()); a not-yet-logged-in machine has no
+// credentials, so gating registration on hasCredentials() left `/login` with no
+// Privateer option — the classic chicken-and-egg where you can't log in because
+// you're not logged in. The OAuth provider's login() itself runs the device-code
+// flow when hasCredentials() is false (see privateerOAuthProvider.login), so first
+// login works entirely through Pi once the provider is present.
 //
 // Registration is SYNCHRONOUS (seeded with the fallback), then refined once the live
 // catalog is fetched. This matters: Pi flushes provider registrations made during the
@@ -151,7 +159,7 @@ export function makeAccountProvider() {
   return (pi: {
     registerProvider?: (name: string, config: unknown) => void;
   }): void => {
-    if (!hasCredentials() || typeof pi.registerProvider !== "function") return;
+    if (typeof pi.registerProvider !== "function") return;
     const register = (ids: string[]): void =>
       pi.registerProvider!("privateer", {
         name: "Privateer account",