@nanocollective/roster 0.1.0-beta.27 → 0.1.0-beta.29
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/dist/worker/index.js +206 -16
- package/docs/hosting.md +12 -3
- package/docs/security.md +3 -1
- package/package.json +1 -1
- package/templates/ops/.github/workflows/session.yaml +18 -0
package/docs/hosting.md
CHANGED
|
@@ -71,6 +71,10 @@ CMO to draft this week's post". The tools:
|
|
|
71
71
|
| `run` | Starts a staff member's session now, or one of their routines |
|
|
72
72
|
| `runs` | Recent runs: how each went, how long, what it cost, and its log |
|
|
73
73
|
| `read_brain` | `STATE.md`, `CHARTER.md`, `memory/INDEX.md`, `log/decisions.md` or `staff.yaml` |
|
|
74
|
+
| `read_pr` | A pull request to review: checks, conflicts, review state, commits and the diff |
|
|
75
|
+
| `approve` | An approving review, as you |
|
|
76
|
+
| `merge` | Merges a pull request, only when you have told it to |
|
|
77
|
+
| `wait` | Waits up to ten minutes for a staff member's reply on a thread, or for their run to finish |
|
|
74
78
|
|
|
75
79
|
The Connectors screen has the line to paste for Claude Code, Codex and Claude, under **Connect
|
|
76
80
|
your own agent**. From Claude Code:
|
|
@@ -82,11 +86,16 @@ claude mcp add --transport http roster-acme https://roster.acme.com/mcp
|
|
|
82
86
|
then `/mcp` to sign in. With more than one Roster, give each its own name (`roster-acme`,
|
|
83
87
|
`roster-globex`): an agent keeps each server's tools apart by that name.
|
|
84
88
|
|
|
85
|
-
|
|
86
|
-
|
|
89
|
+
So with half an hour spare you can work through the brief with your agent: answer the asks,
|
|
90
|
+
read and merge the pull requests, ask for the next thing and wait for the answer, without
|
|
91
|
+
waiting for the daily run.
|
|
92
|
+
|
|
93
|
+
It merges only when you tell it to: the tool asks for your words, and Claude Code asks you
|
|
94
|
+
before the call. It cannot hire, retire or change the org: those stay local. Everything it
|
|
95
|
+
posts is posted as you.
|
|
87
96
|
|
|
88
97
|
Nothing to set up beyond the portal itself: the connector signs in through the same OAuth App,
|
|
89
|
-
on
|
|
98
|
+
on the same callback URL (`/auth/callback`).
|
|
90
99
|
|
|
91
100
|
## Deploying it
|
|
92
101
|
|
package/docs/security.md
CHANGED
|
@@ -170,7 +170,9 @@ access token lasts an hour and a refresh token thirty days. Each connection sign
|
|
|
170
170
|
separately, so signing out of the portal does not disconnect Claude; revoking the OAuth App on
|
|
171
171
|
GitHub disconnects both, and rotating `SESSION_KEY` disconnects every connector. A code is not
|
|
172
172
|
single use, since there is no store to remember it in, but it lasts five minutes and is useless
|
|
173
|
-
without the PKCE verifier only the client holds. The tools
|
|
173
|
+
without the PKCE verifier only the client holds. The tools can approve and merge, which the
|
|
174
|
+
person's own token could do on GitHub anyway; the merge tool is marked destructive, so a client
|
|
175
|
+
asks before calling it, and takes the person's words telling it to. They cannot hire or change
|
|
174
176
|
the org.
|
|
175
177
|
|
|
176
178
|
**The OAuth scopes.** `repo`, `notifications` and `workflow`. A GitHub App would be narrower,
|
package/package.json
CHANGED
|
@@ -407,6 +407,24 @@ jobs:
|
|
|
407
407
|
ROSTER_CONNECTORS: ${{ steps.connectors.outputs.file }}
|
|
408
408
|
run: node roster-ops/agents.mjs --staff "${{ inputs.staff }}" --ops roster-ops --brains . >> "$GITHUB_OUTPUT"
|
|
409
409
|
|
|
410
|
+
# On a pull request the action treats its working directory as the PR's checkout: it
|
|
411
|
+
# re-points `origin`, runs `git diff HEAD` and restores .claude/ and CLAUDE.md from the
|
|
412
|
+
# base branch. Here the working directory is the workspace root, which holds the checkouts
|
|
413
|
+
# but is not one, so its git calls fail and the run dies before the agent starts. An empty
|
|
414
|
+
# repo with one commit and an `origin` gives it something to work on. Every path is
|
|
415
|
+
# ignored, so the checkouts inside it never show as untracked. Nothing from the PR is at
|
|
416
|
+
# the root, so the restore has nothing to protect against.
|
|
417
|
+
- name: Give the action a repo to work in
|
|
418
|
+
if: steps.agent.outputs.kind == 'action' && (github.event.issue.pull_request || github.event.pull_request)
|
|
419
|
+
run: |
|
|
420
|
+
set -euo pipefail
|
|
421
|
+
[ -d .git ] && exit 0
|
|
422
|
+
git init --quiet
|
|
423
|
+
echo '*' >> .git/info/exclude
|
|
424
|
+
git -c user.name=roster -c user.email=roster@users.noreply.github.com \
|
|
425
|
+
commit --quiet --allow-empty -m "workspace root"
|
|
426
|
+
git remote add origin "https://github.com/${{ github.repository }}.git"
|
|
427
|
+
|
|
410
428
|
# `uses:` cannot be an expression, so an Action-based runner has to be written out
|
|
411
429
|
# literally. This is the reference one; every other agent goes through the step below.
|
|
412
430
|
- name: Run the session
|