mirror of https://github.com/stablyai/orca.git synced 2026-10-01 00:02:10 +00:00

Files

T

Neil 45f3512a33 feat(agents): add first-class DeepSeek Harness (dsh) support (#22468 )

* feat(agents): add first-class DeepSeek Harness (dsh) support

Register DSH as a supervised Orca agent: catalog entry and detection for its
dsh-tui profile, status/question hooks through DeepSeek's own Claude-Code hook
bridge, composer-ready prompt delivery, session resume, headless Source Control
AI, and title identity that no longer collides with Gemini's.

* fix(dsh): reach Orca through DSH's credential scrub and stop reading its title as Gemini

DSH runs command hooks through its own shell executor, which drops every env var whose
name contains KEY, TOKEN, SECRET or PASSWORD — taking ORCA_PANE_KEY and
ORCA_AGENT_LAUNCH_TOKEN with it, so every hook exited without posting. Mirror both onto
scrub-safe aliases at spawn and restore them at the top of the DSH hook script.

Its title collided too: DSH rests on the same glyph Gemini works on, so a resting DSH
pane was relabelled Gemini CLI and reported working forever. Defer both the Gemini
classifier and the title status detector on DSH's whale, in the base module both copies
of that classifier read.

* test(mobile): repin the session-route closure for the DSH agent icon

* fix(dsh): address review — never splice user rows, cover remote panes, keep the diff off argv

- findManagedDshPatchRegion paired an orphan start marker with a later block's end, so a
  truncated write made install/remove delete the user's own rows. Pair each end with the
  nearest preceding start; regression test fails without the fix.
- The relay PTY env builder never applied the scrub-safe aliases, so remote DSH status
  silently never appeared even with the remote hook installed.
- Source Control AI sent the whole diff on argv; send it over stdin with DSH's '-' marker.
- dsh-tui/dst already chose the interactive profile, so a workspace folder named 'web' or
  'plugin' no longer marks a live agent pane non-interactive.
- Isolate USERPROFILE as well as HOME so a Windows run cannot edit the real home.
- Drop the duplicate README badge and revert an incidental doc reformat.

* refactor(dsh): share the managed-hooks reader and tighten the new modules

Reuse before reimplementing: readManagedDshHookEvents was a near-verbatim copy of Muse's,
with byte-identical private helpers. Both now call one readManagedHookEventsFromJson.

Also: one readTextOrAbsent instead of two spellings of the same read (dropping an
existsSync TOCTOU), one status() builder instead of four inline literals, rmSync(force)
instead of exists-then-unlink, and a redundant empty-string guard before JSON.parse.
The patch-file transforms lose their index juggling for a predicate plus a filter.

* fix(dsh): refuse a flow-style patch file, keep its mode, and stop the relay inheriting a pane

- applyManagedDshPatch matched only an exact `[]`, so `[] # keep empty` or a non-empty
  flow sequence got a block entry appended after it — invalid YAML that would leave DSH
  unable to load the user's own patch layer either. It now strips the token from an empty
  sequence (keeping a trailing comment) and returns null for a non-empty one; install
  reports that and changes nothing.
- The patch rewrite dropped an owner-only file to the umask default (CWE-732); pass
  preserveMode.
- The relay PTY env never dropped inherited pane identity the way the local and daemon
  builders do, so a spawn that specified none could inherit the relay's own and every
  agent's hook would report against that pane.

* fix(dsh): keep the flow-style refusal in every status read, and scope the mode test to POSIX

A refused patch file carries no managed region, so getStatus() fell through to a bare
not_installed with detail null — the actionable 'rewrite it as a block sequence' message
only ever reached the one-shot install() return. Export the predicate and check it first,
behind one shared message constant.

The owner-only mode assertion cannot hold on Windows, where chmod only toggles the
read-only attribute and mode & 0o777 reads 0o666 for any writable file.

* docs(readme): restore the DeepSeek Harness badge lost in the rebase

* test(mobile): repin the session-route closure to the measured 4221

Measured, not derived: 4220 without the DSH icon entry, 4221 with it. Two of the three
modules above main's 4218 pin are not this change's — they arrived with the mobile work
after #22570 and were never repinned; the changelog records that split explicitly.

* fix(dsh): settle tui-idle on the agent's own hook, so supervised workers see it ready

Reported by a tester on the adhoc build: `terminal wait --for tui-idle` ran to its 90s
timeout against an already-ready DSH composer, so a supervised worker never sees the agent
as ready.

Every existing tier reads the title, and DSH deliberately carries no title status: its rest
prefix is Gemini's working glyph, so the detector reports none. A fresh first-party `done`
is better evidence than any title anyway — it is the agent's own account of its own turn,
and normalizeDshEvent drops subagent events, so it is the lead's. Scoped to DSH: for agents
whose hooks report child turns, a mid-turn `done` is the #6011 class this file prevents.

* test(daemon): record the DSH transcript's true-colour I2 divergences

Adding the dsh-tui capture to __fixtures__ enrolled it in the serialize replay sweep, where
it reports 10 I2 divergences and failed the unlisted-transcript default of 0.

Every one is the same shape — visible-grid row=0, a 24-bit background the round trip does
not restore to default — which is DSH's whale intro painting whole rows of true colour.
Verified as an upstream limitation rather than a regression by replaying against the
previous build (build-serialize-addon-at-ref.mjs --ref origin/main): I1 and I3 both hold.

* fix(dsh): return the new tui-idle verdict from the first-party done lane

Main refactored isTuiIdleSatisfied into evaluateTuiIdle, which returns a verdict rather
than a boolean. The DSH lane still returned `true`; it is tier-1 positive evidence, so it
returns READY_STRONG like the title/body lane above it. Re-verified the regression test
still fails without the lane.

* test(relay): pin the scrub-safe pane-identity aliases on the relay spawn path

The relay builds a remote pane's env itself, so the alias mirroring there had no
test: removing the call left every suite green while remote DSH status silently
vanished. Both cases fail without it.

* docs(dsh): point the hook service at the integration reference

The reference doc had no inbound link from anywhere in the repo.

2026-09-27 22:44:18 -07:00

18 KiB

Raw Blame History

Orca

_{English · 中文 · 日本語 · 한국어 · Español · Português}

L'orchestrateur d'IA pour les builders 100x.
Lancez Codex, Claude Code, OpenCode ou Pi côte à côte — chacun dans son propre worktree, le tout suivi au même endroit.

Télécharger Orca

_{Sous Windows ? Prenez la dernière RC — elle inclut des correctifs Windows.}

Fonctionnalités

Companion mobile Surveillez et pilotez vos agents depuis votre téléphone — soyez notifié quand un agent termine, et envoyez des instructions de suivi où que vous soyez. App Store iOS · TestFlight · APK Android 0.0.50 · Docs →
Worktrees parallèles Lancez un même prompt sur cinq agents, chacun dans son propre worktree git isolé — comparez les résultats et mergez le gagnant. Docs →
Splits de terminal Terminaux de niveau Ghostty avec rendu WebGL, splits infinis et un scrollback qui survit aux redémarrages. Docs →
Mode Design Cliquez sur n'importe quel élément d'UI dans une vraie fenêtre Chromium pour envoyer son HTML, son CSS et une capture recadrée directement dans le prompt de votre agent. Docs →
GitHub & Linear, natifs Parcourez PRs, issues et boards de projet dans l'app — ouvrez un worktree depuis n'importe quelle tâche et reviewz sans changer de contexte. Docs →
Worktrees SSH Faites tourner des agents sur une machine distante costaude, avec édition de fichiers, git et terminaux complets — reconnexion auto et port forwarding inclus. Docs →
Annoter les diffs IA Posez des commentaires sur n'importe quelle ligne de diff et renvoyez-les à l'agent — review, édition et commit sans quitter Orca. Docs →
Glisser-déposer vers les agents L'éditeur VS Code avec autosave partout — glissez fichiers ou images directement dans le prompt d'un agent. Docs →
Orca CLI Les agents pilotent aussi Orca — scriptez n'importe quel workflow avec `orca worktree create`, `snapshot`, `click` et `fill`. Docs →

Aussi dans la boîte :

Quick open — Cherchez parmi worktrees, fichiers, agents, commandes et contexte du repo sans quitter votre flow.
Sélecteur de comptes & suivi d'usage — Suivez l'usage Claude et Codex et les resets de rate limit, et basculez de compte à chaud sans vous reconnecter.
Aperçus riches du repo — Prévisualisez Markdown, images, PDF et docs du repo dans le workspace.
Computer Use — Laissez les agents piloter des apps desktop et l'UI visible quand un workflow demande une vraie interaction.
Notifications et non-lus — Sachez quand un agent termine ou a besoin d'attention, puis marquez des fils comme non lus pour y revenir plus tard.
Et bien plus encore — on ship tous les jours, donc cette liste est toujours en retard. Le changelog est la vraie liste des features.

Agents pris en charge

Fonctionne avec n'importe quel agent CLI — s'il tourne dans un terminal, il tourne dans Orca.

Claude Code Codex Grok Cursor GitHub Copilot Muse DeepSeek Harness ZCode OpenCode MiMo Code Amp OpenClaude Antigravity Pi oh-my-pi Hermes Agent Devin Goose Auggie Autohand Code Charm Cline Codebuff Command Code Continue Droid Kilocode Kimi Kiro Mistral Vibe Qwen Code Rovo Dev + n'importe quel agent CLI

Installation

Desktop — macOS, Windows, Linux

Télécharger depuis onOrca.dev
Ou récupérez un build directement : macOS Apple Silicon · macOS Intel · Windows (.exe) · Linux AppImage · Tous les builds
Sous Windows : utilisez la dernière RC (v1.4.147-rc.3) — elle inclut des correctifs Windows absents de la stable.
Vous lancez orca serve sur un serveur Linux headless ? Consultez le guide serveur Linux headless.

Ou via un gestionnaire de paquets :

# macOS (Homebrew)
brew install --cask stablyai/orca/orca

# Arch Linux (AUR) — ou stably-orca-git pour compiler depuis les sources
yay -S stably-orca-bin

Companion mobile — iOS, Android

Associez-la à l'app de bureau pour surveiller et piloter vos agents depuis votre téléphone.

iOS : Télécharger sur l'App Store ou rejoindre TestFlight
Android : Télécharger l'APK 0.0.50

Communauté & support

Discord : Rejoignez la communauté sur Discord.
Twitter / X : Suivez @orca_build pour les news et annonces.
WeChat : Scannez pour rejoindre le groupe WeChat 10 de la communauté Orca.
Feedback & idées : On ship vite. Il manque quelque chose ? Demandez une feature.
Confidentialité : Voir la doc confidentialité & télémétrie pour ce qu'Orca collecte en anonyme et comment désactiver la télémétrie.
Soutenez-nous : Mettez une star sur ce repo pour suivre nos ships quotidiens.

Développement

Envie de contribuer ou de lancer le projet en local ? Consultez notre guide CONTRIBUTING.md.

Builds signés

Signature de code Windows sponsorisée / fournie par SignPath.io, certificat par SignPath Foundation.

Licence

Orca est libre et open source sous la licence MIT.

18 KiB Raw Blame History

Orca

Télécharger Orca

Fonctionnalités

Companion mobile

Worktrees parallèles

Splits de terminal

Mode Design

GitHub & Linear, natifs

Worktrees SSH

Annoter les diffs IA

Glisser-déposer vers les agents

Orca CLI