oh-my-pr 4.3.6 → 4.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -59,6 +59,7 @@ Then:
59
59
  - Watches repositories and tracked PRs for review activity, comments, and failing checks
60
60
  - Triages feedback into actionable items
61
61
  - Runs `codex` or `claude` in isolated worktrees under `~/.oh-my-pr`
62
+ - Uses a bounded code-owner fallback after failed default babysitter runs so the resolved agent can inspect GitHub feedback, commit, and push when the primary automation path fails
62
63
  - Replies to GitHub PR comments on your behalf and resolves conversations to keep the thread clean
63
64
  - Pushes verified fixes back to the PR branch
64
65
  - Can automatically create a GitHub release when a merged PR is important enough to justify a version bump
@@ -98,6 +99,20 @@ oh-my-pr can be used in a few ways:
98
99
  - local REST API: see [LOCAL_API.md](LOCAL_API.md)
99
100
  - optional Tauri desktop shell
100
101
 
102
+ Local browser and API access work without a dashboard login. To use the web
103
+ dashboard from another machine, set remote web credentials before starting the
104
+ server:
105
+
106
+ ```bash
107
+ OH_MY_PR_WEB_USERNAME=operator \
108
+ OH_MY_PR_WEB_PASSWORD='choose-a-long-password' \
109
+ OH_MY_PR_SESSION_SECRET='choose-a-long-random-secret' \
110
+ oh-my-pr
111
+ ```
112
+
113
+ Remote API requests then require a signed dashboard session. Put TLS in front
114
+ of the server before using remote access over an untrusted network.
115
+
101
116
  ### Logging
102
117
 
103
118
  Server output is structured (pino) and goes to two destinations by default:
@@ -157,7 +172,9 @@ npm install
157
172
  npm run dev
158
173
  ```
159
174
 
160
- The dashboard is available at `http://localhost:5001` by default. All `/api/*` routes are restricted to loopback callers.
175
+ The dashboard is available at `http://localhost:5001` by default. Loopback API
176
+ requests work without login; remote dashboard/API access requires
177
+ `OH_MY_PR_WEB_USERNAME` and `OH_MY_PR_WEB_PASSWORD`.
161
178
 
162
179
  ## Docs
163
180