Command Runner & Process Explorer

Sciorex includes a built-in terminal layer for launching tasks, monitoring processes, and inspecting system resource usage — without switching to an external terminal.

Command Runner

Execute shell commands directly from within Sciorex with full ANSI color rendering.

Feature	Description
Shell integration	Uses your system shell (bash, zsh, PowerShell, cmd) with your existing profile and aliases
ANSI color rendering	Full 256-color and truecolor support for command output
Auto-scroll	Output streams in real time with smart auto-scroll that pauses when you scroll up
Input forwarding	Interactive prompts (y/n confirmations, password inputs) are forwarded to the embedded terminal
Working directory	Defaults to the project root; configurable per command

Common use cases:

• Package management — npm install, pip install, cargo build
• Dev servers — npm run dev, python manage.py runserver
• Build scripts — npm run build, make, gradle assemble
• Git operations — git pull, git rebase, git log --oneline
• Custom scripts — any shell command your project uses

TIP

Commands launched through the Command Runner inherit your shell environment, including PATH, aliases, and shell functions. If it works in your terminal, it works here.

Concurrent Processes

Run up to 20 processes simultaneously, each with independent state.

Property	Detail
Max concurrent	20 processes
Independent state	Each process has its own output buffer, exit code, and working directory
Tab interface	Switch between running processes via labeled tabs
Background execution	Processes continue running when their tab is not focused
Grouped launch	Start multiple commands at once from a saved command group

WARNING

Each concurrent process consumes system resources (memory, CPU, file handles). Monitor resource usage through the Process Explorer if you are running many processes simultaneously. The 20-process limit is a safety guardrail, not a target.

Process Explorer

A tree visualization of all processes relevant to your Sciorex session and development environment.

Process Explorer
├── System
│   ├── electron (PID 1234)  ██░░ 4.2% CPU  180 MB
│   └── gpu-process (PID 1235)  █░░░ 1.1% CPU  95 MB
├── Renderer
│   ├── main-window (PID 1240)  ██░░ 3.8% CPU  220 MB
│   └── webview-panel (PID 1241)  █░░░ 0.5% CPU  45 MB
├── CLI / Terminal
│   ├── npm run dev (PID 2001)  ███░ 8.1% CPU  310 MB
│   └── vitest --watch (PID 2002)  ██░░ 5.3% CPU  190 MB
├── Git
│   └── git fetch --all (PID 2010)  █░░░ 0.2% CPU  12 MB
├── LaTeX
│   └── pdflatex main.tex (PID 2020)  ████ 15.0% CPU  85 MB
├── MCP Servers
│   ├── sciorex-research (PID 3001)  █░░░ 0.8% CPU  60 MB
│   ├── sciorex-tickets (PID 3002)  █░░░ 0.6% CPU  55 MB
│   └── sciorex-secrets (PID 3003)  █░░░ 0.3% CPU  40 MB
└── VS Code Server
    └── code-server (PID 4001)  ██░░ 2.5% CPU  150 MB

INFO

The Process Explorer groups processes into categories (System, Renderer, CLI, Git, LaTeX, MCP, VS Code) based on their origin. This makes it easy to find the process you are looking for even when many are running.

Resource Monitoring

Real-time CPU and memory metrics for every tracked process.

Metric	Granularity	Update Interval
CPU usage (%)	Per-process	2 seconds
Memory (RSS)	Per-process	2 seconds
Disk I/O	Per-process (where available)	5 seconds
Network	Aggregate per category	5 seconds

• Spark-line graphs show trends over the last 60 seconds
• Threshold alerts highlight processes exceeding configurable CPU or memory limits
• Historical data retained for the current session

TIP

Set memory thresholds for dev server processes. If a process exceeds the threshold (common with memory leaks in watch mode), Sciorex highlights it in red so you notice before your system slows down.

Server Detection

Sciorex automatically detects common local servers and surfaces them in the Process Explorer.

Server	Detection Method
Ollama	Scans for ollama serve process and checks port 11434
LM Studio	Detects LM Studio process and its API endpoint
Dev servers	Recognizes Vite, Webpack Dev Server, Next.js, and other common dev servers by process name and port
Database servers	Detects PostgreSQL, MySQL, Redis, MongoDB when running locally
Docker containers	Lists running containers with port mappings and resource usage

INFO

Detected servers appear with a status indicator (green = healthy, yellow = high resource usage, red = unresponsive). Click a detected server to view its logs, resource usage, and connection details.

Command History

Never retype a command. Sciorex maintains a searchable history with smart features.

Feature	Description
Favorites	Star frequently used commands for quick access from the command palette
Search	Fuzzy search across all historical commands by keyword
Path-specific recall	History is tagged by working directory; switching projects shows relevant commands first
Frequency sorting	Most-used commands surface to the top of suggestions
Timestamp	Each entry records when it was last run and how many times total

Event Monitoring

Subscribe to and monitor EventBus events flowing through the Sciorex system.

• View real-time event stream filtered by event type, source, or payload content
• Inspect event payloads with syntax-highlighted JSON viewer
• Track event frequency with a live sparkline per event type
• Useful for debugging MCP tool invocations, agent communication, and plugin behavior

WARNING

Event monitoring is a diagnostic tool intended for debugging and development. Keeping many event subscriptions active can increase memory usage. Disable subscriptions you are not actively watching.

Display Modes

The Command Runner and Process Explorer can be displayed in two modes.

Mode	Behavior
Modal	Opens as an overlay panel within the main Sciorex window; dismisses with Escape
Separate window	Detaches into its own OS-level window that persists independently of the main editor

TIP

Use the separate window mode when you need to monitor a long-running build or test suite while continuing to work in the editor. The detached window stays on top of other applications if you enable "Always on Top" in its title bar menu.

Process Actions

Right-click any process in the Process Explorer or Command Runner to access these actions.

Action	Description
Kill	Send SIGTERM (graceful) or SIGKILL (force) to terminate the process
View output	Open the full output buffer in a scrollable, searchable panel
Copy output	Copy the entire output buffer to the clipboard
Restart	Kill and immediately re-run the same command
Pin	Keep a completed process visible in the list instead of auto-removing it

Related

• File Editor — the code editor that sits alongside the terminal
• AI Backend Architecture — how AI models connect to and use the terminal
• Settings — configure shell, history limits, resource thresholds, and display preferences