Monitor Your Terminal From Anywhere: VS Code Extension

You kick off a Claude Code refactoring job. It’s going to take a while. You want to make coffee, check on the kids, or just sit somewhere more comfortable than your desk chair.

But you can’t. Because if Claude needs a permission, asks a question, or hits an error—you’ll miss it. The whole thing stalls until you get back.

This is the problem we built Pulse to solve. And today, we’re releasing the easiest way to use it: a VS Code extension that makes terminal monitoring completely invisible.

Zero friction for IDE users

If you live in VS Code, you shouldn’t have to change anything about your workflow. No wrapper scripts. No special terminals. No commands to remember.

Here’s what your day looks like with the Pulse extension:

Morning:

1. Open your VS Code project
2. Extension connects automatically (status bar shows ”● Pulse”)
3. Start Claude Code or any long-running task in the integrated terminal

From your iPad:

1. Open the Pulse dashboard
2. See your active session
3. Watch terminal output stream in real-time
4. Send a command if something needs attention

Back at your desk:

• Everything happened in your normal VS Code terminal
• No special commands, no wrapper scripts
• It just works

The extension uses VS Code’s terminal API to capture output as it happens. You don’t change how you work—you just gain the ability to watch from anywhere.

Two ways to capture, one dashboard

The VS Code extension is perfect for IDE users, but not everyone works that way. Maybe you’re SSH’d into a remote server. Maybe you prefer a standalone terminal. Maybe you’re running automation that doesn’t touch VS Code at all.

That’s why Pulse has two capture methods:

VS Code Extension

Best for: Daily coding in VS Code, AI agent supervision, pair programming

Just install and go. The extension handles everything.
Status bar shows connection state.
Every terminal tab is shareable.

CLI Daemon

Best for: Remote servers, standalone terminals, CI/CD pipelines

The CLI wraps any command or shell session, capturing output and streaming it to your dashboard. Perfect for when you’re SSH’d into a server or prefer working outside an IDE.

Both methods feed into the same dashboard. You can have VS Code sessions from your laptop, CLI sessions from a remote server, and see them all in one place on your iPad.

What it looks like in practice

Picture this on your iPad dashboard:

▼ webapp (VS Code)
  ● Claude refactoring auth module...

▼ api-server (SSH)
  ● npm run dev - Server running on :3000

▼ scripts (VS Code)
  ○ idle

Three sessions from two different sources. The dashboard doesn’t care where they originate—they all appear the same way.

The green dot means active output. Yellow means idle. Grey means the session ended. You can drill into any session to see the full terminal output, scrollback and all.

Remote commands when you need them

Watching is great, but sometimes you need to act. Maybe Claude is asking a question. Maybe your dev server crashed and needs a restart. Maybe you just want to run git status to see what’s changed.

From the dashboard, you can send commands directly to any active session:

1. Tap the session
2. Type your command
3. It executes in the real terminal
4. Output streams back to you

The command runs exactly as if you typed it at your desk. For Claude Code sessions, this means you can approve permissions, answer questions, or course-correct—all from your couch.

Session states

Sessions have a simple lifecycle:

State	What it means	Can send commands?
Active	Output streaming, green dot	Yes
Idle	No output for 5+ minutes, yellow dot	Yes
Closed	Terminal closed, grey	No

Even idle sessions stay connected. If you walk away and your build finishes, you’ll see it when you check back. The session only closes when you close the terminal or stop the daemon.

Why this matters

The shift to AI-assisted development has created a new problem: supervision. Claude Code can work for 10, 20, 30 minutes at a stretch—but it still needs human input at key moments.

Before Pulse, your options were:

• Stay at your desk and watch
• Walk away and hope nothing needs you
• Check back constantly, interrupting whatever else you’re doing

Now you can actually step away. Get a notification when something needs attention. Check in from wherever you are. Send a command and keep things moving.

The VS Code extension makes this as frictionless as possible. You don’t adopt a new workflow—you just gain superpowers for the workflow you already have.

---

Join the waitlist at pulsevibe.dev to be notified when we launch.