backeer-codex 0.5.1 → 0.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "backeer-codex",
3
- "version": "0.5.1",
3
+ "version": "0.7.0",
4
4
  "description": "Backeer approvals, lifecycle notifications and chat-scoped OpenCode connections.",
5
5
  "author": {
6
6
  "name": "Backeer"
package/README.md CHANGED
@@ -25,8 +25,12 @@ selection; subagents stay hidden unless requested. Connect by exact title withou
25
25
  copying an ID. Duplicate titles require an ID from the current list. No automatic
26
26
  newest-session choice or fallback is made.
27
27
 
28
- For terminal setup, run `backeer-codex opencode setup`. For diagnostics, use
29
- `backeer-codex opencode discover`. Both reuse existing credentials and SSH
28
+ For terminal setup, run `backeer-codex opencode setup`. It lets you reuse a saved
29
+ connection and choose a current session by number, without entering a session ID.
30
+ In chat, `connection_setup` guides the same connection/candidate/session choices.
31
+ For a saved connection diagnosis, use `backeer-codex opencode diagnose <name>`
32
+ or the read-only `diagnose_connection` MCP tool. `opencode discover` finds
33
+ verified candidates for first setup. These reuse existing credentials and SSH
30
34
  tunnels; no server, port-range scan, vault extraction, SSH edit or raw-token
31
35
  prompt is added. If the new computer lacks a tunnel or protected token file,
32
36
  setup explains that prerequisite. Custom ports/files can be selected explicitly.
@@ -77,10 +81,22 @@ notification settings are kept separate and unchanged.
77
81
  SSE heartbeats keep hours-long quiet work connected. Transport failures retry
78
82
  every three seconds indefinitely; a bounded tool wait ending does not stop SSE.
79
83
  Disconnecting a binding releases its local resources without stopping OpenCode.
80
- At most 16 local bindings can be open per MCP process. Bindings intentionally
84
+ No fixed binding quota is imposed. Bindings intentionally
81
85
  live in memory: after restarting the app/MCP process, reconnect to the same
82
86
  existing session. This does not restart its work. Replay gaps are explicit.
83
87
 
88
+ `diagnose_connection` distinguishes a missing local listener, timeout, rejected
89
+ credential, wrong project and unavailable session. Bound diagnostics include SSE
90
+ state, last connection/disconnection times, retry count and buffered event count;
91
+ they never print credentials or credential paths. During a temporary transport
92
+ failure, reads can return this binding's buffered output with `verified: false`.
93
+ The same binding/cursor is retained; new instructions and answers still require
94
+ fresh project/session verification. Missing replay history is reported as a gap,
95
+ never invented or treated as complete. A gap must not be acknowledged until
96
+ `session_status` succeeds for the same target. Disconnecting one chat does not
97
+ close another chat's stream, and active bindings do not consume the quota for
98
+ read-only session listings or diagnosis.
99
+
84
100
  The plugin does not create SSH tunnels or change SSH permissions. Keep the saved
85
101
  tunnel running; a dropped tunnel is handled by SSE reconnection once it returns.
86
102
  On Windows, token ownership/ACL is checked using built-in PowerShell; allow only
@@ -143,7 +159,7 @@ backeer-codex status
143
159
 
144
160
  In `remote` mode, the plugin uses a synchronous `PermissionRequest` hook. Codex waits for
145
161
  this hook before showing its native approval prompt. While Backeer is waiting for
146
- a remote decision (110 seconds by default), the native prompt is not available.
162
+ a remote decision (no plugin-imposed timeout by default; the host may enforce its own hook deadline), the native prompt is not available.
147
163
  A valid remote decision resolves the request without displaying the native prompt.
148
164
  If no remote decision arrives, or Backeer fails, the hook returns no decision and
149
165
  Codex continues with its normal local approval flow.
@@ -186,3 +202,9 @@ question answers are not implemented. Neither mode emulates or scrapes that UI.
186
202
  ### OpenCode questions (0.5.0)
187
203
 
188
204
  The MCP tools `list_questions` and `answer_question` read pending ordinary questions and submit option selections or custom text in the bound session. Use local plugin 0.5.1+ and remote `backeer-opencode` 0.8.1+ for verified private V2 server connections and safe native-question diagnostics. Existing sessions are preserved; no new service is started. Pending questions are read from OpenCode even after reconnect; no background question polling is added. Permission and authentication forms remain excluded. See the bundled Backeer skill for exact selection, user authorization and delivery retry rules.
205
+
206
+ ### Usage quotas
207
+
208
+ The bundled adapter imposes no fixed count/size/age quota on profiles, sessions, SSE readers, retained output, prompts or ordinary questions/answers. Reads/waits accept optional caller-selected budgets without application maxima; omitting them reads available output or waits until output/cancellation. Companion websocket/JSONL messages and approval history have no fixed quota. Redaction preserves all non-secret text, array entries and fields. No SSH or authorization checks are bypassed. Memory, native APIs and Codex/MCP/gateway protocol limits still apply. Codex hook lifecycle deadlines are enforced by the host: https://learn.chatgpt.com/docs/hooks .
209
+
210
+ Each chat receives only its selected session's SSE output, avoiding unrelated project output in every chat buffer. Concurrent callers share in-flight verification only for the same exact session, with cancellable reader cleanup.