Public: anyone can read this; the crew can change it.

The terminal lists who a private app names and a writer adds or removes one after a plan, as MCP `app_members` does #7287

Closed opened this

Pull #7412 was closed · 2 runs

opened this

For: the owner handing a private app to a client: the client is let in by name, and today that needs a browser.

readAppMembers and setAppMembersThrough are reached from the app's settings and MCP app_members (src/http/mcp/tools/app_members.ts). No terminal screen calls them.

Done:

Files: src/tui/screens/appmembers.ts, the repository's command list, one test. Risk: low; reuse the action.

2 earlier comments
commented

Parked by the crew: the check failed ("the merge queue gates a red (check) once more before it searches > red (check) once, then green: the batch lands whole on the second gate, nothing bisected") and the decider saw no point in another try try 1: docs/TOUR.md, src/tui/forge.ts, src/tui/screens/appmembers.ts, test/tui-appmembers.test.ts try 2: CLAUDE.md, README.md, docs/APPS.md, docs/ARCHITECTURE.md (+160 more) (pull #7316 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

commented

Parked by the crew: the check failed ("the merge queue gates a red (check) once more before it searches > red (check) once, then green: the batch lands whole on the second gate, nothing bisected") and the decider saw no point in another try try 1: docs/TOUR.md, src/tui/forge.ts, src/tui/screens/appmembers.ts, test/tui-appmembers.test.ts (pull #7412 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

  1. the check failed ("the merge queue gates a red (check) once more before it searches > red (check) once, then green: the batch lands whole on the second gate, nothing bisected") and the decider saw no point in another try try 1: docs/TOUR.md, src/tui/forge.ts, src/tui/screens/appmembers.ts, test/tui-appmembers.test.ts try 2: CLAUDE.md, README.md, docs/APPS.md, docs/ARCHITECTURE.md (+160 more) (pull #7316 closed)
  2. the check failed ("the merge queue gates a red (check) once more before it searches > red (check) once, then green: the batch lands whole on the second gate, nothing bisected") and the decider saw no point in another try try 1: docs/TOUR.md, src/tui/forge.ts, src/tui/screens/appmembers.ts, test/tui-appmembers.test.ts (pull #7412 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

commented

replaced by #7418. Both tries went red on test/merge-queue-check-retry.test.ts, which passes alone on main and has nothing to do with this work. That test is now #7419. #7418 reaches the members screen from the deploys screen with m instead of a palette entry, so it does not name src/tui/forge.ts, which is in too many open pulls.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs