StreamView Documentation

Multi-terminal viewer for Windows developers

Getting Started

Installation

Microsoft Store (Recommended)

  1. Open the Microsoft Store and search for "StreamView"
  2. Click Install
  3. Launch StreamView from the Start menu

Sideload

  1. Download the latest .msix from the downloads page
  2. Double-click to install
  3. Launch StreamView from the Start menu

Quick Start

  1. Add a terminal — Click + Add Stream in the tab bar or press Ctrl+N
  2. Choose a shell — Select PowerShell, Command Prompt, WSL, or any Windows Terminal profile
  3. Arrange your layout — Use the layout buttons: Grid, Main+Sidebar, Rows, or Single
  4. Work across terminals — Click stream tabs to switch focus between panes

Layouts

StreamView offers four layout modes to organize your terminals:

Grid

Equal-sized panes in rows and columns. Best for monitoring multiple similar processes.

Main + Sidebar

One large pane with smaller sidebar. Best for primary task with background monitors.

Rows

Horizontal strips stacked vertically. Best for log monitoring and tailing.

Single

Full-screen single terminal. Best for focused work or reading output.

Switch layouts using the buttons in the toolbar. Your layout preference is saved per workspace.

Workspaces

Organize related terminals into workspaces — one for each project or task. Each workspace maintains its own streams and layout independently.

  • Create: Click + next to workspace tabs
  • Rename: Double-click a workspace tab
  • Switch: Click workspace tabs
  • Delete: Right-click a workspace tab

Managing Streams

Adding Streams

  • Click + Add Stream in the tab bar, or press Ctrl+N
  • Choose from detected Windows Terminal profiles, custom saved streams, or create a new stream
  • Your default shell (configurable in Settings) appears first in the list

Right-Click Menu

  • Right-click a stream tab — Duplicate or Remove the stream
  • Right-click the tab bar — Quick-add a new stream from the profile menu

Stream Profiles

Save frequently used terminal configurations as reusable profiles:

  1. Open Settings > Streams
  2. Click + Create New Stream
  3. Set the name, command, working directory, and accent color
  4. Launch saved profiles from the add-stream menu or the Welcome screen

Session Persistence

StreamView auto-saves your session every 30 seconds and when the app closes:

  • Open terminals and their positions
  • Workspace configurations
  • Layout preferences
  • Window size and position

Everything restores automatically on next launch. Two settings control this in Settings > General > Startup:

  • Restore on launch — Restores workspaces and stream layout from the last session
  • Auto-start streams on restore — When enabled, terminal processes start automatically. When disabled, only the layout is restored and you click play to start each stream individually.

Keyboard Shortcuts

Navigation

Shortcut Action
Ctrl+1-9 Switch to stream 1-9
Ctrl+N Add new stream
Ctrl+W Close current stream
Ctrl+, Open settings

View

Shortcut Action
F11 Toggle fullscreen
Escape Exit fullscreen
Ctrl+Enter Toggle fullscreen (alt)
Ctrl+] Rotate streams forward
Ctrl+[ Rotate streams backward

Zoom

Shortcut Action
Ctrl++ Zoom in
Ctrl+- Zoom out
Ctrl+0 Reset zoom
Ctrl+Scroll Zoom with mouse wheel

Scrollback

Shortcut Action
Mouse Wheel Scroll through history
Shift+PageUp/Down Page through history
Shift+Home Jump to start of buffer
Shift+End Jump to end (live)

Settings

Access settings via Ctrl+, or the gear icon.

General

Setting Description
Start with WindowsLaunch StreamView on login
Restore on launchRestore workspaces and stream layout from last session
Auto-start on restoreAutomatically start terminal processes when restoring
Default shellShell used for new terminals when no profile is selected
Buffer sizeScrollback line count (5,000-50,000)
Auto-check updatesCheck for new versions on startup

Appearance

Setting Description
ThemeDark, Light, or High Contrast
Terminal fontJetBrains Mono, Cascadia Code, Consolas, or Fira Code
Font size12-18px
Default layoutGrid, Main+Sidebar, Rows, or Single

History

Setting Description
Auto-save sessionsRecord terminal output for later review
Retention periodHow long to keep session logs (7 days, 30 days, 90 days, or Forever)

Terminal Features

Supported Shells

  • PowerShell — Windows PowerShell and PowerShell 7+
  • Command Prompt — Classic Windows CMD
  • WSL — Windows Subsystem for Linux distributions
  • Git Bash — Git for Windows bash shell
  • Custom — Any executable with command-line arguments

Windows Terminal Integration

StreamView automatically detects all profiles configured in Windows Terminal. Custom profiles appear in the add-stream menu with their shell paths and working directories imported.

ANSI Color Support

  • 16 standard colors
  • 256 extended colors
  • 24-bit true color (RGB)
  • Bold, italic, underline, and other text styles

Session History

StreamView records terminal output for later review. History is stored locally — you can point the data directory at a cloud-synced folder (OneDrive, Dropbox, etc.) to access history across machines, but StreamView itself has no cloud features.

Viewing History

  1. Open Settings > History
  2. Browse sessions by date, stream name, or workspace
  3. Click a session to view its recorded output
  4. Search across all sessions

Export Options

  • Copy All: Copy session content to clipboard
  • Export .md: Save as Markdown file
  • Export .txt: Save as plain text
  • Export All: Create a ZIP archive of all recorded history

Privacy

  • History is stored locally on your machine (or your chosen data directory)
  • No terminal content is sent to any external server
  • Clear all history anytime from Settings

Recording Modes

Each stream can have its own recording mode, controlling what gets saved to session history. Set this per-template in the stream profile editor.

Mode Records Best For
All User input + terminal output General terminal sessions
Input Only Only what you type Claude Code sessions (prompts are valuable, TUI output is noisy)
Output Only Only terminal output Log tailing, running services, build output
None Nothing Sensitive operations or streams where history isn't useful

Screenshot Paste

Share screenshots with Claude Code directly from StreamView:

  1. Take a screenshot with Win+Shift+S (or PrtSc)
  2. Click the camera button in the stream header, press Ctrl+Shift+V, or Ctrl+V when the clipboard has an image
  3. StreamView saves the image as PNG and types the file path into the terminal
  4. Claude Code reads the image file directly — no manual file management needed

Screenshots are saved to {DataDir}/screenshots/.

Claude Code + MCP Integration (Beta)

StreamView includes an MCP (Model Context Protocol) server that lets Claude Code search your terminal history and log its own summaries.

Security

The MCP server uses stdio transport — it runs as a local child process of Claude Code, not as a network server. There is no port, no HTTP endpoint, and no way for remote machines to connect.

  • No network exposure — communication is via stdin/stdout pipes, not sockets
  • Process-level isolation — only the Claude Code process that spawned it can communicate
  • Toggle on/off — disable MCP anytime in Settings > Data > Integration
  • Read-only by default — search only reads history, log only appends

Setup

Add the StreamView MCP server to your project's .mcp.json:

{
  "mcpServers": {
    "streamview": {
      "type": "stdio",
      "command": "powershell",
      "args": ["-NoProfile", "-ExecutionPolicy", "Bypass",
               "-File", "path/to/mcp-server.ps1"]
    }
  }
}

Available MCP Tools

Tool Description
streamview_search Search terminal history by keyword, date range, stream name, or role
streamview_log Claude writes a clean summary to history instead of parsing terminal output
streamview_streams List all configured streams, their workspaces, and recording modes

Recommended Claude Code Setup

  • Use the built-in "Claude Code" stream template (or create one with your preferred shell)
  • Set recording mode to Input Only — captures prompts cleanly, skips TUI noise
  • Enable the MCP server so Claude can log findings and search past sessions

Data Locations

The data directory is configurable in Settings > Data > Data Directory. Point it at a cloud-synced folder (OneDrive, Dropbox) to access history and settings across machines.

Portable data (follows data directory)

Data Location
History {DataDir}/history/YYYY-MM-DD/{StreamName}_{HHmmss}/
Settings {DataDir}/settings.json
Screenshots {DataDir}/screenshots/

Machine-local data (always local)

Data Location
Session State %LOCALAPPDATA%\StreamView\session.json
Stream Profiles %LOCALAPPDATA%\StreamView\custom-profiles.json
Bootstrap Config %LOCALAPPDATA%\StreamView\config.json
Logs %LOCALAPPDATA%\StreamView\streamview.log

Troubleshooting

Terminal not displaying output

  • Verify the shell command is correct
  • Check that the working directory exists
  • Try a different shell (PowerShell, CMD)
  • Check logs at %LOCALAPPDATA%\StreamView\streamview.log

Performance issues

  • Reduce buffer size in Settings > General
  • Close unused terminal streams
  • Disable auto-save sessions if not needed

Keyboard input not working

  • Click inside the terminal pane to focus it
  • Check the terminal status indicator (green = running)
  • Try restarting the stream from its tab

System Requirements

  • OS: Windows 10 version 1809 (build 17763) or later
  • Architecture: x64
  • RAM: 4 GB minimum
  • Disk: 200 MB for installation, plus space for history
  • Optional: WSL for Linux terminal support

Privacy

StreamView collects anonymous telemetry (app launches, feature usage) to improve the product. No personal data, terminal content, or commands are ever collected or transmitted. Telemetry details can be reviewed in Settings.

Need Help?

Use Help > Contact Support in StreamView to submit a support ticket with logs attached automatically.

When contacting support, include your StreamView version (shown in the status bar), Windows version, and steps to reproduce the issue.

An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please reload the page.