@omercnet/paseo-omp 2.0.2-next.270.1 → 2.0.2-next.271.1

package/OVERVIEW.md

@@ -2,7 +2,7 @@ OMP adds an agent provider for the OMP coding agent, plus an OMP sidebar and wor
 
 ## Setup
 
-- Paseo ^0.11.0 || ^0.12.0.
+- Paseo ^0.12.0.
 - OMP 18.1.15 or newer on the daemon host, speaking RPC protocol v2. Older runtimes are rejected.
 - Provider options let you change the OMP command, set environment values, choose an output redaction mode and set a session directory and timeout. Named OMP profiles appear as separate `OMP · <profile>` providers.
 

package/README.md

@@ -24,7 +24,7 @@ before capture.
 
 ## Quick start
 
-Requirements: Paseo `^0.11.0 || ^0.12.0`, OMP `18.1.15` or newer, and OMP RPC protocol v2. The config screen and Hub row use the 0.11 screen and sidebar APIs, so Paseo 0.9 and 0.10 hosts are no longer supported.
+Requirements: Paseo `^0.12.0`, OMP `18.1.15` or newer, and OMP RPC protocol v2. Workspace discovery passes `includeBackground`, which throws on hosts that do not advertise `features.backgroundWorkspaces` (new in 0.12), so older hosts are not supported.
 
 ```bash
 paseo plugin install npm:@omercnet/paseo-omp@<version>
@@ -125,7 +125,7 @@ Existing agents whose provider is `omp` remain owned by the bundled provider. Ne
 
 OMP `18.1.15` is the oldest version tested end to end. The direct provider's hard compatibility gate is `rpc-ui` protocol v2: metadata-free legacy ready frames and v1-only runtimes are rejected before a provider session opens because they cannot support the advertised persistence and conversation-rewind capabilities. Typed tool approvals remain capability-gated and fall back as described above. For terminal completion, a matching `agent_end.requestId` is authoritative and mismatches are ignored before state changes. Released OMP 18.2.x builds that omit that field use an ordered fallback requiring a fresh correlated native user entry followed by current-turn assistant activity, an idle non-compacting runtime, and no conflicting permission, tool, steer, or child-session work. Ambiguous events while OMP is active are ignored; unresolved ambiguity after confirmed idle fails only the Paseo turn. This trades a bounded residual same-agent stale-event risk for compatibility with released OMP instead of terminating and lazily restarting the runtime after every later prompt. Paseo clients, including mobile clients inside reconnect grace, do not own or terminate the daemon-managed OMP session.
 
-Paseo 0.11 is the minimum supported release. The controlled Docker canary is pinned to official 0.11.1; nightly SDK checks cover the latest and beta channels. The canary preserves nested provider-subagent ancestry and spawning-tool links, and validates npm-managed plugin sources, platform-owned external URL opening, and whole-item timeline transforms before Overview grouping.
+Paseo 0.12 is the minimum supported release. The controlled Docker canary is pinned to official 0.12.0-beta.2; nightly SDK checks cover the latest and beta channels. The canary preserves nested provider-subagent ancestry and spawning-tool links, and validates npm-managed plugin sources, platform-owned external URL opening, and whole-item timeline transforms before Overview grouping.
 
 Install, update, disable, or remove `paseo-omp` independently of the bundled provider. Verify the provider snapshot contains `omp-plugin` after installation; a bundled `omp` entry may remain present and is not modified by this plugin.
 

package/index.client.tsx

@@ -99,6 +99,7 @@ async function loadAgents(paseo: PaseoApi): Promise<AgentEntry[]> {
   let cursor: string | undefined;
   for (let page = 0; page < MAX_PAGES; page += 1) {
     const result = await paseo.agents.list({
+      filter: { includeBackground: true },
       sort: [{ key: "updated_at", direction: "desc" }],
       page: { limit: PAGE_LIMIT, ...(cursor ? { cursor } : {}) },
     });
@@ -137,7 +138,8 @@ export function registerConfigAndHub(
   }
   const { HubSidebarItem } = createHubSidebar(() =>
     loadHubSnapshot(
-      () => client.paseo.workspaces.list({ page: { limit: 200 } }),
+      () =>
+        client.paseo.workspaces.list({ filter: { includeBackground: true }, page: { limit: 200 } }),
       async (cwd) => (await client.rpc(listHubProcesses, { cwd })).processes,
     ),
   );
@@ -504,7 +506,7 @@ export default function contribute(client: PluginClientContext) {
   let unsubscribeAgentDirectory = () => {};
   let releaseAgentDirectory: (() => Promise<void>) | undefined;
   void client.paseo.agents
-    .list({ subscribe: {} })
+    .list({ subscribe: {}, filter: { includeBackground: true } })
     .then(({ subscription }) => {
       if (!subscription) return;
       if (disposed) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omercnet/paseo-omp",
-  "version": "2.0.2-next.270.1",
+  "version": "2.0.2-next.271.1",
   "type": "module",
   "description": "Paseo integration for OMP, including its direct provider and workspace tooling.",
   "license": "MIT",

package/paseo-plugin.json

@@ -1,6 +1,6 @@
 {
   "id": "paseo-omp",
   "description": "Paseo integration for OMP, including its direct provider and workspace tooling.",
-  "requirements": { "paseo": "^0.11.0 || ^0.12.0" },
+  "requirements": { "paseo": "^0.12.0" },
   "build": [["node", "scripts/prepare-dependencies.mjs"]]
 }

package/server/package-version.ts

@@ -1,2 +1,2 @@
 /** Release Please keeps this bundle-safe constant aligned with package.json. */
-export const PASEO_OMP_PACKAGE_VERSION = "2.0.2-next.270.1"; // x-release-please-version
+export const PASEO_OMP_PACKAGE_VERSION = "2.0.2-next.271.1"; // x-release-please-version