Skip to content
Back to search

dely

Multi-harness control protocol that turns requests into approved design contracts, orchestrating isolated worker sessions for sequential implementation and independent code reviews under Orca supervision for Claude Code, Codex, Cursor, Antigravity, and other AI coding agents.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hieuphung97--dely/badge.svg)](/listings/hieuphung97--dely)

HTML

<a href="/listings/hieuphung97--dely"><img src="/api/listings/hieuphung97--dely/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. [Install Orca](#install-orca). 2. [Install Dely](#install-dely) in the harness you will talk to. 3. Open that harness in your project. Run `dely:setup` to choose which harness and model run each role, or use the project's existing pins. If no pin names a phase, it runs on Control's harness. 4. Ask for a change.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "dely",
  3. "description": "An automation-first, Orca-supervised delivery protocol for coding agents.",
  4. "owner": {
  5. "name": "Hieu Phung",
  6. "url": "https://github.com/hieuphung97"
  7. },
  8. "plugins": [
  9. {
  10. "name": "dely",
  11. "description": "An automation-first, Orca-supervised delivery protocol for coding agents.",
  12. "source": "./",
  13. "category": "productivity"
  14. }
  15. ]
  16. }
README.md · README · 328 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # dely
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset="assets/logo.svg">
  4. <img src="assets/logo-light.svg" alt="dely" width="72" height="72">
  5. </picture>
  6. Ask for a change; Dely takes it through design approval, implementation,
  7. independent review, and a pull request you merge.
  8. https://github.com/user-attachments/assets/83ec539a-6551-4807-8517-0c73e5d171d7
  9. [YouTube](https://www.youtube.com/watch?v=6pRWkhlQSAc)
  10. ## Contents
  11. - [Quickstart](#quickstart)
  12. - [How Dely works](#how-dely-works)
  13. - [Choose a harness for each role](#choose-a-harness-for-each-role)
  14. - [Install Orca](#install-orca)
  15. - [Install Dely](#install-dely)
  16. - [Configure a project](#configure-a-project)
  17. - [Log](#log)
  18. - [Troubleshooting](#troubleshooting)
  19. ## Quickstart
  20. 1. [Install Orca](#install-orca).
  21. 2. [Install Dely](#install-dely) in the harness you will talk to.
  22. 3. Open that harness in your project. Run `dely:setup` to choose which harness
  23. and model run each role, or use the project's existing pins. If no pin names
  24. a phase, it runs on Control's harness.
  25. 4. Ask for a change.
  26. ## How Dely works
  27. You ask. Control designs. You approve. The implementer builds. The reviewer
  28. checks. Control opens the pull request. You merge.
  29. **Control** is the session you talk to. It writes the design, waits for your
  30. approval, starts the other two sessions, and opens the pull request. Install
  31. Dely here.
  32. **Implementer** is a session Control starts to make the change.
  33. **Reviewer** is a session Control starts to check the change independently
  34. before the pull request. The implementer and the reviewer are the workers.
  35. A Spike investigates only — no delivery run. One that dispatches workers opens its own Orca Run and keeps their files in that Run's folder.
  36. ## Choose a harness for each role
  37. Before the first delivery in a project, open each harness you chose there once
  38. and answer its trust question. Setup opens them for you. Claude Code needs no
  39. such step on Orca 1.4.220 and later, which by default trusts the folder when
  40. it starts Claude; with Orca's "Trust the folder when Orca starts an agent"
  41. setting off, or a failed trust write, Claude still asks and the preflight
  42. failure names the dialog. OMP has no trust question; Pi asks only when the project or a parent folder has `.pi/` or
  43. `.agents/skills`.
  44. ✓ works · ⚠ works, read the note · ✗ not supported
  45. | Harness | Control | Implementer | Reviewer | Watch out for |
  46. | --- | --- | --- | --- | --- |
  47. | Claude Code | ✓ | ✓ | ✓ | Put @AGENTS.md in CLAUDE.md. |
  48. | Codex CLI | ⚠ | ✓ | ✓ | Use Codex CLI 0.159.2 or newer with Orca 1.4.217 or newer. As Control, it can start the next Dely step before the last one finishes. |
  49. | Grok Build | ⚠ | ⚠ | ⚠ | Answer the trust question once in every project. As a worker, you cannot choose the model. As Control, a free account ran out of usage mid-delivery. |
  50. | Antigravity CLI | ✓ | ⚠ | ⚠ | Choose the effort through the model name. Avoid gemini-3-flash-preview. As a worker, the first launch in a new folder can lose the task and show 'not signed in' while signed in; Dely retries once, then asks you to open agy there. |
  51. | Kiro CLI | ✗ | ✗ | ✗ | Workers never start in Orca. |
  52. | Cursor Agent CLI | ✓ | ✓ | ✓ | Choose the effort through the model name, for example cursor-grok-4.6-high. |
  53. | GitHub Copilot CLI | ✓ | ⚠ | ⚠ | At the first launch, answer No, thanks to the app prompt; until then a launch can leave the task unsent. Answer the folder trust question once in every project and choose to remember the folder; Orca does not see it, so a missed one shows as NO_ACK. As a worker, you cannot choose the model. |
  54. | OMP | ⚠ | ⚠ | ⚠ | It never asks for trust, so use it only in repositories you trust. As a worker, use Orca 1.4.224 or newer, which does not show OMP's status (stablyai/orca#24436), so Dely reports a working OMP worker as needing attention. As Control, run dely wait with your largest job timeout (3600 s); a shorter timeout kills the wait before it ends. |
  55. | Pi | ⚠ | ⚠ | ⚠ | As Control, run Dely's commands with no time limit. As a worker, to pin a model, install Dely in Pi, then check the model in Pi's session log. |
  56. Other agents Orca can launch may work too;
  57. [`harnesses.json`](harnesses.json) records what was measured.
  58. ## Install Orca
  59. Orca runs each session and launches the workers.
  60. 1. Install the [desktop app](https://www.onorca.dev/docs/install).
  61. 2. Register the CLI: Settings → General → Orca CLI. See the
  62. [CLI overview](https://www.onorca.dev/docs/cli/overview).
  63. 3. Enable orchestration: Settings → Experimental. See
  64. [orchestration](https://www.onorca.dev/docs/cli/orchestration).
  65. 4. Check it:
  66. ```bash
  67. orca open
  68. orca status --json
  69. orca orchestration run-list --json
  70. ```
  71. On Linux, the binary is `orca-ide`.
  72. ## Install Dely
  73. **Install Dely only in the harness you use as the Control session.** A harness
  74. used only as implementer or reviewer needs Orca and its own login. Workers
  75. read no Dely skill. **A pinned Pi worker also needs that harness's
  76. Dely install below**, which loads `dely-pin.ts`.
  77. Have Node 18 or newer on PATH. Open Control in your project and ask for a
  78. change using `dely:delivery`. To choose the implementer and reviewer, run
  79. `dely:setup` first; see [Configure a project](#configure-a-project). If no pin
  80. names a phase, it runs on Control's harness with its default model and effort.
  81. Use the invocation spelling listed below for your harness.
  82. ### Claude Code
  83. ```bash
  84. claude plugin marketplace add https://github.com/hieuphung97/dely.git
  85. claude plugin install dely@dely
  86. claude plugin list # verify
  87. claude plugin update dely # update; restart to apply
  88. claude plugin uninstall dely # remove
  89. ```
  90. Put `@AGENTS.md` in `CLAUDE.md` so Claude reads the routing line setup adds.
  91. Invoke `/dely:delivery` or `/dely:setup`.
  92. ### Codex CLI
  93. ```bash
  94. codex plugin marketplace add https://github.com/hieuphung97/dely.git
  95. codex plugin add dely@dely
  96. codex plugin list # verify
  97. codex plugin marketplace upgrade # update; open a new session
  98. codex plugin remove dely@dely # remove
  99. ```
  100. If add keeps a stale marketplace, remove the marketplace and plugin, then add
  101. again. Pin a tag or full commit SHA with
  102. `codex plugin marketplace add --ref <ref> https://github.com/hieuphung97/dely.git`.
  103. Do not use `codex plugin install`.
  104. Invoke `$delivery (dely:delivery)` or `$setup (dely:setup)`.
  105. ### Cursor Agent CLI
  106. ```bash
  107. cursor-agent plugin marketplace add https://github.com/hieuphung97/dely.git
  108. cursor-agent plugin marketplace list # verify marketplace
  109. cursor-agent plugin marketplace update dely # re-index only; does not fetch
  110. cursor-agent plugin marketplace remove dely # remove marketplace only
  111. ```
  112. In a session, open `/plugin` → Marketplace → dely → Install for you.
  113. To update, remove and re-add the marketplace, then uninstall and reinstall
  114. Dely in `/plugin`. To remove Dely, use `/plugin` → Installed → dely → Uninstall.
  115. Type `/dely` to find `/delivery` and `/setup`. Local snapshot installs are
  116. unavailable; Cursor can read the Claude plugin cache.
  117. ### GitHub Copilot CLI
  118. ```bash
  119. copilot plugin install https://github.com/hieuphung97/dely.git
  120. copilot plugin install /path/to/dely # local alternative
  121. copilot skill list # verify delivery and setup
  122. copilot plugin update dely # update git or local install
  123. copilot plugin uninstall dely # remove
  124. ```
  125. Invoke `/dely:delivery` or `/dely:setup`. Direct installs print a deprecation
  126. warning. A same-named project or personal skill can hide the plugin skill.
  127. ### Antigravity CLI
  128. ```bash
  129. agy plugin install https://github.com/hieuphung97/dely.git
  130. agy plugin install /path/to/dely # local alternative
  131. agy plugin list # verify dely with skills
  132. agy plugin install https://github.com/hieuphung97/dely.git # update git install
  133. agy plugin uninstall dely # remove
  134. ```
  135. There is no plugin update subcommand. Re-run install with the same target to
  136. update. Invoke `/dely:delivery` or `/dely:setup`.
  137. ### Grok Build
  138. ```bash
  139. grok plugin install https://github.com/hieuphung97/dely.git --trust
  140. grok plugin install /path/to/dely --trust # local alternative
  141. grok plugin details dely # verify
  142. grok inspect # verify loaded delivery and setup
  143. grok plugin update dely # update git install
  144. grok plugin uninstall dely # remove
  145. ```
  146. For a local install, uninstall then install again; update does not re-copy.
  147. Invoke `/delivery` or `/setup`. Grok also loads Claude Code plugins; its own
  148. copy wins. To stop loading Dely completely, remove both copies if present.
  149. ### OMP
  150. Use a dedicated clone or an unpacked snapshot; install links the source path.
  151. ```bash
  152. git clone https://github.com/hieuphung97/dely.git
  153. omp plugin install /path/to/dely
  154. omp plugin list --json # verify the install (Control only; OMP workers need none)
  155. omp skill list --json # verify loaded skills
  156. omp plugin uninstall dely # remove; needs bun on PATH
  157. omp plugin disable dely # disable skills and extension
  158. ```
  159. Update by pulling the dedicated clone, then opening a new OMP session.
  160. Without bun, disable Dely; delete `~/.omp/plugins/node_modules/dely`, remove
  161. the empty `node_modules` directory, and delete `.plugins.dely` from
  162. `~/.omp/plugins/omp-plugins.lock.json`. Invoke `delivery` or `setup` without
  163. namespacing. OMP has no workspace-trust gate; only use trusted repositories.
  164. ### Pi
  165. ```bash
  166. pi install git:github.com/hieuphung97/dely@v<version>
  167. pi install /path/to/dely # local alternative
  168. pi list # verify
  169. pi --verbose # verify loaded paths at startup
  170. pi remove git:github.com/hieuphung97/dely@v<version>
  171. pi remove /path/to/dely # remove local install
  172. ```
  173. Find `<version>` in [releases](https://github.com/hieuphung97/dely/releases).
  174. Update by installing the new tag. At startup, check that Skills names
  175. `delivery` and `setup`, and Extensions names `dely-pin.ts`.
  176. Invoke `/skill:delivery` or `/skill:setup`. Check a pinned worker's model in
  177. `~/.pi/agent/sessions/`.
  178. Checked versions (observations, not minimums): Orca 1.4.218, 1.4.220, 1.4.224 (OMP and Pi worker), 1.4.247; Claude Code
  179. 2.1.286; Codex CLI 0.159.3; Cursor Agent CLI 2026.09.28-64d2043; Copilot CLI
  180. 1.0.89; Antigravity CLI 1.2.13 (install), 1.2.14 (worker, Control); Grok
  181. Build 1.0.44; OMP 18.4.8 (Control), 18.6.1 (worker); Pi 0.99.1, 1.0.2.
  182. ## Configure a project
  183. Pins say which harness, model and effort run the implementer and the reviewer.
  184. Run `dely:setup` in Control. It asks whether the choice is for the team or only
  185. for you, then writes one of two files:
  186. - `.dely/pins.json` holds team pins. Commit it.
  187. - `.dely/local/pins.json` holds your own pins. It is never committed.
  188. Both files look like this:
  189. ```json
  190. {
  191. "implement": { "harness": "claude", "model": "default", "effort": "default" },
  192. "review": { "harness": "codex", "model": "default", "effort": "default" }
  193. }
  194. ```
  195. `harness` is an id from [`harnesses.json`](harnesses.json), such as `claude` or
  196. `codex`, not the display name. Use `default` to leave the model or effort to
  197. the harness. A file can name just one phase.
  198. Dely picks a pin for each phase on its own. Your file wins, then the team file,
  199. then Control's own harness with its defaults. If your file pins only
  200. `review`, Dely uses the team's `implement` pin when there is one. Otherwise it
  201. uses Control's harness and defaults.
  202. In another worktree of the same clone, Dely looks for your file in that
  203. worktree first, then in the main checkout.
  204. `.dely/local/` has its own `.gitignore` holding `*`, so nothing in it shows in
  205. `git status`; `dely dispatch` writes it when absent and leaves an existing one alone.
  206. `git clean -fdx` deletes it, personal pins included.
  207. `.dely/local/runs/<run>/` holds every prompt and handoff of one Orca Run;
  208. `dely dispatch` refuses a prompt anywhere else. The files stay until the run
  209. closes, when Control deletes the folder and `dely log` records anything left
  210. there as `residue`; `null` with a `residueError` means part of the folder could
  211. not be read.
  212. To see what is in use, ask Control to run `dely pins --repo <path>`. It prints
  213. each phase's harness, model, effort and source (`local`, `team` or `control`).
  214. ### Upgrading from 0.23
  215. Version 0.23 kept the pins in a `<!-- dely:begin -->` block in `AGENTS.md`.
  216. Dely no longer reads that block. Run `dely:setup` to move the table to
  217. `.dely/pins.json` and replace the block with one routing line in `AGENTS.md`.
  218. ## Log
  219. `~/.dely/log.jsonl` is machine-local JSON Lines, one object per line. It
  220. is off unless `~/.dely/` exists; `mkdir ~/.dely` turns it on, and Dely
  221. never creates that directory. A missing directory means nothing is
  222. written and nothing is created.
  223. The file may contain sensitive content. It quotes worker screen output
  224. in full, so it can hold repository contents, error text, and whatever a
  225. harness printed.
  226. ## Troubleshooting
  227. - **Worker stays at startup:** read its screen. Answer shell startup prompts
  228. such as an oh-my-zsh update, then retry.
  229. - **Orca disconnects:** reopen Orca, check the commands under Install Orca,
  230. and inspect workers with `orca orchestration worker-list --run <run>`
  231. before retrying.
  232. - **First launch stops at trust:** open that harness in the same path and
  233. answer its dialog, then retry. Copilot can report only `NO_ACK`, and its
  234. first launch also shows an app promo: answer No, thanks once;
  235. Antigravity can lose the prompt on a new path; retry once. Pi asks when
  236. the path or an ancestor has `.pi/` resources or `.agents/skills`.
  237. - **Worker tab stays open:** Dely releases each worker when its `worker_done`
  238. settles and again at close. A tab you typed or pasted into is yours, so
  239. Orca keeps it (`retained`, `user_takeover`); close it yourself. Answer a
  240. harness dialog by opening that harness in the same path (as the trust
  241. bullet says), not in the worker tab.
  242. - **Codex helper says "not inside an Orca terminal":** ask Control to look up
  243. its handle with `orca terminal list --worktree active --json` only when
  244. that worktree has one agent terminal, then prefix helper and `orca` commands
  245. with `ORCA_TERMINAL_HANDLE=<handle>`. Otherwise, use another Control harness.
  246. Never use another pane's handle.
  247. - **Old behavior after update:** open a new Control session. Ask Control to run
  248. its `scripts/dely` with no arguments to identify the running copy. Compare
  249. `skills/delivery/SKILL.md` by SHA-256 at every skill location, including
  250. `~/.agents/skills`, project and personal skills, plugin caches and
  251. marketplace sources; update or remove mismatched copies.
  252. Codex personal skills can shadow plugins; Cursor copies can override the
  253. Claude cache; Copilot project and personal skills can hide its plugin.
  254. [Workflow contract](skills/delivery/SKILL.md) ·
  255. [Contributing](CONTRIBUTING.md) · [Code of conduct](CODE_OF_CONDUCT.md) ·
  256. [Security](SECURITY.md) · [Decisions](docs/decisions.md) · [MIT](LICENSE)
probe/trust.sh · Bundled script · 121 lines · 1 finding marked
  1. #!/bin/bash
  2. # Pre-trust Claude Code at a probe path for the parameterized rows of
  3. # probe/checklist.md: open the harness in an Orca terminal, answer its own trust
  4. # dialog, and verify the answer in the harness's store. An Orca terminal opened
  5. # this way is not an agent start, so the dialog still appears. By default, Orca
  6. # 1.4.220 and later trust the folder themselves when they start a Claude Code
  7. # worker; with their "Trust the folder when Orca starts an agent" setting off,
  8. # or a failed trust write, the worker still shows it.
  9. #
  10. # Usage: probe/trust.sh <repo path under ~/dely-probe> [harness]
  11. #
  12. # Only `claude` is supported, because its store key is the one that has been
  13. # measured. For any other harness, answer the dialog by hand: a script that
  14. # reports success from the screen is worse than no script. The earlier probe
  15. # script did exactly that, twice, while `hasTrustDialogAccepted` stayed false,
  16. # and the delivery then failed its second preflight for the first reason.
  17. #
  18. # Dely itself never answers a dialog. This is probe tooling, it is not shipped
  19. # in the skill, and no skill references it.
  20. set -eu
  21. ROOT="$HOME/dely-probe"
  22. target=${1-}
  23. harness=${2-claude}
  24. if [ -z "$target" ]; then
  25. echo "usage: probe/trust.sh <repo path under ~/dely-probe> [harness]" >&2
  26. exit 2
  27. fi
  28. if [ ! -d "$target" ]; then
  29. echo "REFUSED $target is not a directory" >&2
  30. exit 2
  31. fi
  32. repo=$(cd "$target" && pwd -P)
  33. # Hard limit: this script only ever opens a harness on a path under
  34. # ~/dely-probe/. It is checked after resolving symlinks and `..`, and before
  35. # anything is created.
  36. case "$repo/" in
  37. "$ROOT"/*) ;;
  38. *) echo "REFUSED $repo is not under $ROOT/" >&2; exit 2 ;;
  39. esac
  40. if [ "$harness" != claude ]; then
  41. echo "REFUSED harness '$harness' has no measured store key; answer its dialog by hand" >&2
  42. exit 2
  43. fi
  44. store="$HOME/.claude.json"
  45. trusted() {
  46. node -e '
  47. const fs = require("fs");
  48. try {
  49. const j = JSON.parse(fs.readFileSync(process.argv[1], "utf8"));
  50. const p = (j.projects || {})[process.argv[2]] || {};
  51. process.exit(p.hasTrustDialogAccepted === true ? 0 : 1);
  52. } catch (e) {
  53. process.exit(1);
  54. }
  55. ' "$store" "$repo"
  56. }
  57. if trusted; then
  58. echo "TRUSTED $repo already; no terminal opened"
  59. exit 0
  60. fi
  61. handle=$(orca terminal create --worktree "path:$repo" --title "probe-trust" \
  62. --command "claude --dangerously-skip-permissions" --json |
  63. node -e 'let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{try{process.stdout.write(((JSON.parse(s).result||{}).terminal||{}).handle||"")}catch(e){}})')
  64. if [ -z "$handle" ]; then
  65. echo "NOT_TRUSTED $repo terminal create returned no handle" >&2
  66. exit 1
  67. fi
  68. cleanup() { orca terminal close --terminal "$handle" --json >/dev/null 2>&1 || true; }
  69. trap cleanup EXIT
  70. # --screen renders the frame. Without it a read returns accumulated output,
  71. # which a TUI leaves as stacked fragments, and an empty tail once a previous
  72. # read has consumed the cursor.
  73. screen() {
  74. orca terminal read --terminal "$handle" --screen --json |
  75. node -e 'let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{try{process.stdout.write((((JSON.parse(s).result||{}).terminal||{}).tail||[]).join("\n"))}catch(e){}})'
  76. }
  77. # Claude has reworded this dialog at least once, so match several of its parts
  78. # rather than one sentence. This only decides when to answer; whether the answer
  79. # took is decided by the store, below.
  80. dialog='do you trust|trust the files|quick safety check|security guide|no, exit'
  81. seen=
  82. for _ in $(seq 1 30); do
  83. if screen | grep -qiE "$dialog"; then seen=1; break; fi
  84. sleep 2
  85. done
  86. if [ -z "$seen" ]; then
  87. echo "NOT_TRUSTED $repo no trust dialog appeared in 60 s; last screen: $(screen | tail -5 | tr '\n' ' ')" >&2
  88. exit 1
  89. fi
  90. # The cursor can sit on the refusing choice, so move up before confirming.
  91. answer() {
  92. orca terminal send --terminal "$handle" --text $'\x1b[A' --json >/dev/null
  93. sleep 1
  94. orca terminal send --terminal "$handle" --text $'\r' --json >/dev/null
  95. sleep 6
  96. }
  97. answer
  98. if ! trusted; then
  99. answer
  100. fi
  101. if trusted; then
  102. echo "TRUSTED $repo verified in $store"
  103. exit 0
  104. fi
  105. echo "NOT_TRUSTED $repo dialog was answered but $store still reports hasTrustDialogAccepted false; last screen: $(screen | tail -5 | tr '\n' ' ')" >&2
  106. exit 1

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.