StarShell

Terminal Agents Suffice for Enterprise Automation

1ServiceNow    2Mila – Quebec AI Institute    3Université de Montréal

Comparison of MCP, Web, and Terminal agents on a ServiceNow catalog ordering task. The terminal agent recovers from errors through iterative API exploration.

Abstract

There has been growing interest in building agents that can interact with digital platforms to execute meaningful enterprise tasks autonomously. Among the approaches explored are tool-augmented agents built on abstractions such as Model Context Protocol (MCP) and web agents that operate through graphical interfaces. Yet, it remains unclear whether such complex agentic systems are necessary given their cost and operational overhead.

We argue that a coding agent equipped only with a terminal and a filesystem can solve many enterprise tasks more effectively by interacting directly with platform APIs. We evaluate this hypothesis across diverse real-world systems and show that these low-level terminal agents match or outperform more complex agent architectures. Our findings suggest that simple programmatic interfaces, combined with strong foundation models, are sufficient for practical enterprise automation.

Overview

StarShell overview

Overview of StarShell: a minimal terminal agent for enterprise automation. The agent operates through a terminal and filesystem, optionally using documentation and persistent skills to discover and invoke APIs directly on enterprise platforms (e.g., GitLab, ServiceNow, ERPNext), without relying on GUI interaction or pre-defined tool registries.

Results

We evaluate three agent architectures — Terminal (bash), MCP (tool-augmented), and Web (Playwright) — across three enterprise platforms and multiple foundation models. SR is the success rate (%) and Cost is the average cost per task in USD.

Agent ServiceNow GitLab ERPNext Overall
SRCost SRCost SRCost SRCost
Claude Sonnet 4.6
MCP11.50.7645.20.4855.60.1432.90.51
Web72.44.4982.90.8861.83.6372.23.29
Terminal73.60.7876.50.2867.60.4672.70.56
Claude Opus 4.6
MCP16.10.6646.80.9068.90.1739.20.58
Web77.64.2181.90.8581.66.4979.93.97
Terminal79.11.9480.20.5076.80.7278.71.22
GPT-5.4 Thinking (Medium)
MCP18.50.1447.90.4062.80.2138.80.23
Web69.40.5481.40.1772.50.5173.40.43
Terminal77.00.2071.30.1370.00.2473.50.19
Gemini 3.1 Pro
MCP14.20.1048.90.1562.80.0737.10.11
Web62.10.6884.60.2265.21.1368.90.69
Terminal78.50.1079.80.0673.90.1077.50.09

Terminal agents consistently match or outperform MCP and Web agents while being significantly cheaper. Bold indicates best or tied-best per model–platform.

Skills Accumulation

The terminal agent can persist reusable procedures (skills) across sequential tasks. Top: cumulative number of successful tasks. Middle: cumulative cost ($USD). Bottom: skills directory size (KB). The agent with memory (blue) accumulates reusable procedures; the baseline (black) starts fresh every time.

Skills accumulation over sequential tasks

BibTeX

@article{bechard2026terminal,
  title   = {Terminal Agents Suffice for Enterprise Automation},
  author  = {Bechard, Patrice and Ayala, Orlando Marquez and Chen, Emily and Skelton, Jordan and Davasam, Sagar and Sunkara, Srinivas and Yadav, Vikas and Rajeswar, Sai},
  journal = {arXiv preprint arXiv:2604.00073},
  year    = {2026}
}