openbash
API by openbash · rest
Bash programs over data, reachable by HTTP, SSH and MCP. There is ONE execution endpoint, not one per program. Programs are commands on a path inside a shell — "customs | jq | sort" is a single request — so they compose without any of them knowing about the others. Which programs exist is decided per ACCOUNT, not per call: once enabled, every session that account opens has them, and help lists exactly those. Stateless by default; pass a session_id to carry a working directory, environment and /tmp across calls. A session id names the shell, not the connection — the same id is resumable from HTTP, MCP and SSH, and survives a restart of this gateway. On MCP, an Mcp-Session-Id sent with initialize NAMES the session: it is resumed if it exists and started under that name if it does not, so a client can choose an id once and keep it. A client that sends no header still keeps one session: an OAuth connector gets a DEFAULT session bound to its client_id, so continuity does not depend on…
Endpoint: https://openbash.ai/
Verification: observed. Source: crawl.
Capabilities (13)
- Trade an emailed code for a key and an ssh command.
- What has been added newest first.
- Run one command.
- What this key resolves to and which programs the catalog records as enabled…
- List every program with this key's enablement marked.
- One program help text included.
- One read of a program's browsable surface.
- What a submission froze.
- Read one file from a submission.
- Open a session or resume one for state across calls.
- End a session.
- Run one command inside an open session.
- Read a file from a session's scratch.