Public: anyone can read this; the crew can change it.
The terminal lists the teams of your organizations and who is in each, as the organization's Teams page does #8070
The terminal now has an "Organization teams" screen. It shows the teams of each organization you belong to and lets you see who is in each team, like / /-/teams. src/tui/screens/orgteams.ts (new): the palette entry org-teams (title "Organization teams", hint "who is in each team of your organizations").
stopped parked by the crew deploy dfece67
3 earlier comments
The terminal now has an "Organization teams" screen. It shows the teams of each organization you belong to and lets you see who is in each team, like /<org>/-/teams.
src/tui/screens/orgteams.ts(new): the palette entryorg-teams(title "Organization teams", hint "who is in each team of your organizations"). It is offered to anyone signed in whomlistOrgsForUserfinds in at least one organization. The list goes organization by organization, sorted by name. Each row shows a team,@org, its member count and the team's permission. Which teams appear is decided bylistTeamsVisibleTo, the same rule as the web page: an org admin sees every team, a member sees only their own. An organization with no team you can see shows "No teams you can see." Enter on a team opens its members (@usernameand display name, if set); esc goes back. No key adds or removes anyone.src/tui/screens/entries.ts: one import and one line, placingorgTeamsright afterteams.test/tui-org-teams.test.ts(new) covers four cases: an org admin sees Owners, Writers and Readers with member counts; a member sees only Writers; Enter shows the right members and esc returns; a person in no organization is not offered the entry. All four fail when the entry is taken out ofentries.ts.
Checks run here: bun scripts/gate.ts and bun x tsc --noEmit both pass. bun scripts/fast.ts named 244 test files, an estimated 20 minutes and over its 5-minute budget. Instead I ran the new test, the palette suites, tui-teams, pull-tui-teams and tui-asks-first: 54 tests, all passing. The full check runs on the push.
Not done here: adding and removing members from the terminal, which the issue leaves as a follow-up.
To try it: in the terminal, press ctrl-k, type "Organization teams", press Enter, then Enter on a team.
🤖 Generated with Claude Code
The terminal now has an "Organization teams" screen. It lists, for each organization you belong to, the teams you're allowed to see and how many people are in each, like /<org>/-/teams.
src/tui/screens/orgteams.ts(new): the palette entryorg-teams("Organization teams", hint "who is in each team of your organizations"). It is offered to anyone signed in whomlistOrgsForUserfinds in at least one organization.- Teams are grouped by organization, sorted by name, and each row shows
@org, the member count and the team's permission. - Which teams appear is decided by
listTeamsVisibleTo, the same rule as the web page: an org admin sees every team, a member only their own. An organization with no team you can see says "No teams you can see." - Enter on a team lists its members (
@usernameand display name); esc goes back. - It is read-only: no key adds or removes anyone.
- Teams are grouped by organization, sorted by name, and each row shows
src/tui/screens/entries.ts: one import and one line, puttingorgTeamsright afterteams.test/tui-org-teams.test.ts(new): checks that an org admin sees every team, a member sees only their own, Enter shows the right members and esc goes back, and someone in no organization isn't offered the entry. All four tests fail without the line inentries.ts.test/egress-admin.test.ts(the test was wrong): #8036 madexon the egress screen ask before revoking, but this test still expected the revoke to happen straight away. It now waits for the confirm and pressesy. The other egress failure in the check was the leftover grant from that test.
The tui-size failure ("issues at 60×20") is not from this change: that test opens the issues screen directly without the palette. It passed in three repeated runs here, so it looks like a timing flake on the check machine.
bun scripts/gate.ts and bun x tsc --noEmit pass. The new test passes, and so do the egress, tui-size, palette, teams and asks-first tests. I didn't run the whole suite here, because scripts/fast.ts named 244 files; the forge's check runs it on push.
Adding and removing members from the terminal is left for a follow-up.
To try it: ctrl-k, type "Organization teams", Enter, then Enter on a team.
🤖 Generated with Claude Code
The terminal now has an "Organization teams" screen. For each organization you belong to, it lists the teams you may see and how many people are in each, as the organization's Teams page does (/<org>/-/teams).
src/tui/screens/orgteams.ts(new) adds the palette entryorg-teams("Organization teams", hint "who is in each team of your organizations").- Who gets it: anyone signed in who belongs to at least one organization (
listOrgsForUser). - Which teams show:
listTeamsVisibleTodecides, the page's rule: an org admin sees every team, a member only their own. An organization with no team you can see shows "No teams you can see." - What a row shows:
@org, the member count and the team's permission, sorted by organization name. - Keys: Enter on a team lists its members (
@usernameand display name), and esc goes back. No key adds or removes anyone.
- Who gets it: anyone signed in who belongs to at least one organization (
src/tui/screens/entries.tsgets one import and one line, puttingorgTeamsright afterteams.test/tui-org-teams.test.ts(new) checks four things: an org admin sees every team, a member sees only their own, Enter shows the right members and esc goes back, and someone in no organization isn't offered the entry. All four fail without the line inentries.ts.test/egress-admin.test.tswas out of date after #8036 made revoke ask first. This branch andmainfixed it the same way: wait for the confirm, check the grant is still there, pressy. The merge keeps that, with my wait text, which names the app (Stop ada/arm reaching) and is more specific thanmain'sRevoke.
After merging main, bun scripts/gate.ts and bun x tsc --noEmit pass. So do tui-org-teams, egress-admin, palette-entries and tui-asks-first, 18 tests in all. I didn't run the full suite here because scripts/fast.ts names 244 files; the forge's check runs it on the push.
Adding and removing members from the terminal is left for a follow-up.
To try it: press ctrl-k, type "Organization teams", press Enter, then Enter on a team.
🤖 Generated with Claude Code
Parked by the crew: the check stayed red through 2 automatic tries
The terminal now has an "Organization teams" screen. It shows the teams of each organization you belong to and lets you see who is in each team, like
/<org>/-/teams.src/tui/screens/orgteams.ts(new): the palette entryorg-teams(title "Organization teams", hint "who is in each team of your organizations"). It is offered to anyone signed in whomlistOrgsForUserfinds in at least one organization. The list goes organization by organization, sorted by name. Each row shows a team,@org, its member count and the team's permission. Which teams appear is decided bylistTeamsVisibleTo, the same rule as the web page: an org admin sees every team, a member sees only their own. An organization with no team you can see shows "No teams you can see." Enter on a team opens its members (@usernameand display name, if set); esc goes back. No key adds or removes anyone.src/tui/screens/entries.ts: one import and one line, placingorgTeamsright afterteams.test/tui-org-teams.test.ts(new) covers four cases: an org admin sees Owners, Writers and Readers with member counts; a member sees only Writers; Enter shows the right members and esc returns; a person in no organization is not offered the entry. All four fail when the entry is taken out ofentries.ts.Checks run here:
bun scripts/gate.tsandbun x tsc --noEmitboth pass.bun scripts/fast.tsnamed 244 test files, an estimated 20 minutes and over its 5-minute budget. Instead I ran the new test, the palette suites,tui-teams,pull-tui-teamsandtui-asks-first: 54 tests, all passing. The full check runs on the push.Not done here: adding and removing members from the terminal, which the issue leaves as a follow-up.
To try it: in the terminal, press ctrl-k, type "Organization teams", press Enter, then Enter on a team.
🤖 Generated with Claude Code
Closes #7997