Creating Your First Split Terminal in Remocode

Creating Your First Split Terminal in Remocode

Split terminals are at the heart of Remocode. Instead of switching between tabs or windows, you can see multiple shell sessions at once. This guide shows you how to create, manage, and use split panes effectively.

Your First Vertical Split

With Remocode open and a terminal session active:

• ●Press `⌘D`
• ●The current pane splits into two side-by-side panes

You now have two independent terminal sessions. Click either pane to make it active, then type as usual.

Use case: Run your development server on the left and edit files on the right.

Your First Horizontal Split

To split the pane top-to-bottom instead:

• ●Press `⌘⇧D`
• ●The current pane splits into an upper and lower pane

Use case: Run tests in the top pane while watching logs in the bottom pane.

Combining Splits

You can split any pane further. For example, starting from a single pane:

• ●Press `⌘D` to split right (now you have left and right)
• ●Click the right pane
• ●Press `⌘⇧D` to split it downward (now you have left, top-right, and bottom-right)

This creates an L-shaped layout:

┌──────────────┬──────────────┐
│              │   Top Right  │
│    Left      ├──────────────┤
│              │ Bottom Right │
└──────────────┴──────────────┘

The 2x2 Workspace Shortcut

For the most common multi-pane layout, press `⌘⇧W` to create a new workspace. This instantly gives you a 2x2 grid of four panes:

┌──────────────┬──────────────┐
│   Pane 1     │   Pane 2     │
├──────────────┼──────────────┤
│   Pane 3     │   Pane 4     │
└──────────────┴──────────────┘

This is the recommended starting layout for most development workflows.

Practical Multi-Pane Workflows

Full-Stack Development:

| Pane | Purpose | |------|---------| | Top-left | Frontend dev server (npm run dev) | | Top-right | Backend server (node server.js) | | Bottom-left | Git operations | | Bottom-right | AI panel or test runner |

DevOps Workflow:

| Pane | Purpose | |------|---------| | Top-left | kubectl watch (kubectl get pods -w) | | Top-right | Log tailing (stern my-app) | | Bottom-left | Docker management | | Bottom-right | SSH session to remote server |

AI-Assisted Coding:

| Pane | Purpose | |------|---------| | Left (wide) | Code editor (vim, nano, or your CLI editor) | | Top-right | AI panel (⌘⇧A) | | Bottom-right | Test runner (npm test -- --watch) |

Closing Panes

To close a pane, click on it to make it active, then press `⌘W`. The remaining panes will resize to fill the available space.

Zooming

If a particular pane needs more room temporarily:

• ●`⌘=` — zoom in (increases font size across all panes)
• ●`⌘-` — zoom out
• ●`⌘0` — reset to default zoom level

Best Practices

• ●Start with `⌘⇧W` to get a workspace, then close panes you do not need
• ●Keep related tasks adjacent so you can glance between them
• ●Use the AI panel (⌘⇧A) alongside your splits for inline assistance
• ●Do not over-split — three or four panes is usually the sweet spot on most screens

Split terminals turn Remocode into a command center for your entire development workflow. Once you build the muscle memory for ⌘D and ⌘⇧D, you will wonder how you worked without them.