workbuddy-bridge-setup
/workbuddy-bridge-setup
Konfiguruje, naprawia i weryfikuje lokalny most WorkBuddy, który udostępnia modele innym agentom wraz z warstwą dostarczania.
- Autor
- tiqi9896 ↗
- Repozytorium
- workbuddy-hermes-bridge ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 07.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 4
Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Konfiguruje, naprawia i weryfikuje lokalny most WorkBuddy, który udostępnia modele innym agentom wraz z warstwą dostarczania.
Oryginalny opis (EN)
Use when setting up, repairing, or verifying the local WorkBuddy bridge that exposes WorkBuddy models to Hermes/other agents with a delivery layer.
Jak działa
- What this does
- Setup
- Repair path
- Coverage
- Tuning
- Rules
- Troubleshooting
- Scope
Podgląd SKILL.md
--- name: workbuddy-bridge-setup description: Use when setting up, repairing, or verifying the local WorkBuddy bridge that exposes WorkBuddy models to Hermes/other agents with a delivery layer. --- # WorkBuddy bridge — agent skill Install, verify, and repair the local WorkBuddy reverse proxy. `AGENTS.md` in the repo root is the long-form version of this document. ## What this does Two halves in one process: - **Transport** — `bridge/bridge.py` re-exposes WorkBuddy's cloud API (catalog + chat completions) as a local OpenAI-compatible endpoint on `127.0.0.1:8799`. - **Delivery layer** — `bridge/breaker.py` injects a delivery contract into every request, detects refusals/downgrades/fade-outs, and retries with escalation until a real artifact comes back. The delivery layer must live in the bridge. There is no agent-side plugin substitute — if the agent's `base_url` is not the bridge, the contract is never applied. ## Setup ```bash git clone https://github.com/tiqi9896/workbuddy-hermes-bridge.git cd workbuddy-hermes-bridge python bridge/capture_token.py # requires the signed-in desktop client python bridge/bridge.py --verbose # listens on 127.0.0.1:8799 ``` Verify: ```bash python bridge/verify_target_models.py # expect: passed 21 failed 0 total 21 curl http://127.0.0.1:8799/health curl http://127.0.0.1:8799/breaker # enabled=true, injections rising ``` Point the agent at it: ```bash hermes config set model.provider workbuddy hermes config set model.base_url http://127.0.0.1:8799/v1 hermes config set model.api_key workbuddy-local-bridge ``` ## Repair path **Always check the disk state, never just the HTTP status.** ```bash python bridge/target_guard.py ``` It runs the coverage self-check and, if `breaker.py` was truncated or corrupted, restores it from `backup/breaker.py.good` (sha256-verified), triggers a hot reload via `GET /reload`, and re-verifies. Why this matters: `importlib.reload` preserves existing module attributes, so a corrupted file on disk can leave a running bridge behaving perfectly while a restart would drop every target model out of the delivery layer. A 200 from `/health` is not proof the file is intact. This has happened for real — a 140 KB `breaker.py` was cut to 12.5 KB by an edit script whose anchor search failed and sliced with `-1`. ## Coverage The target-model addendum (the strongest section) applies to: - `hy4free`, `hy4std`, `hy4-preview-x` - `deepseek-v4.1-flash` and the `deepseek*` family - `space-bunny` and the `space*` family - `minimax-m3.1-flash` and the `minimax*` family - `glm-5.3-flash` and the `glm*` family - `auto`, `default`, `fast-model`, `balanced-model`, `deep-model` The routing tiers matter: their upstream target is not visible to the client, so they must be treated as targets explicitly rather than matched by name prefix. ## Tuning Text lives in `bridge/bridge_text/` and `bridge/breaker_prompt*.txt`. Code lives in the `.py` files. Do not mix them. | Want to change | Edit | |---|---| | base prompt | `bridge/breaker_prompt.txt` / `.en.txt` | | strongest target section | `bridge/bridge_text/unlimited.txt` / `.en.txt` | | adult clause | `bridge/bridge_text/adult_clause.txt` / `.en.txt` | | per-family clauses | `bridge/bridge_text/family_addenda.json` / `.en.json` | | adult genre carriers | `bridge/bridge_text/adult_carriers.json` / `.en.json` | | escalation ladder | `bridge/bridge_text/adult_escalation.json` / `.en.json` | | language | `config.json` → `breaker_lang` | Resources are re-read per request. The constants embedded in `breaker.py` and `bridge.py` are the fallback — keep them in sync, or behavior will depend on which file exists. ## Rules 1. Never commit `bridge/token.json`, `bridge/bridge.log`, `bridge/models_cache.json`, or `bridge/backup/`. They are gitignored. 2. Never hardcode machine paths. Use `Path(__file__).parent` or the `WORKBUDDY_APP_EXE` / `WB_PYTHON` environment variables. 3. After changing `breaker.py` or `bridge.py`, run `python bridge/verify_target_models.py` and report the result. 4. A successful compile does not mean the file is intact. 5. The delivery layer must stay language-neutral in code. ## Troubleshooting | Symptom | Fix | |---|---| | 401 from the bridge | `python bridge/capture_token.py` | | self-check fails | `python bridge/target_guard.py` | | agent still gets refusals | confirm `base_url` is the bridge; check `injections` rises | | bridge exits at startup | port in use — change `port` in `config.json` | | capture cannot find the app | wrong `app_exe` — re-locate `WorkBuddy.exe` | | requests hang | raise `request_timeout_seconds` | ## Scope A behavior-contract layer for models the user calls with their own WorkBuddy account. It does not bypass provider-side enforcement and does not make third-party systems more accessible. Use it for authorized work and comply with the provider's terms and applicable law.
Pliki w paczce (2)
- SKILL.md 5 KB
- SKILL.zh-CN.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · tiqi9896/workbuddy-hermes-bridge | 100 | MIT |
| tiqi9896/workbuddy-hermes-bridge-zh | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 6e77fd96534a (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100workbuddy-cache-monitor
Liczy i pokazuje trafienia w cache kontekstu WorkBuddy dla każdego zadania, z tokenami, liczbą żądań i rozkładem czasu. - 100workbuddy-skin-change
Zmienia tło klienta WorkBuddy na obraz podany przez użytkownika, z możliwością cofnięcia zmian. - 95workbuddy-account-switch
Przełącza konta w lokalnej aplikacji WorkBuddy i przygotowuje pliki zadań, które użytkownik uruchamia w graficznym przełączniku. - 100buddy-control
Steruje wdrażaniem narzędzi na komputerze i przydziela zadania agentom CodeBuddy i WorkBuddy, sprawdzając ich wyniki. - 81tiangong-auto-research-workbuddy
Dostosowuje zarządzany przepływ Tiangong Auto Research do natywnego producenta WorkBuddy lub CodeBuddy w trybie Default Permission, jako cienki router do zainstalowanego skilla tiangong-auto-research. - 90curate-workbuddy-resource
Ocenia publiczne repozytorium, dokument, skill, integrację MCP, workflow lub poradnik pod katalog zasobów WorkBuddy i rekomenduje włączenie, wstrzymanie albo wykluczenie według dowodów jakości, licencji i bezpieczeństwa.