Build Automations and Agents Autonomously

Describe the system you want, and let OpenSail draft the agent, automation, connectors, schedule, permissions, and review flow.

<p align="center"> <img src="assets/agent-builder.png" alt="Agent Builder authoring a new agent from chat" width="85%" /> </p>

OpenSail includes built-in agents that help people turn intent into reusable team assets.

Agent Builder: Mention @agent-builder, describe the agent you want, and it drafts a user-owned agent with a name, instructions, model preference, connected MCP servers, skills, and tool permissions. It uses the user's installed resources, produces a review card, and publishes after approval.

Automation Builder: Mention @automation-builder, choose one of your existing agents, describe the schedule and output target, and it drafts a user-owned automation. It attaches the cron trigger, prompt template, delivery targets, compute tier, and spend cap, then waits for the publish-and-activate review.

Service Integrator: Use the Service Integrator agent to connect services, configure MCPs and channels, and make sure agents have the tools they need before a workflow goes live.

These builders make the marketplace practical for everyday teams: build an agent, attach the right systems, schedule it, review it, and share it from the same chat surface.

<p align="center"> <img src="assets/agent-builder-details.png" alt="Agent Builder review card with the full agent configuration expanded" width="85%" /> </p>

---

Deployment targets

Ship to 22 places by drawing an edge.

<p align="center"> <img src="assets/deployment-targets.png" alt="Pick from 22 deployment providers — serverless, container, static, and registry targets" width="85%" /> </p>

Deploy from the Architecture Panel. Draw an edge from a container to a deployment target. A/B deployments work naturally: connect the same container to two targets (Vercel for production, Cloudflare for preview) and each gets independent deployment history and rollback.

22 supported targets:

Each target is a registry entry. Adding a new provider is one config block.

---

Docker Compose

This is the most realistic first run for most people. It starts the frontend, backend, worker, gateway, Postgres, Redis, Traefik, and the devserver image used by user project containers.

Use Docker Desktop on macOS or Windows, Docker Engine on Linux, or Colima on macOS. On Windows, run the commands from WSL2 so bind mounts and project paths behave like Linux paths.

git clone https://github.com/TesslateAI/opensail.git
cd opensail
cp .env.example .env

Edit .env before first boot:

• SECRET_KEY should be a real random value.
• LITELLM_API_BASE and LITELLM_MASTER_KEY are needed for agent/model calls. A working model proxy gives you the full agent experience.

Then start the stack:

docker compose up --build -d
docker compose ps

Open http://localhost. API docs are at http://localhost:8000/docs.

The fuller Docker walkthrough is in docs/guides/docker-setup.md. After your first setup, the helper script is handy:

./scripts/docker.sh start
./scripts/docker.sh status
./scripts/docker.sh logs backend

Guided macOS Setup

If you are on macOS and want the repo to help install local tooling, use the interactive installer. It installs Homebrew dependencies, starts Colima, helps create .env, and lets you choose Docker Compose or Minikube.

git clone https://github.com/TesslateAI/opensail.git
cd opensail
./scripts/install-macos.sh

Use Docker Compose unless you specifically need Kubernetes behavior.

Gateway API and MCP Server

Rent your compute to other agents.

OpenSail exposes your running instance to the outside world through two interfaces:

Gateway API: External users (agents or humans) can interact with your OpenSail instance using an API key. They get their own sandboxed containers, can invoke agents, and run workflows. The API supports webhook callbacks on completion, scoped permissions per key, and project-level isolation.

MCP Server (in development): OpenSail itself becomes an MCP tool server. External coding agents (Claude Code, Cursor, Codex, or your own) can connect to your OpenSail instance, get sandboxed compute, use your agents, and publish apps directly from their development environment. Your instance becomes infrastructure that other agents can build on.

---