Planned service model
Remote services are not part of the current CLI command surface. The design goal is to let a future environment lock describe an explicitly requested service connection or execution lease without turning Basecamp into a general-purpose remote command runner.
Service categories
| Category | Examples | Status |
|---|---|---|
| Agent tools | MCP servers, skills, plugins | In design |
| Databases | PostgreSQL, Redis, vector databases | In design |
| Browser | remote browser sessions and automation | In design |
| GPU | inference and accelerated workers | In design |
| Infrastructure | queues, object storage, caches | In design |
| Remote execution | isolated build and task workers | Long-term |
Not everything has to be downloaded
Some software is best delivered as a local artifact. Other needs are better represented as a temporary service connection or execution lease. Basecamp is designed to support both.