devops-bot-sdk 1.6.86__tar.gz → 1.6.87__tar.gz

{devops_bot_sdk-1.6.86 → devops_bot_sdk-1.6.87}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devops-bot-sdk
-Version: 1.6.86
+Version: 1.6.87
 Summary: DevOps Bot Desktop SDK — thin client for the AgentOS Electron desktop app
 Author: noumanaziz2128
 License-Expression: LicenseRef-Proprietary

{devops_bot_sdk-1.6.86 → devops_bot_sdk-1.6.87}/devops_bot_sdk.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devops-bot-sdk
-Version: 1.6.86
+Version: 1.6.87
 Summary: DevOps Bot Desktop SDK — thin client for the AgentOS Electron desktop app
 Author: noumanaziz2128
 License-Expression: LicenseRef-Proprietary

{devops_bot_sdk-1.6.86 → devops_bot_sdk-1.6.87}/sdk/__init__.py

@@ -1,6 +1,6 @@
 """AgentOS Desktop SDK — thin HTTPS/SSE client for the Electron app.
 
-Version: 1.6.86
+Version: 1.6.87
 
 Public surface:
   BackendClient.from_config()        — create client from ~/.agentos/config.toml
@@ -34,7 +34,7 @@ Rules:
   - All data egress through submit_webhook only
 """
 
-__version__ = "1.6.86"   # SINGLE SOURCE OF TRUTH — bump on every change; pyproject,
+__version__ = "1.6.87"   # SINGLE SOURCE OF TRUTH — bump on every change; pyproject,
 __author__  = "AgentOS"   # sdk.client.SDK_VERSION and the UI server version all read this.
 
 from sdk.client import BackendClient

{devops_bot_sdk-1.6.86 → devops_bot_sdk-1.6.87}/sdk/helpdesk_kb.md

@@ -101,6 +101,45 @@ the fix is not in their code, `agentos-auto update` installs the latest.
   unresolved".** The `agentId` on the ticket could not be resolved
   (`handlers._resolve_ticket_agent`); check the agent exists with
   `agentos agent list`, or run with an explicit `--agent NAME`.
+- **AI Draftsman fallback (`ad`) fails with `RATE_LIMIT: 429 RESOURCE_EXHAUSTED`.**
+  The text is Vertex's, but measured on 2026-10-24 the cause was Azure: the
+  gateway's `gpt-5.4` deployment (eastus) over its tokens-per-minute quota, then
+  every fallback model, with only the last error shown. Client side, `ad` 1.1.2
+  retries that error itself (5/10/20/40s); the SDK keeps machines on it —
+  `local_exec.FALLBACK_MIN_VERSION` is `(1, 1, 2)` and an older `ad` is upgraded
+  on `agentos-auto update`, or now with `agentos fallback install`. Check with
+  `agentos fallback status`. Server side (ai-draftsman-ml-b2b), rate-limited
+  deployments cool down and requests wait for capacity instead of failing, once
+  that change is deployed. Large prompts (a long ticket, `agentos help`) hit the
+  limit sooner; retrying a minute later usually works.
+- **`agentos-auto update` says "still on vX — the upgrade did not take" but pip
+  exited 0.** Fixed in `updater._fresh_python_argv`: the post-install check ran
+  `python -c`, which reads the current directory first, so run from inside a
+  checkout of this repo it read the checkout's leftover `devops_bot_sdk.egg-info`
+  instead of the install. On an older SDK: run the update from any other folder,
+  or delete `devops_bot_sdk.egg-info` in the checkout (generated, git-ignored).
+  The install itself had worked.
+- **After `agentos-auto update`: "no systemd unit 'agentos-ui' — restart the panel
+  manually", "could not read the firewall state (needs root …) … sudo ufw allow
+  8765/tcp", "VPS health: not reported — not_assigned_vps".** Not errors. The
+  update restarts the panel so it runs the new code (`sdk/ui/service.py`), checks
+  the panel's port is open for remote access (`sdk/firewall.py` — it never runs
+  sudo itself, so unprivileged it prints the command instead), and reports VPS
+  health only from the VPS assigned to the account (`sdk/vps_health.py`). On a
+  laptop or any machine that is not the assigned VPS all three are expected and
+  need no action; on the VPS, open the port with the printed command if the panel
+  must be reachable remotely, and restart `agentos-ui` if it runs by hand.
+
+## Help in the control panel
+
+The panel's **Help** page (`/help.html`, "Help" in the nav; `sdk/ui/static/help.html`)
+is the same helper as `agentos help`: describe the problem, the answer shows which
+engine answered (claude or the AI Draftsman fallback), follow-ups stay in the same
+case. **Collect diagnostics only** = `agentos doctor`; **Download bundle for your
+admin** = a zip of the case's diagnostics, errors and logs (no SDK source). API:
+`POST /api/ui/help/ask` (a job), `POST /api/ui/help/doctor`,
+`GET /api/ui/help/case/{name}/bundle` (`sdk/ui/api.py`). It runs on the machine the
+panel runs on, so it reads that machine's logs.
 
 ## Useful commands (all verified to exist)