Pop-Out AI Terminals, Slash Command Autocomplete, and Memory Monitor for Claude Code

It's 4 PM. Claude Code has been refactoring your auth layer for forty minutes. You want to drag that terminal onto your second monitor so you can keep an eye on it while you work in the main window. You can't. Terminal panes in every ai code editor you've tried are locked inside the main window — you either alt-tab away or accept that the agent disappears the moment you focus on something else.

Meanwhile, you're trying to remember whether the command to compact a Claude Code conversation is /compact, /condense, or something else entirely. And the laptop fans just spun up because four AI agents are streaming output simultaneously and you have no idea which one is actually pegging your RAM.

Three small frictions that ruin a perfectly good agentic coding session. 1DevTool v1.11.2 fixes all three: Pop-Out Terminals, Slash Command Autocomplete, and a Memory & Performance Monitor that lives in the status bar. This release is a love letter to anyone running Claude Code, Codex CLI, Gemini CLI, or Amp on a single laptop and feeling the heat.

Pop-Out Terminals: Drag Any AI Agent to a Second Monitor

The pop-out feature is the smallest UI change with the biggest workflow impact. Every terminal in 1DevTool now has a tiny "Pop Out to New Window" button in its toolbar — a 12-pixel arrow icon sitting between the fullscreen and recording controls. Click it, and the terminal detaches into its own resizable window.

How Pop-Out Actually Works (No Lost State)

This is harder than it sounds, because terminals are stateful. Naive implementations of pop-out either lose all the scrollback, restart the underlying process, or worse — leave a ghost terminal behind in the original window. 1DevTool handles it cleanly: when you click the pop-out button, the renderer disposes the xterm view in the main window, the main Electron process spawns a new BrowserWindow with the terminal's ID in the URL, and the new window re-mounts the same terminal record from the Zustand store. The PTY process never restarts. Your scrollback is preserved. Claude Code keeps running.

The popped-out window inherits your font size and zoom factor instantly. There's a compact titlebar at the top with three controls: −, the current font size, and +. Cmd++, Cmd+−, and Cmd+0 work exactly like they do in the main window — and because the terminal store is global, changing the font size in the popout updates every other terminal in the app at the same time.

Anchor It Back When You're Done

Done with the popped-out terminal? Click the Anchor button in the popout's titlebar. The window closes, the main process notifies the renderer, and the terminal re-mounts in its original slot in the main 1DevTool window — exactly where you left it. No configuration, no "Window" menu hunting, no manual reattach. The same terminal instance, the same scrollback, the same agent session.

The killer use case is multi-monitor workflows. Pop your long-running Claude Code session onto a side monitor, leave it streaming in your peripheral vision, and use the main window for a Codex CLI session that's actively waiting on your input. You finally get the focus split that physical monitors were designed for — without losing the integration benefits of an all-in-one workspace.

Slash Command Autocomplete for Claude Code, Codex, and Gemini

Modern AI agents have a lot of slash commands. Claude Code alone ships with more than sixty of them — /compact, /clear, /model, /login, /cost, /doctor, /init, /permissions, the list goes on. Codex CLI has its own set. Gemini CLI has yet another. Nobody remembers all of them, so people fall back to the same five or six commands and never discover the powerful ones.

Slash Command Autocomplete fixes that. Type / in the AI input overlay above any terminal, and a dropdown appears showing every command available for that specific agent type, grouped by category, with fuzzy search.

Agent-Aware Command Lists

The autocomplete is agent-aware. When you're typing into a Claude Code terminal, you see Claude commands grouped into categories like conversation, model, config, tools, git, and debug. Switch to a Codex CLI terminal, and the dropdown immediately shows Codex's ~15 commands instead. Open a Gemini CLI terminal, and you see the 30+ Gemini-specific commands. The detection is automatic — 1DevTool knows what agent each terminal is running, so the dropdown always matches the context.

Each command appears as a monospace label (/compact) followed by a short description in muted text. As you type, fuzzy matching surfaces commands by name first, then by description. Press ↑/↓ to navigate, Enter or Tab to insert the selected command, and Esc to dismiss. The whole interaction takes under a second once you build the muscle memory.

Installed Skills Show Up Too

Beyond built-in commands, the autocomplete also surfaces your installed skills. If you've set up GStack skills or installed any custom skills via 1DevTool's Skills Manager, they appear in the same dropdown — tagged with a colored badge so you can tell at a glance whether you're inserting a built-in command or a custom skill. Built-in commands take precedence on name collisions, so your shipped agent commands never get shadowed by a custom skill that happens to share a name.

This turns the autocomplete into something more interesting than a typing aid: it's a discovery layer. The next time you wonder "does Claude Code have a way to do X?", type / and search. If it exists, you'll see it. If your team has built a custom skill for it, you'll see that too.

Memory & Performance Monitor: Watch Your Laptop Survive Multi-Agent Day

Running multiple AI agents in parallel is the fastest way to discover the limits of your machine. Each Claude Code or Codex session can hold gigabytes of context. Each terminal holds a scrollback buffer. Each browser tab in the embedded browser eats more RAM. And the symptoms of memory pressure are subtle — micro-stutters, delayed keystrokes, fans suddenly spinning up — long before you actually crash.

v1.11.2 adds a status-bar indicator that watches your system RAM in real time and surfaces a warning before things get bad. By default it stays hidden when memory pressure is low. When usage crosses 75%, a yellow indicator with a memory icon and percentage appears in the status bar. Above 90%, it turns red.

Three Numbers That Actually Matter

Click the indicator and a compact panel slides up showing exactly the three numbers a developer running multiple agents needs:

• System RAM: total used vs. total installed, e.g., 14.2 GB / 16 GB, with a colored progress bar.
• 1DevTool usage: the resident set size of the 1DevTool process itself, so you can tell whether the pressure is coming from your editor or from something else running on the machine.
• CPU load: the one-minute load average normalized against your core count — instantly tells you whether you're CPU-bound, memory-bound, or both.

The metrics refresh every thirty seconds in the background, but the popup re-fetches the moment you open it so you always see fresh numbers when you're looking.

One-Click "Clear Terminal Buffers"

The popup includes a single action button: Clear Terminal Buffers. Click it, and 1DevTool walks every active PTY in the app, drops its in-memory output buffer, and reports back how many buffers it cleared. Your live agent sessions keep running — only the scrollback history gets pruned. For a developer who's been running ten Claude Code sessions for six hours, this can recover hundreds of megabytes in a single click.

It pairs nicely with another v1.11.2 improvement: terminal output buffers are now capped at 2 MB by default (down from 5 MB), and they expire automatically when a terminal is detached. The combination means your typical multi-agent workspace runs noticeably lighter without you doing anything.

MCP Feature Toggles: Channels, Design, and Prototype on Demand

1DevTool ships three first-party MCP servers: Channels (multi-agent orchestration), Design (the AI design canvas), and Prototype (the prototype tool). Up until v1.11.2, they were either always enabled or always disabled based on your config. v1.11.2 turns each one into a feature card in MCP settings with a toggle switch and a one-click reinstall button.

Each card shows a status dot (green when installed, gray when not), the feature name, the MCP config key it registers, and a short description. Toggle the switch and 1DevTool writes the appropriate entry to your ~/.claude.json file. If something goes wrong — Node missing, permissions issue, broken install — the card surfaces diagnostics with a "Copy debug logs" button so you can share the exact platform, paths, and file accessibility info instead of guessing.

The reinstall button is the secret weapon. If a feature shows up as "failed" or "disconnected" in your agent, one click rewrites its config entry from scratch. You don't have to leave the app, edit JSON by hand, or restart anything — just click and the next agent session picks up the fresh config.

Quality-of-Life Changes Worth Knowing About

v1.11.2 also includes a stack of smaller improvements that compound across a long workday:

• Skip Version button on the auto-update dialog — dismiss an update permanently if you're not ready for it.
• Cmd+W closes the focused panel — editor file, browser tab, or terminal — based on which panel has focus, rather than always closing the same thing.
• Esc closes the Git panel — small thing, but the kind of keyboard shortcut you reach for thirty times a day.
• Smarter reader mode formatting — bold text, indentation, and trailing status-bar lines from streaming agents are cleaned up more reliably when rendering terminal output as markdown.
• Mermaid diagram validation — invalid syntax is caught before rendering, so you no longer get broken SVGs from AI-generated diagrams.
• Faster terminal rendering — buffer trimming is deferred off the main thread, so heavy output streams no longer cause UI micro-stutters.
• Dark-mode caret fix — the cursor in the AI input field is now actually visible in dark themes.
• Auto-update dialog now actually checks for updates the moment you open it, instead of waiting for a manual click.

Who Benefits Most

Before vs After: A Multi-Agent Workflow

Pull the three headline features together and a typical day looks meaningfully different.

Before v1.11.2

1. Open Claude Code, Codex, and Gemini in three terminals.
2. Want to glance at Claude on your second monitor — you can't. Alt-tab instead.
3. Try to remember which Claude command compacts the conversation. Google it.
4. Notice the fans spinning up. No idea why. Quit a random app.
5. Keep working until something stutters. Restart the editor to recover memory.

After v1.11.2

1. Open the same three terminals.
2. Pop Claude onto your second monitor with one click. Anchor it back when you're done.
3. Type /comp — fuzzy search surfaces /compact instantly.
4. The status bar shows yellow at 78% RAM. Click it, see the breakdown.
5. Click "Clear Terminal Buffers" — back to 62%, no restart needed.

Full Changelog: v1.11.2

The headline features:

• Pop-Out Terminals — pop any terminal into its own resizable window with one click, inheriting font size and zoom, and anchor it back at any time.
• Slash Command Autocomplete — type / in the AI input to browse every built-in command for your agent (Claude, Codex, Gemini, etc.) plus your installed skills, grouped by category with fuzzy search.
• Memory & Performance Monitor — a status-bar indicator turns yellow or red under memory pressure; click for a breakdown of system RAM, 1DevTool usage, CPU load, and a one-click "Clear terminal buffers" action.
• MCP Feature Toggles — enable or disable Channels, Design, and Prototype as feature cards in MCP settings, with one-click reinstall if something goes wrong.

And the supporting improvements and fixes:

• Skip Version button on the update dialog.
• Cmd+W closes the focused panel — editor file, browser tab, or terminal.
• Esc closes the Git panel.
• Smarter reader mode formatting for bold text, indentation, and trailing status-bar lines.
• Mermaid diagrams validate before rendering.
• Lower memory footprint — 2 MB terminal output buffers (down from 5 MB) that auto-expire when detached.
• Faster terminal rendering — buffer trimming deferred off the main thread.
• Dark-mode caret fix in the AI input field.
• Auto-update dialog checks for updates automatically when opened.
• Reader mode no longer loses formatting at the bottom of Claude conversations.

Try It Today

Pop-Out Terminals, Slash Command Autocomplete, and the Memory Monitor are available now in 1DevTool v1.11.2. If you're running multiple AI agents on a single machine — especially Claude Code, Codex CLI, or Gemini CLI in parallel — download the latest release and feel the difference within the first hour.

These three features are the kind of small workflow improvements that don't look like much in a changelog and then quietly become indispensable. Pop a terminal to your second monitor once and you'll never go back. Type / and discover commands you didn't know existed. Watch your laptop survive a six-agent afternoon.

One workspace. Every agent. Every key shortcut and every megabyte where you expect them.