From e5c860b1435b5a801e0ca9585fc6d19d32c86db5 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 24 Sep 2026 22:49:04 +0000 Subject: [PATCH 1/2] Document agent-only commits and the workflows in use. The README now states that only agent-authored code is accepted, and describes cloud implementation, Bugbot fixes, desktop plans, and read-only explore runs. Co-authored-by: Dominic Letz --- README.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/README.md b/README.md index 0409165..8cacdcd 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,7 @@ # desktop_webview +> **No human commits are accepted in this project. Only agent code.** + Native desktop webview host for [elixir-desktop](https://github.com/elixir-desktop/desktop). The host is a stand-alone native binary per platform. It listens on localhost TCP and @@ -53,6 +55,31 @@ MyApp.app/ Host flags use the `--edw-*` prefix; all other argv is forwarded to the BEAM app. See [docs/packaging.md](docs/packaging.md). +## Agent development + +Implementation is done by Cursor agents. A commit is accepted only when it is +agent-authored (`Cursor Agent `). Humans file the task +and review the pull request; they do not land implementation commits. + +Four workflows are in use: + +| Workflow | Where it starts | What it produces | +|----------|-----------------|------------------| +| Cloud implementation | Cursor web or CLI cloud agent | Code on a `cursor/-` branch, commits, and a draft pull request | +| Bugbot fix | “Fix in Web” from a review comment on an open pull request | A follow-up commit on that pull request’s existing branch | +| Desktop plan | Cursor desktop, asked for a plan | An implementation plan only. No branch and no commits | +| Explore | Spawned by a parent agent | A read-only report. No branch and no commits | + +Cloud implementation follows [AGENTS.md](AGENTS.md): + +1. Read `AGENTS.md` and the docs the change touches (`docs/protocol.md`, packaging, porting, status). +2. Branch from the current base as `cursor/-`. +3. Change the protocol doc and both sides (Elixir and the native host) in the same change. Production methods do not depend on `test.*`. +4. Prove behavior with the shared Elixir suite: `mix test` for units, and `mix test.e2e` (or the platform job in [`.github/workflows/ci.yml`](.github/workflows/ci.yml)) against a built host. Mark a status-matrix row `done` only after that E2E covers it. +5. Commit, push, and open a draft pull request. Watch CI (Elixir unit, plus macOS, Linux, and Windows host E2E) and push follow-up commits until it is green. + +Bugbot fix uses the same rules on the branch that is already under review. Desktop plan and Explore stop before any commit. + ## Documentation - [Protocol](docs/protocol.md) — framing, methods, behavioral semantics, test RPC From c30db691d86e3fbc151b7d3f02533070fca8415b Mon Sep 17 00:00:00 2001 From: Dominic Letz Date: Fri, 25 Sep 2026 12:20:51 +0200 Subject: [PATCH 2/2] Revise agent development section in README Simplified the description of implementation authorship. --- README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/README.md b/README.md index 8cacdcd..59fefbe 100644 --- a/README.md +++ b/README.md @@ -57,9 +57,7 @@ See [docs/packaging.md](docs/packaging.md). ## Agent development -Implementation is done by Cursor agents. A commit is accepted only when it is -agent-authored (`Cursor Agent `). Humans file the task -and review the pull request; they do not land implementation commits. +Implementation is done by agents. Humans file the task and review the pull request; they do not land implementation commits. Four workflows are in use: