This looks great! The slowness of the cold-start due to the number of API requests is still an issue, although it's mitigated by caching and parallelization. I wouldn't consider this to be a blocker.

Since we now output the OWNER/REPO#NUMBER syntax to identify individual PR & issue threads, I wonder whether it would be useful to provide facilities to use the same syntax as argument to other commands.

# note: this wouldn't work in bash or shells where `#` is strictly
# a comment character no matter where it appears
gh issue view cli/cli#123
gh browse cli/cli#123

Should we consider this as followup? I'm thinking this because I wonder what's the story for using gh to act on items that the user learned about through gh status.

This is really cool. I am seeing a weird UX issue with the vertical separator next to "Assigned PRs" in my terminal, both kitty and terminal.app. Seem likely it is a lipgloss bug but just wanted to point it out as we might see issues opened up around it.

Edit: After looking at this a bit more it is clear that the boarder is at the end of each line of the left column and my left column only has three lines so the boarder only displays on three lines. So it is not so much a bug as an artifact of me not having many assigned issues.

ok