@opengeni/runtime 3.1.3-canary.38890816741001 → 3.2.2

package/dist/index.js

@@ -187,7 +187,7 @@ import {
   workspaceEnvironmentInstructions,
   wrapAttemptToolDefinitions,
   wrapAttemptToolExecute
-} from "./chunk-GPCVTVNT.js";
+} from "./chunk-2AUDDDO2.js";
 import {
   ActiveBackendUnresolvableError,
   BROWSER_CONTROL_ADMIN_TOKEN_FILE,

package/dist/workspace-tool-gateway.js

@@ -3,7 +3,7 @@ import {
   prepareAgentTools,
   secretArgumentMode,
   sessionMcpApprovalConnectionId
-} from "./chunk-GPCVTVNT.js";
+} from "./chunk-2AUDDDO2.js";
 import "./chunk-462CH77G.js";
 import "./chunk-4KFT2G3W.js";
 import "./chunk-7OUG7WBV.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@opengeni/runtime",
-  "version": "3.1.3-canary.38890816741001",
+  "version": "3.2.2",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",
@@ -75,19 +75,19 @@
     "@openai/agents": "0.14.3",
     "@openai/agents-core": "0.14.3",
     "@openai/agents-extensions": "0.14.3",
-    "@opengeni/agent-proto": "3.1.3-canary.38890816741001",
-    "@opengeni/capabilities": "3.1.3-canary.38890816741001",
-    "@opengeni/codemode": "3.1.3-canary.38890816741001",
-    "@opengeni/codex": "3.1.3-canary.38890816741001",
-    "@opengeni/config": "3.1.3-canary.38890816741001",
-    "@opengeni/contracts": "3.1.3-canary.38890816741001",
-    "@opengeni/interaction": "3.1.3-canary.38890816741001",
-    "@opengeni/network": "3.1.3-canary.38890816741001",
-    "@opengeni/observability": "3.1.3-canary.38890816741001",
-    "@opengeni/sdk": "3.1.3-canary.38890816741001",
-    "@opengeni/tool-gateway": "3.1.3-canary.38890816741001",
-    "@opengeni/vaults": "3.1.3-canary.38890816741001",
-    "@opengeni/xai-subscription": "3.1.3-canary.38890816741001",
+    "@opengeni/agent-proto": "3.2.2",
+    "@opengeni/capabilities": "3.2.2",
+    "@opengeni/codemode": "3.2.2",
+    "@opengeni/codex": "3.2.2",
+    "@opengeni/config": "3.2.2",
+    "@opengeni/contracts": "3.2.2",
+    "@opengeni/interaction": "3.2.2",
+    "@opengeni/network": "3.2.2",
+    "@opengeni/observability": "3.2.2",
+    "@opengeni/sdk": "3.2.2",
+    "@opengeni/tool-gateway": "3.2.2",
+    "@opengeni/vaults": "3.2.2",
+    "@opengeni/xai-subscription": "3.2.2",
     "debug": "4.4.3",
     "modal": "0.9.0",
     "openai": "6.47.0",

package/src/bundled_default_skills/opengeni-client/references/tools-and-auth.md

@@ -193,3 +193,54 @@ README's Workspace tools section for approval and migration details.
 Never put tokens in prompts, Skills, `modelContext`, tool URLs, browser code,
 or logs. Opengeni stores Connection and MCP header secrets encrypted and keeps
 them out of the model's context.
+
+### Your product as a vault provider
+
+Use native vaults when the agent needs to discover and use stored credentials.
+An embedding product can expose multiple remote vaults through a signed
+`external` connection; an in-process host can keep using
+`connectionCredentials.vaultProvider`. Keep the simple chat/tool integration
+above unchanged unless the product actually needs this optional capability.
+
+Configure remote connections on the server with `vaultsApi(client, workspaceId)`
+from `@opengeni/sdk`: `installVaultProvider`, `getVaultProviderCatalog`,
+`listProviderVaults`, and `linkProviderVault`. Never put provider tokens or the
+signing secret in browser code, model context, or URL parameters. Verify each
+request's raw-body signature and map its native account/workspace/subject to
+the host's actual tenant/user before authorizing it. A shared connection must
+not return a different user's inventory into the same metadata mirror; use
+separate user-owned connections for user-specific stores.
+
+Connection setup uses the existing `connections:write` and `secrets:write`
+permissions and native owner checks, including authorized agent attempts for
+shared connections. Personal setup requires the verified owner, and
+organization setup requires its admin. List/read/write operations always use
+the registered connection endpoint, not a per-call URL chosen by a tool caller.
+
+`getVaultProviderCatalog` includes deployment availability even before anyone
+connects; disable unavailable setup choices instead of collecting credentials
+that this deployment cannot use. `listVaultProviderConnections` remains a
+metadata-only convenience when only existing connections are needed.
+
+For a remote host, use `createExternalVaultReceiver` from the server-only
+`@opengeni/sdk/external-vault-receiver` subpath and a durable atomic replay and
+mutation store. The in-memory store is only for local tests. Its
+`resolveConnection` binds the native connection to one fixed host inventory;
+`authorize` checks the mapped person on every operation. If the host must
+register the native connection ID first, install returns saved/pending setup;
+register that ID, then verify. Never accept all unknown connections into one
+default tenant to avoid this registration step.
+
+Provider capabilities are granular: do not assume every read-write vault can
+update TOTP, upload files, restore history or archive items. Distinguish cached
+metadata from live value reads. Incomplete discovery or an unavailable source
+is not proof that the user has no matching secret. For a saved-but-pending
+setup (`discoveryPending: true`), use `verifyVaultProviderConnection` with the
+connection ID rather than resubmitting a consumed bootstrap token.
+
+The native secret ask card still saves to hosted vaults only. If the host must
+own collection, collect in the host UI and expose the saved item via its
+provider. Keep short-lived per-attempt credentials on the existing renewable
+credential callback: a stored item does not replace expiry/renewal, Git/MCP
+transport bindings or cleanup. See the product's external-vault and credential
+provider documentation before implementing either path.

package/src/bundled_secret_skills/opengeni-secrets/SKILL.md

@@ -5,10 +5,8 @@ description: Use when signing in, creating accounts, storing or using passwords,
 
 # Secrets: sign in and use credentials yourself
 
-You are trusted with the user's vaults. Act on your own: sign in, create
-accounts when the task allows it, enroll your own 2FA, fetch email and SMS
-codes, and solve CAPTCHAs. You never need to see a value: write a reference and
-it resolves where it runs.
+Use references instead of viewing values. Sign in, create accounts when the
+task allows it, enroll 2FA, fetch codes and solve CAPTCHAs yourself.
 
 ## References
 
@@ -30,16 +28,15 @@ The `secret_*` tools take references as names and never resolve them.
 
 ## Tools
 
-- `secret_search {query?, website?, type?, vault?, cursor?}`: items and
-  references, never values; no filters lists all, page one lists vaults.
-  Repeat with `cursor` while `nextCursor` is set.
-- `secret_save {item, vault?, saveTo?, type?, websites?, username?, fields?, mode?}`:
-  each field takes one of `value`, `generate`, `fromReference` or
-  `restoreVersion`. Use `generate` for new passwords.
-- `secret_move {reference, toVault, mode, newName?}`: move or copy an item.
-- `secret_delete {reference}`: archive an item.
-- `secret_get {reference}`: plaintext, only with `secrets:read`. Use it only
-  when a tool cannot take a reference.
+- `secret_search`: metadata and references, never values. No filters lists all;
+  page one lists vaults. Follow `nextCursor` with unchanged filters. Check
+  `complete` and freshness before inferring absence. `refresh: true` requests
+  fresh inventory without bypassing rate limits.
+- `secret_save`: each field takes `value`, `generate`, `fromReference` or
+  `restoreVersion`. Generate new passwords.
+- `secret_move`: move or copy to another vault.
+- `secret_delete`: archive an item.
+- `secret_get`: plaintext with `secrets:read`, only if references cannot work.
 
 ## Login ladder
 
@@ -65,9 +62,9 @@ after one failure.
 
 - `saveTo`: `user` (Only me, reused later), `task` (throwaway, shared with this
   task's sessions) or `workspace` (team keys, schedules that run without you).
-- Name items after the service and account ("GitHub", "GitHub ops bot") and
-  record `websites` and `username`.
-- Move an item with `secret_move` when a schedule or teammate needs it.
+- Name items by service/account; record `websites` and `username`.
+- Respect provider capabilities. Ask cards save to hosted vaults only.
+  Provider write and move limits: `references/troubleshooting.md`.
 
 ## Missing secrets and errors
 
@@ -75,12 +72,16 @@ A tool result with `secret_reference_error` ran nothing. For a missing secret
 it includes `askCard`: call `request_human_input` with it, changing only
 `saveTo` or `prompt`, then retry with the returned reference.
 
+An unavailable or incomplete provider is not a missing secret: respect retry
+times or reconnect/unlock it. Inspect unknown write outcomes before retrying;
+never repeat a create just because its inventory refresh failed.
+
 ## Playbooks
 
-- `references/login-playbook.md`: browser sign-in, codes, CAPTCHAs.
-- `references/account-creation.md`: sign-ups and generated passwords.
-- `references/2fa-enrollment.md`: enroll and use your own TOTP.
-- `references/api-keys.md`: CLIs, env vars, config files, `secretfile`.
-- `references/ask-card.md`: the `kind: "secret"` question.
-- `references/troubleshooting.md`: every error code and what to do.
-- `references/codemode-and-scripts.md`: escaping in `ogtool` and scripts.
+- Login: `references/login-playbook.md`.
+- Sign-up: `references/account-creation.md`.
+- TOTP: `references/2fa-enrollment.md`.
+- CLI/files: `references/api-keys.md`.
+- Secret card: `references/ask-card.md`.
+- Errors: `references/troubleshooting.md`.
+- Escaping: `references/codemode-and-scripts.md`.

package/src/bundled_secret_skills/opengeni-secrets/references/troubleshooting.md

@@ -23,6 +23,21 @@ and a `hint`. Fix the reference and retry the same action.
 
 ## Save and vault errors
 
+Connected providers advertise their supported operations. Do not work around a
+read-only or unsupported operation by exposing values in logs or process
+arguments. A move requires recoverable removal at the source; a copy may still
+be supported without it. Ask cards save to hosted vaults only.
+
+An offline, locked, rate-limited or incomplete source is not proof that a secret
+is missing. Check search `complete` and source freshness, preserve filters while
+paging, and request `refresh: true` deliberately. It respects rate limits. Report
+the reconnect or unlock action rather than asking for the secret again.
+
+For `provider_outcome_unknown`, inspect the provider before retrying: a write
+may already have succeeded. `provider_inventory_incomplete` with `saved: true`
+means the write succeeded but the subsequent inventory refresh failed. Refresh
+the inventory; never automatically repeat the create.
+
 | Error | What to do |
 |---|---|
 | `vault_read_only` | A connected vault is read-only. Save to an Opengeni vault (`saveTo` without `vault`) or ask the user to make it writable. |