Activity feed
Real-time chat + GitHub events in one stream.
Back to use cases Pair without a screen-share.
Team Workflows
Pair without a screen-share.
Standup without a meeting.
Three engineers, three branches, one Slack channel that's mostly noise. Here's how teams actually collaborate inside Nest: terminal-first, async-friendly, and visible.
The problem
Your team's context is scattered across five windows
Slack for chat. Zoom for pair programming. GitHub for notifications. A Notion page for snippets nobody updates. A standup bot that everyone mutes. Every collaboration tool sits outside the place you actually write code, so context-switching has become the job. When you finally get back to the terminal, you've forgotten what your teammate was asking.
The workflow
Five steps. Zero context loss.
1
Open the team workspace
⌘K → type team → enter. The activity feed loads with GitHub events, chat messages and standups streaming in real time. Same window. Same keystrokes you already use.
team · activity feed · live raven
S sam.r · pushed 3 commits to feat/auth 2m
A alex.k · opened PR #812 · rate limiter v2 5m
R riley.b · merged feat/notifications 12m
CI github · checks passed on PR #812 14m
2
Pair on a bug, no screen-share
Hit ⌘⇧S in any pane and Nest gives you an 8-char share code. Drop it in chat. Your teammate types the code into their own Nest and now sees your terminal output as you type: read-only on their end, real-time on yours. No installs, no SSH, no Zoom.
alex.k · ~/raven-nest · pane 2
sharing · code A1B2-C3D4 · 2 viewers
~/raven-nest ❯ npm test -- auth.spec › vitest run auth.spec FAIL src/auth/auth.spec.ts × verifyToken rejects expired JWT Expected: 401 Received: 500 ~/raven-nest ❯ _
3
Push a snippet to the team
You wrote a great explain-this-stack-trace snippet last week. Right-click → Share with team. Now sam.r and riley.b can fire it from their own ⌘K: same prompt, same params, no copy-paste in Notion.
explain-this-stack-trace team
Paste any stack trace, get a 4-line summary with the most likely fix and the file:line to inspect first.
by alex.k · used 47× · ⌘K
4
Standup, in the activity feed
09:00 and the standup card appears pinned at the top of the team feed. Type your three lines. So does everyone else. No meeting, no Zoom fatigue, no waiting for the slowest joiner. Async PMs can read it later from the same feed.
Standup · Tue May 19 3 of 3 posted
A
alex.k 9:02am
rate limiter v2, finishing burst-window tests today
S
sam.r 9:05am
auth refactor in review, blocked on PR #812 merging first
R
riley.b 9:11am
notifications shipped, picking up onboarding flow next
5
Review with full context
Open a teammate's PR straight from the activity feed in a new pane. It opens with their branch already checked out as a worktree, dev server running on its own port, and an agent primed to answer questions about the diff. You comment inline, they see it in their feed.
PR #812 · rate limiter v2 · worktree :5174 +42 −18
src/middleware/rate-limit.ts @@ -14,7 +14,12 @@ const key = `rl:${req.ip}:${route}`; - const hits = await redis.incr(key); + const hits = await redis.incr(key); + if (hits === 1) { + await redis.expire(key, WINDOW_SEC); + } if (hits > LIMIT) return res.status(429).end();
S
sam.r inline · line 17
Race on the expire: if two requests hit at the same time, the second incr can land before expire and the key never gets a TTL. Use SET NX PX or pipeline this.
The outcome
Less Slack noise, fewer meetings, more shipped commits. Your team's context lives where your team's code lives.
What powers it
The team workspace, piece by piece
Terminal sharing
Share any pane with an 8-char code. Read-only or interactive.
Shared snippets
Team prompt library, version-controlled.
Built-in standup
Async daily check-in. No new tool.
Your AI workspace is waiting
Stop juggling tabs.
Start shipping.
Free during launch. No credit card. Works with the tools you already have, and the ones you didn't know you needed.
Local-first · No telemetry
macOS 13+ · Windows 10+ · Linux