Bosco, your assistant
Bosco is the assistant built into the SailOps console. It knows your project, explains the product, troubleshoots what is failing, and can configure resources when you allow it.
Bosco is included on every plan at no extra cost.
What Bosco does
- Answers questions about SailOps — "how do I add a custom domain?" — with a link to the documentation page.
- Troubleshoots your project — "why is my API restarting?" — by reading the status, events, logs, metrics and alerts of your workloads, then telling you what it checked and what it found.
- Configures your project — "scale the worker to two instances" — through the same operations you would do in the console, with your approval when you want it.
- Shows usage as a chart — "how much CPU did the API use this hour?" — with a small graph of the last window, right in the conversation.
- Opens a support ticket for you — when something looks like a platform fault it cannot explain, Bosco offers to open a ticket; it only does so once you say yes, and links the ticket in the chat. Opening a ticket needs a developer, maintainer, owner or accountant role on the organization; readers can read tickets but not open them.
- Watches a resource for you — "tell me when the API container is running" — Bosco sets up a watch and the console notifies you in the conversation tab (and with a toast) when the condition is met or the timeout expires.
Opening Bosco
- Click the Bosco AI button in the top bar of any project page, or press ⌘ J (Ctrl J on Windows and Linux).
- The panel stays open while you navigate between pages — you can browse your project without losing the conversation. It closes automatically when you switch organization.
- From the panel header, pick a layout: Bubble (a floating window in the corner), Drawer (slides in from the right) or Sidebar (docked next to the page). The choice is remembered.
- In Bubble mode, drag the header to move the window anywhere on screen. The position is saved and restored on your next visit. Double-click the header to snap it back to the default corner. You can also nudge it with the arrow keys (hold Shift for larger steps).
- Conversations belong to the organization, not to a single project. Start a new one at any time; archived conversations disappear from the list.
Bosco knows which page you are on: on a container's page, "this container" means that one.
Getting started with Bosco
Bosco helps at two key moments when you are new to a project or an organization:
- Organization setup — when a paid organization is created, Bosco walks you through billing details, payment method and first project creation in a full-screen guided flow. See Organization setup for the steps.
- Project quickstart — when you open an empty project, Bosco replaces the static quickstart with an interactive prompt. Pick an idea — deploy a container, create a database, host a website and more — or describe what you are building, and Bosco sets it up with you through the conversation.
Conversations across projects
A conversation follows you when you switch projects inside the same organization. A thin divider marks the point where the scope moved. From then on, Bosco's tools act on the new project.
- Proposals made in the previous project must be approved or rejected from that project — the card tells you if you need to switch.
- If your role on a project is later revoked, exchanges that happened in it are hidden from the conversation. The title is also hidden when the first exchange is no longer visible.
- Switching organization closes the panel and resets the state entirely.
Permission modes
Every conversation has a mode. Change it from the panel header.
| Mode | What Bosco may do |
|---|---|
| Observe | Read only. Bosco describes what to change and lets you do it. |
| Ask | Bosco reads freely; every change is shown as a card you approve or reject before it runs. A proposal expires after 15 minutes. |
| Auto | Bosco applies ordinary changes immediately and tells you what it did. |
Your role in the project caps the mode. Readers and accountants can only use Observe. Developers, maintainers and owners can use all three. Switching a conversation to Ask or Auto never grants you more than your role allows: Bosco can only do what you could do yourself in the console.
What Bosco will never do
Some actions stay in your hands, whatever the mode:
- Delete a container, website, gateway, database, cache, queue, volume or file.
- Reset or regenerate credentials of a managed service.
- Restore or delete a backup.
- Apply a whole stack in one go.
- Leave your organization — it cannot read or change anything outside the organization you have open.
When one of these is the right thing to do, Bosco says so and gives you a link that opens the matching dialog in the console, where you confirm the action yourself.
Bosco also sticks to SailOps. Ask it to write unrelated code or to discuss another provider and it will politely decline.
Fair-use limits
Bosco is free, with limits that keep it responsive for everyone:
- 300 messages and 10 million tokens per member per day, reset at midnight UTC. The panel shows what is left. Custom plans have no daily cap.
- 40 messages per conversation — start a new one when you reach it.
- A proposed change waits 15 minutes for your decision, then expires.
Privacy
- Bosco's language model runs on Scaleway Generative APIs in Paris. Your conversations never leave the European Union.
- Bosco sees curated views of your project: statuses, event summaries, log lines with credentials masked, usage figures. It never receives your environment variable values, connection strings, service credentials, backup archives or full configuration exports.
- Conversations are stored with your organization and deleted 90 days after their last message. Archive one to hide it sooner.
- Every change Bosco applies is recorded in your organization's audit log, under your name, with Bosco as the source.
- An organization can opt out of Bosco entirely — contact support. Opting out also turns off Sonny, the automatic first response on support tickets.
Resource watches
Ask Bosco to notify you when a resource reaches a condition — for example, "tell me when the worker container is running" or "let me know when the nightly job completes". Bosco calls watch_resource once and the console monitors the resource for you:
- Supported resources: containers, jobs, cron jobs, PostgreSQL, MariaDB, Valkey, NATS, websites and gateways.
- Conditions:
running,ready,stopped,completed,failedorexists. - The watch times out after 10 minutes by default (up to 30 minutes if you ask).
- When the condition is met or the watch times out, a notice appears in the conversation and a toast pops up, even if you navigated away from the page.
- Watches live in the current browser tab only — they do not survive a page reload.
Tips
- Ask in French or English; Bosco answers in your language and searches the documentation in it.
- Resource names in Bosco's answers are chips: click one to open the resource's page or the tab it refers to.
- In Ask mode, read the card before approving: it shows the exact operation and its parameters.
- Name the workload — "the
apicontainer" — and Bosco skips a step. - If Bosco says the data does not show a cause, it means it: it does not guess. Follow its "what to check next".