Paseo sh is the terminal-first path for controlled agent coding

Where shell access helps

A coding agent becomes more useful when it can inspect files, run tests, generate artifacts, and explain what happened. Shell access makes that possible, but it also raises the stakes.

Paseo sh should be treated as a controlled lane: commands are scoped, logs are preserved, and high-impact actions require review. That is the difference between a useful terminal helper and an unsafe automation shortcut.

• Use shell access for tests, static checks, local builds, and repeatable scripts.
• Keep destructive commands behind explicit review.
• Store secrets outside prompts, logs, and generated notes.
• Prefer sandboxed execution before exposing a real workstation or production runner.

When the managed workspace is better

A terminal is fast for operators, but it is not always the best buying experience for a team. A managed workspace gives non-terminal stakeholders a clearer view of plan choice, payment, memory, and safety.

The best pattern is often both: use the web workspace to choose and onboard, then reserve Paseo sh style runs for repeatable tasks that benefit from command-line speed.

A safer first run

Start with one small repository mission. Allow read-only inspection first, then tests, then file edits, then a final review. If the run creates value and the safety boundary feels clear, Studio annual is usually enough to continue.

Common questions