Terminal & AI Agents

Choose Where Your Agent Runs

Add Terminal's This agent runs on control decides where the AI CLI process actually runs: This Computer runs it locally with your own login, quota, memory, skills and MCP servers against a mount, and On the machine runs it over ssh -tt on the machine itself. Set it per project and override it per terminal.

Choose Where Your Agent Runs

Why You Need This

How this feature boosts your daily productivity

Where the files live and where the agent runs are two different questions, and treating them as one is how you end up with a CLI that is a stranger on your own server — no login, no quota, none of the MCP servers you configured, a fresh config staring at you. 1DevTool now asks the question out loud and never answers it for you: neither placement is a fallback for the other, and the app never switches between them on its own. An agent that is not installed on the target machine is greyed out with the reason instead of accepting the launch and failing at the prompt, so "Claude isn't on the mini" is something you read before you commit, not sixty seconds into a run that was never going to work.

How It Works

Get started in 4 simple steps

1
1

Open Add Terminal

The This agent runs on control sits above the agent grid, showing the project's machine and This Computer as two explicit choices.

2
2

Pick This Computer to keep your own setup

The CLI runs here with your login, quota, memory, skills and MCP servers, reading the machine's files through a mount (fuse-t on macOS, sshfs elsewhere).

3
3

Or pick the machine to run it there

The CLI runs over ssh -tt on the machine itself, using whatever is installed on that host.

4
4

Set it per project, override per terminal

The project default applies to new terminals; any single terminal can be pointed the other way without changing the project.

5
5

Read the greyed-out reasons

An agent that is not installed on the target machine is disabled with the reason shown, instead of accepting the launch and failing at the prompt.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# run the CLI on the remote box
# no login, no quota, no MCP servers
# no skills, a fresh config
# or run it locally and hope the mount is up
# nothing tells you which one you did

The 1DevTool Way

Add Terminal -> This agent runs on
This Computer: your login, quota, MCP, via a mount
On the machine: over ssh -tt, there
Per project, overridable per terminal
Not-installed agents are greyed out with a reason

Key Capabilities

Everything included with Choose Where Your Agent Runs

Decide where the AI CLI process actually runs
Run the CLI locally with your own login and quota
Reach the machine's files through a mount when running local
Keep your MCP servers, memory and skills on a remote project
Run the CLI over ssh -tt on the machine instead
Set a default per project and override it per terminal
See agents greyed out when they are not installed on the target
Read the reason a placement is unavailable before launching
Know the app never switches placement on its own

Why It Matters

The productivity impact of having terminal & ai agents built into your workspace

Zero Context Switching

All your AI agents and terminals live in one window. No more alt-tabbing between 5 different terminal apps.

Visual Status Tracking

Color-coded tabs and the Kanban dashboard tell you which agents are done, running, or need attention — at a glance.

Persistent Sessions

Tmux-backed persistence means your terminal state survives crashes and restarts. Never lose scrollback history again.

Flexible Arrangements

One-click layouts adapt to your task: grid for monitoring, columns for comparing, fullscreen for deep focus.

Ready to boost your workflow?

Download 1DevTool for free and experience Choose Where Your Agent Runs along with 287 other features — all in one app.