Rebuildability
Can a clean clone restore tools and dependencies from committed instructions?
Run a read-only evidence audit before choosing remote infrastructure. The plugin recommends a rebuildable Claude Code web session, a persistent development shell, or more investigation.
The sparse checkout fetches only the marketplace manifest and this plugin from the Terminalbox repository.
claude plugin marketplace add Anchras/terminalbox --sparse .claude-plugin plugins/remote-workspace-fit claude plugin install remote-workspace-fit@terminalbox-tools /remote-workspace-fit:workspace-fit The skill reads orientation docs, tracked manifests, lockfiles, development scripts, container configuration, and CI files. It does not execute the workflow it finds.
Can a clean clone restore tools and dependencies from committed instructions?
Do databases, watchers, queues, containers, or agent processes need to keep running?
Is the valuable state an interactive shell or tmux session steered across devices?
Are private networks, SSH hops, non-GitHub sources, hardware, or local data required?
Use the provider workflow when setup is repeatable and the task can return a branch or pull request asynchronously.
Generate the free setup files →Consider a persistent shell when processes, interactive state, or cross-device continuity are the actual requirement.
See the €6/month persistent option →Ask one focused question or run one safe validation step. The plugin does not recommend buying anything without repository-backed evidence.
Ask for an honest fit check →Every result separates observed evidence from unknowns and ends with one safe next test.
Recommendation Rebuildable web session — the tracked lockfiles and CI setup restore the project. Repository evidence • package-lock.json and npm ci are committed • CI provisions the only documented service • no long-running local process is required Persistence triggers None found. Next test Confirm one fresh cloud session can run the documented check.
One Markdown skill with the audit workflow, decision rules, and output contract.
No executable scripts, hooks, MCP servers, agents, credentials, or network client.
Reading secret values, installing dependencies, starting services, or changing files.
This page records bounded view and button labels. Plugin use and repository contents are not sent to Terminalbox.