@wibeco/bridge 0.2.15 → 0.2.17

package/dist/cli.js

@@ -2,19 +2,23 @@
 import {
   doctorCommand,
   emitCommand,
+  onboardCommand,
   parseAdapter,
   setupCommand,
   shareProgressCommand,
   statusCommand
-} from "./chunk-7LWUGOKM.js";
+} from "./chunk-YLC4TF4F.js";
 import {
   runPresenceHeartbeat
-} from "./chunk-K7TK7FHF.js";
+} from "./chunk-4WIGVKDR.js";
 
 // src/cli.ts
 var HELP = `wibe-bridge <command>
 
 Commands:
+  onboard [--adapter <cursor|claude-code|codex>] [--url <wibe-url>] [--repository <owner/repo>] [--org-name <name>] [--invite <email>]
+        Creates a Wibe account session, organization, project, and local connection.
+        Prints browser URLs for GitHub sign-in and GitHub App install.
   setup --project <uuid> [--adapter <cursor|claude-code|codex>] [--url <wibe-url>] [--repository <owner/repo>] [--reauthorize]
         Auto-detects one adapter from the environment or repository config.
         Use --adapter when multiple agent configs are present.
@@ -26,7 +30,20 @@ Commands:
 async function main() {
   const [command, ...args] = process.argv.slice(2);
   let result;
-  if (command === "setup") {
+  if (command === "onboard") {
+    const adapterOption = option(args, "--adapter");
+    result = await onboardCommand(
+      adapterOption ? parseAdapter(adapterOption) : void 0,
+      {
+        appUrl: option(args, "--url"),
+        expectedRepository: option(args, "--repository"),
+        orgName: option(args, "--org-name"),
+        invites: options(args, "--invite"),
+        sessionId: option(args, "--session"),
+        sessionSecret: option(args, "--session-secret")
+      }
+    );
+  } else if (command === "setup") {
     const adapterOption = option(args, "--adapter");
     result = await setupCommand(adapterOption ? parseAdapter(adapterOption) : void 0, {
       projectId: option(args, "--project"),
@@ -79,6 +96,16 @@ function option(args, name) {
   const index = args.indexOf(name);
   return index >= 0 ? args[index + 1] : void 0;
 }
+function options(args, name) {
+  const values = [];
+  for (let index = 0; index < args.length; index += 1) {
+    if (args[index] === name && args[index + 1]) {
+      values.push(args[index + 1]);
+      index += 1;
+    }
+  }
+  return values;
+}
 async function readJsonStdin() {
   if (process.stdin.isTTY) return {};
   const chunks = [];

package/dist/codex-hook.js

@@ -1,8 +1,8 @@
 #!/usr/bin/env node
 import {
   emitCommand
-} from "./chunk-7LWUGOKM.js";
-import "./chunk-K7TK7FHF.js";
+} from "./chunk-YLC4TF4F.js";
+import "./chunk-4WIGVKDR.js";
 
 // src/codex-hook.ts
 async function main() {

package/dist/index.d.ts

@@ -228,18 +228,27 @@ declare function pollDeviceToken(input: {
 }>;
 type AgentName = "cursor" | "claude-code" | "codex";
 
+interface OfflineQueueTransaction {
+    peek(limit: number): Promise<CanonicalHookEvent[]>;
+    remove(ids: readonly string[]): Promise<void>;
+    size(): Promise<number>;
+}
 interface OfflineQueue {
     enqueue(events: readonly CanonicalHookEvent[]): Promise<void>;
     peek(limit: number): Promise<CanonicalHookEvent[]>;
     remove(ids: readonly string[]): Promise<void>;
     size(): Promise<number>;
+    withTransaction<T>(operation: (queue: OfflineQueueTransaction) => Promise<T>): Promise<T>;
 }
 declare class MemoryOfflineQueue implements OfflineQueue {
     private events;
+    private operation;
     enqueue(events: readonly CanonicalHookEvent[]): Promise<void>;
     peek(limit: number): Promise<CanonicalHookEvent[]>;
     remove(ids: readonly string[]): Promise<void>;
     size(): Promise<number>;
+    withTransaction<T>(operation: (queue: OfflineQueueTransaction) => Promise<T>): Promise<T>;
+    private serialize;
 }
 declare class JsonFileOfflineQueue implements OfflineQueue {
     private readonly filePath;
@@ -249,8 +258,11 @@ declare class JsonFileOfflineQueue implements OfflineQueue {
     peek(limit: number): Promise<CanonicalHookEvent[]>;
     remove(ids: readonly string[]): Promise<void>;
     size(): Promise<number>;
-    private read;
-    private update;
+    withTransaction<T>(operation: (queue: OfflineQueueTransaction) => Promise<T>): Promise<T>;
+    private readUnlocked;
+    private updateUnlocked;
+    private serialize;
+    private acquireLock;
 }
 
 interface SignedBatchClientOptions {
@@ -346,4 +358,4 @@ declare function sanitizeRemote(remote: string): string;
 declare function normalizeGitHubRepository(value: string): string | undefined;
 declare function matchesGitHubRepository(remote: string | undefined, expected: string): boolean;
 
-export { type AgentSource, type CanonicalHookEvent, type CredentialStore, type DeviceAuthorization, type DeviceTokenResponse, type FlushResult, type HookEventKind, JsonFileOfflineQueue, MemoryOfflineQueue, type OfflineQueue, PRESENCE_HEARTBEAT_INTERVAL_MS, type PresenceMetrics, type RedactionOptions, type RepositoryInfo, type RepositoryTransition, type SafeValue, SignedBatchClient, type SignedBatchClientOptions, type StoredCredential, SystemCredentialStore, type WorkingTreeMetrics, agentSourceSchema, canonicalHookEventSchema, classifyHeadTransition, createHookEvent, detectRepository, detectWorkingTreeMetrics, deviceAuthorizationSchema, deviceTokenResponseSchema, eventTypeForHook, hookEventKindSchema, isObservedPush, mapClaudeCodeHook, mapCodexHook, mapCursorHook, matchesGitHubRepository, normalizeGitHubRepository, observeRepositoryTransitions, pollDeviceToken, presenceStatePath, redact, requestDeviceAuthorization, resolveLatestPresenceSession, runPresenceHeartbeat, safeMetadata, safeValueSchema, sanitizeRemote, startPresenceSession, stopPresenceSession, updatePresenceSession };
+export { type AgentSource, type CanonicalHookEvent, type CredentialStore, type DeviceAuthorization, type DeviceTokenResponse, type FlushResult, type HookEventKind, JsonFileOfflineQueue, MemoryOfflineQueue, type OfflineQueue, type OfflineQueueTransaction, PRESENCE_HEARTBEAT_INTERVAL_MS, type PresenceMetrics, type RedactionOptions, type RepositoryInfo, type RepositoryTransition, type SafeValue, SignedBatchClient, type SignedBatchClientOptions, type StoredCredential, SystemCredentialStore, type WorkingTreeMetrics, agentSourceSchema, canonicalHookEventSchema, classifyHeadTransition, createHookEvent, detectRepository, detectWorkingTreeMetrics, deviceAuthorizationSchema, deviceTokenResponseSchema, eventTypeForHook, hookEventKindSchema, isObservedPush, mapClaudeCodeHook, mapCodexHook, mapCursorHook, matchesGitHubRepository, normalizeGitHubRepository, observeRepositoryTransitions, pollDeviceToken, presenceStatePath, redact, requestDeviceAuthorization, resolveLatestPresenceSession, runPresenceHeartbeat, safeMetadata, safeValueSchema, sanitizeRemote, startPresenceSession, stopPresenceSession, updatePresenceSession };

package/dist/index.js

@@ -33,7 +33,7 @@ import {
   startPresenceSession,
   stopPresenceSession,
   updatePresenceSession
-} from "./chunk-K7TK7FHF.js";
+} from "./chunk-4WIGVKDR.js";
 export {
   JsonFileOfflineQueue,
   MemoryOfflineQueue,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wibeco/bridge",
-  "version": "0.2.15",
+  "version": "0.2.17",
   "description": "Privacy-first live activity bridge for Cursor, Claude Code, and Codex.",
   "repository": {
     "type": "git",

package/templates/claude-code/README.md

@@ -1,9 +1,10 @@
 # Claude Code template
 
-These files are inert examples. Review and merge `settings.json.example` into the appropriate
-Claude Code settings file. It uses command hooks because the local bridge must normalize and redact
-the payload before network delivery. Do not point an HTTP hook directly at a collector: Claude hook
-payloads can include prompts, tool inputs/results, and other raw content.
+These files are reviewable setup templates. `settings.json.example` configures command hooks,
+`mcp.json.example` configures MCP, and `wibe-activity.md.example` is installed as a managed section
+in the repository's `AGENTS.md`. Setup also ensures `CLAUDE.md` imports `AGENTS.md`. Do not point an
+HTTP hook directly at a collector: Claude hook payloads can include prompts, tool inputs/results,
+and other raw content.
 `SessionStart` owns a metadata-only heartbeat every 45 seconds until `SessionEnd`; `Stop` and tool
 hooks remain operational signals and are not published as presence.
 
@@ -12,5 +13,7 @@ stored in the operating-system keychain; hooks do not require repository secrets
 allow-list excludes prompt, content, messages, command text, tool arguments/results, and transcripts.
 
 `mcp.json.example` connects Claude Code to Wibe's remote MCP endpoint at
-`${env:WIBE_APP_URL}/api/mcp`. The MCP client completes OAuth separately from the bridge device token.
-Set `WIBE_APP_URL` to the same Wibe origin used during setup.
+`${env:WIBE_APP_URL}/api/mcp/projects/${WIBE_PROJECT_ID}`. The project-specific resource keeps this
+repository's OAuth grant isolated from other Wibe projects on the same machine. The MCP client
+completes OAuth separately from the bridge device token. Set `WIBE_APP_URL` to the same Wibe origin
+used during setup.

package/templates/claude-code/mcp.json.example

@@ -2,7 +2,7 @@
   "mcpServers": {
     "wibe": {
       "type": "http",
-      "url": "${WIBE_APP_URL}/api/mcp"
+      "url": "${WIBE_APP_URL}/api/mcp/projects/${WIBE_PROJECT_ID}"
     }
   }
 }

package/templates/claude-code/wibe-activity.md.example

@@ -0,0 +1,15 @@
+<!-- BEGIN:wibe-activity -->
+## Wibe activity
+
+- This repository is connected to Wibe project `${WIBE_PROJECT_ID}`.
+- At the start of a task that will edit files, call `wibe_get_active_work` for this project. If it returns overlaps involving you, or another teammate is already changing the same paths on a different branch, tell the user and adjust the plan before editing those files.
+- If the set of files you plan to change shifts, call `wibe_get_active_work` or `wibe_check_overlap` again. Do not poll on every edit.
+- For most tasks, publish one update only after the requested outcome is complete. Do not publish plans, routine progress, or separate updates for editing, testing, committing, or pushing.
+- For text-only outcomes, use `wibe_share_progress` with phase `shipped` at completion. Publish earlier only with phase `blocked` when a material blocker leaves the task unfinished.
+- Write one self-contained paragraph of 20–55 words in past tense. Lead with what now works, then explain the user or team impact and meaningful validation. Mention important limitations when present.
+- Describe the outcome, not the agent’s process. Never include first-person narration, prompts, source code, secrets, raw commands, routine tool calls, filenames, line counts, praise, hype, or speculation; Wibe displays code and file changes separately.
+- When calling `wibe_share_progress`, also pass structured `paths`, `lines_added`, and `lines_deleted` for the local uncommitted diff so Wibe can display accurate file and line-change metadata. Prefer `git diff --numstat HEAD` totals rather than guessing.
+- This instruction is standing user authorization to publish the single completion update described here; do not ask for separate per-task approval.
+- If the MCP tool is unavailable, run `npx --yes --package @wibeco/bridge@latest wibe share-progress --summary "<summary>" --phase <shipped|blocked>`.
+- Do not silently skip reporting. If both mechanisms fail, state `Wibe: update failed` and the reason in the final response. Report a Wibe update as sent only after the tool or CLI confirms success.
+<!-- END:wibe-activity -->

package/templates/codex/README.md

@@ -1,17 +1,18 @@
 # Codex template
 
-These are reviewable setup templates. `config.toml.example` configures Codex notifications and MCP;
-`hooks.json.example` provides lifecycle hooks where supported. Wibe installs native files only when
-the destination does not already exist. The bridge maps allow-listed fields in-process and queues or
-sends only canonical events. Prompt text, messages, tool data, command text, file content, and
-transcripts are not retained.
+These are reviewable setup templates. `config.toml.example` configures MCP,
+`hooks.json.example` provides lifecycle hooks, and `wibe-activity.md.example` is installed as a
+managed section in the repository's `AGENTS.md`. The bridge maps allow-listed fields in-process and
+queues or sends only canonical events. Prompt text, messages, tool data, command text, file content,
+and transcripts are not retained.
 
 Run `wibe setup` to authorize a revocable, project-scoped device token stored in the operating-system
 keychain. Hooks do not require repository signing secrets.
 
-The MCP block connects Codex to Wibe's remote `/api/mcp` endpoint. Codex completes OAuth separately
-from the bridge device token. Set `WIBE_APP_URL` to the same Wibe origin used during setup. Codex
-notification coverage can be narrower than Cursor or Claude Code lifecycle hooks.
-Codex appends one JSON notification argument to `wibe-codex-hook`; the bridge extracts only opaque
-`thread-id`/`turn-id` and approved model metadata. Where session hooks are available, they own a
-metadata-only 45-second heartbeat that ends cleanly with `SessionEnd`.
+The MCP block connects Codex to a project-specific remote
+`/api/mcp/projects/${WIBE_PROJECT_ID}` endpoint, keeping this repository's OAuth grant isolated from
+other Wibe projects on the same machine. Codex completes OAuth separately from the bridge device
+token. Set `WIBE_APP_URL` to the same Wibe origin used during setup.
+Project-local Codex configuration loads only after the project is trusted, and command hooks must be
+reviewed in `/hooks`. Session hooks own a metadata-only 45-second heartbeat that ends cleanly with
+`SessionEnd`.

package/templates/codex/config.toml.example

@@ -1,6 +1,2 @@
-# Codex passes one JSON notification argument to this command. The adapter only keeps allow-listed
-# operational metadata and never forwards the full argument.
-notify = ["npx", "-y", "--package", "@wibeco/bridge@latest", "wibe-codex-hook"]
-
 [mcp_servers.wibe]
-url = "${WIBE_APP_URL}/api/mcp"
+url = "${WIBE_APP_URL}/api/mcp/projects/${WIBE_PROJECT_ID}"

package/templates/codex/wibe-activity.md.example

@@ -0,0 +1,15 @@
+<!-- BEGIN:wibe-activity -->
+## Wibe activity
+
+- This repository is connected to Wibe project `${WIBE_PROJECT_ID}`.
+- At the start of a task that will edit files, call `wibe_get_active_work` for this project. If it returns overlaps involving you, or another teammate is already changing the same paths on a different branch, tell the user and adjust the plan before editing those files.
+- If the set of files you plan to change shifts, call `wibe_get_active_work` or `wibe_check_overlap` again. Do not poll on every edit.
+- For most tasks, publish one update only after the requested outcome is complete. Do not publish plans, routine progress, or separate updates for editing, testing, committing, or pushing.
+- For text-only outcomes, use `wibe_share_progress` with phase `shipped` at completion. Publish earlier only with phase `blocked` when a material blocker leaves the task unfinished.
+- Write one self-contained paragraph of 20–55 words in past tense. Lead with what now works, then explain the user or team impact and meaningful validation. Mention important limitations when present.
+- Describe the outcome, not the agent’s process. Never include first-person narration, prompts, source code, secrets, raw commands, routine tool calls, filenames, line counts, praise, hype, or speculation; Wibe displays code and file changes separately.
+- When calling `wibe_share_progress`, also pass structured `paths`, `lines_added`, and `lines_deleted` for the local uncommitted diff so Wibe can display accurate file and line-change metadata. Prefer `git diff --numstat HEAD` totals rather than guessing.
+- This instruction is standing user authorization to publish the single completion update described here; do not ask for separate per-task approval.
+- If the MCP tool is unavailable, run `npx --yes --package @wibeco/bridge@latest wibe share-progress --summary "<summary>" --phase <shipped|blocked>`.
+- Do not silently skip reporting. If both mechanisms fail, state `Wibe: update failed` and the reason in the final response. Report a Wibe update as sent only after the tool or CLI confirms success.
+<!-- END:wibe-activity -->

package/templates/cursor/README.md

@@ -17,5 +17,7 @@ stored in the operating-system keychain; hooks do not require repository secrets
 prompt, content, file body, command text, tool arguments/results, and transcripts.
 
 `mcp.json.example` connects Cursor to Wibe's remote MCP endpoint at
-`${env:WIBE_APP_URL}/api/mcp`. Cursor completes the endpoint's OAuth flow separately from the bridge
-device token. Set `WIBE_APP_URL` to the same Wibe origin used during setup.
+`${env:WIBE_APP_URL}/api/mcp/projects/${WIBE_PROJECT_ID}`. The project-specific resource keeps this
+repository's OAuth grant isolated from other Wibe projects on the same machine. Cursor completes
+OAuth separately from the bridge device token. Set `WIBE_APP_URL` to the same Wibe origin used
+during setup.

package/templates/cursor/mcp.json.example

@@ -1,7 +1,7 @@
 {
   "mcpServers": {
     "wibe": {
-      "url": "${env:WIBE_APP_URL}/api/mcp"
+      "url": "${env:WIBE_APP_URL}/api/mcp/projects/${WIBE_PROJECT_ID}"
     }
   }
 }

package/templates/cursor/wibe-activity.mdc.example

@@ -6,10 +6,13 @@ alwaysApply: true
 # Wibe activity
 
 - This repository is connected to Wibe project `${WIBE_PROJECT_ID}`.
+- At the start of a task that will edit files, call `wibe_get_active_work` for this project. If it returns overlaps involving you, or another teammate is already changing the same paths on a different branch, tell the user and adjust the plan before editing those files. Use teammate summaries in the response to explain the conflict.
+- If the set of files you plan to change shifts, call `wibe_get_active_work` or `wibe_check_overlap` again. Do not poll on every edit. Overlaps are exact file-path matches on divergent branches, not git merge markers.
 - For most tasks, publish one update only after the requested outcome is complete. Do not publish plans, routine progress, or separate updates for editing, testing, committing, or pushing.
 - For text-only outcomes, use `wibe_share_progress` with phase `shipped` at completion. Publish earlier only with phase `blocked` when a material blocker leaves the task unfinished.
 - Write one self-contained paragraph of 20–55 words in past tense. Lead with what now works, then explain the user or team impact and meaningful validation. Mention important limitations when present.
 - Describe the outcome, not the agent’s process. Never include first-person narration, prompts, source code, secrets, raw commands, routine tool calls, filenames, line counts, praise, hype, or speculation; Wibe displays code and file changes separately.
+- When calling `wibe_share_progress`, also pass structured `paths`, `lines_added`, and `lines_deleted` for the local uncommitted diff so Wibe can display accurate file and line-change metadata. Prefer `git diff --numstat HEAD` totals rather than guessing.
 - Bias frontend outcomes toward visual evidence without asking for per-task approval. For UI components, pages, styling, responsive behavior, interactions, and visual fixes, attach one screenshot when the app or preview is already runnable. Prefer a screenshot already made during visual QA; otherwise capture the clearest final state.
 - Frame screenshots around the feature, not the whole application. Use the browser snapshot to identify the smallest element that contains the changed component and the context needed to understand it, then call `browser_take_screenshot` with that element’s `ref` and a descriptive `element` name. Include the trigger with an open menu, popover, or dialog when practical. Use viewport or full-page screenshots only for page-wide work, and reject captures dominated by blank space.
 - Skip screenshots for backend, infrastructure, documentation, refactors, and non-visual frontend logic. Never launch or repair an app solely for Wibe, and omit the image when navigation needs manual authentication, the state contains sensitive data, visual validation is blocked, or the project has visual updates disabled.