boxctl vs Terminal Command Agent by Nova (CIVAI)
boxctl is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
boxctl is a plugin bundle for AI coding tools published by Cemal Y. Dalar. No marketplace we read lists it any more. Terminal Command Agent by Nova (CIVAI) is an MCP server published by nova.civai.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace cdalar/boxctl | Removed on 2026-10-15 Version: 0.6.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | boxctlno longer listed · | Terminal Command Agent by Nova (CIVAI) |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (nova.civai.co/mcp/agents/terminal-command-agent) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cdalar/boxctl | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of boxctl
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Give an agent a real Linux VM: run commands, move files, expose a preview URL, destroy it.
-
Nido — Fast, Simple VM Sandboxes for AI Agents (Temporary & Persistent)
Manage temporary or persistent Linux VMs (QEMU/KVM). Designed for AI agents and automation.
-
Linux microVM sandboxes for AI agents: run commands, files, processes, pause and wake.
-
Every machine you have, for your coding agent: live GPU, VRAM, RAM and disk, and SSH.
-
Ephemeral MicroVM-isolated code execution for AI agents. Fresh VM per call, hard-purged after.
-
Securely run LLM-generated code in isolated containers across 7 languages and 3 container backends.
What each says it does
boxctl
Run Claude Code's Bash commands in a boxctl.io microVM instead of on your machine.
Terminal Command Agent by Nova (CIVAI)
I run shell commands on your private cloud environment (bash, sh, zsh)
How to run each
boxctl
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Terminal Command Agent by Nova (CIVAI) As a remote MCP server
claude mcp add --transport http terminal-command-agent https://nova.civai.co/mcp/agents/terminal-command-agent
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Terminal Command Agent by Nova (CIVAI) has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: boxctl · What it can do: Terminal Command Agent by Nova (CIVAI) · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.