Ask Bosco a question from your SailOps project. The assistant uses your resources as context to help you understand a situation, examine a change and stay in control of operations.
Available in beta · included in every plan, with usage limits
One question. Context to move forward.
Three illustrative examples show how to explore a situation with Bosco. The data is fictional and responses do not guarantee a diagnosis.
01
Examine a restart with Bosco
Bosco AIObserveIllustrative example · fictional data
The starting question
Why did my application restart?
Bosco’s interpretation
A restart appears in the observed period. I can compare the resource state, logs and metrics to look for an explanation.
01
Read the resource state
Identify the application and the period to examine.
02
Compare logs and metrics
Look for signals around the restart.
03
Form a hypothesis to check
Distinguish observations from a confirmed cause.
02
Propose a capacity change
Bosco AIAskIllustrative example · fictional data
The starting question
Scale the worker from one to two instances.
Bosco’s interpretation
The worker has one instance. Here is the proposed change. In Ask mode, it waits for your approval before execution.
01
Identify the resource
Confirm the target worker and its current state.
02
Present the change
Make the change from one to two instances explicit.
03
Wait for your approval
Review resources and usage impact before approving.
03
Read CPU and memory with Bosco
Bosco AIObserveIllustrative example · fictional data
The starting question
How are my application’s CPU and memory changing?
Bosco’s interpretation
I can read available metrics for the selected period. Here, CPU varies more than memory; this observation needs to be considered alongside the workload.
01
Choose a period
Look at a window relevant to the activity.
02
Compare the signals
Observe changes in CPU and memory.
03
Prepare the discussion
Share these observations before deciding on an adjustment.
You choose the level of action.
The selected mode defines how Bosco can act. Your account permissions still apply.
01
Observe
Understand before acting
Bosco reads accessible information without changing resources. This read-only mode lets you examine a state, logs or metrics.
02
Ask
Approve each change
Bosco proposes changes and waits for approval before executing them. You review the resource and the requested change.
03
Auto
Allow actions, within limits
Bosco automatically executes operations allowed by this mode. Sensitive actions still require approval, and some operations remain exclusive to the console.
An assistant in your project. Clear boundaries.
Bosco helps with exploration and selected operations. It does not guarantee an incident’s cause or resolution. Global deletions, restores and full-stack operations must be handled in the console when they are not supported.
You can converse in French or English. The product interface is in English.
Before your first conversation
Is Bosco included in my plan?
Bosco is available in beta and included in every plan. Daily limits are 300 messages and 10 million tokens per member. Each conversation allows 40 processing turns, including continuations after you approve an action. Custom has no daily cap; the conversation limit still applies.
Can Bosco change my resources without approval?
Observe is read-only. Ask requires approval for changes. Auto allows certain operations without approval at every step, but sensitive actions still need approval. Your role always limits available operations.
What access do I need?
Bosco respects your project scope and permissions. Reader and Accountant roles remain in Observe mode for resources. The assistant does not grant additional permissions to your account.
Are these examples live conversations?
No. These are illustrative examples using fictional data. To use Bosco with your project context, open the SailOps console.
The next step is in your project
Start with a question about your project.
Open Bosco in SailOps or speak with the team to see how it works.