Operator and Chat

Clear updates

All teams use the same communication rules: lead with the answer or result, explain its effect, and ask only for a decision you need to make. Updates distinguish drafts, scheduled work, changes awaiting approval and completed work. A queued action is not reported as finished.

Engineering explains the bug, change and tests directly. Business and support updates use everyday language. Internal errors and tool details stay in the separate technical details view when needed.

Suggestions

New chats show compact suggestions below the message input. Select one to fill an editable draft, or choose View all suggestions to see every current team suggestion with its rationale, review time and supporting work. Filter by team when useful. Use in chat opens a draft; review or edit it and send when ready. Choosing a suggestion never starts work by itself.

If a suggestion changes before you open it, the chat offers the latest suggestions. Refreshing the page’s learning data does not overwrite a draft you are editing.

The organization chat is always available. It is appropriate for questions, synthesis, planning, and deciding whether an idea should become tracked work.

Conversation Stays Conversation by Default

Sending a message does not automatically create a task. This prevents every question from becoming operational clutter and gives the operator room to clarify scope before committing resources.

Use chat to:

• ask what Context currently says;
• compare alternatives;
• clarify the desired outcome;
• identify the owning department;
• discover missing evidence;
• review a proposed plan; or
• decide whether durable execution is warranted.

When to Create Durable Work

Create a task when the request needs one or more of:

• ownership;
• dependencies;
• scheduling;
• attempts and retries;
• files or artifacts;
• human blockers;
• consequential external actions; or
• an outcome that should inform future work.

Write Better Requests

State the outcome, constraints, evidence, deadline if real, and what requires approval. For example:

Review the last 30 days of support themes, use only connected read-only sources, group recurring problems by product area, and prepare an evidence-linked engineering brief. Do not contact customers or change tickets.

This gives the operator a bounded workflow without dictating every implementation step.

Essential Decisions

When a missing decision materially changes the work, Chat can ask one to three structured questions. Choose an option or enter your own answer, then select Send answers. Decide later records a deferral and lets the conversation continue; it does not authorize work that depends on the decision. These questions are separate from explicit approval to retain a Context note.

Attachments

Use attachments when the file is part of the current conversation. Use organization Context when the information should guide future work across chats and tasks.

Normal chats accept Markdown (.md, .markdown), text/data (.txt, .csv, .json, .yaml, .yml, .toml), PDF, and common raster images (.png, .jpg, .jpeg, .webp, .gif). Each file must be non-empty and no larger than 50 MB; each message may include up to five attachments. Oblive validates text encoding or the file signature and rejects mismatched MIME claims. SVG, video, archives, executables, unknown extensions, and extensionless binaries are not accepted. Onboarding sources retain their separate reference-document policy.

If a Response Stops

Pending assistant messages are durable and can be recovered after a lost live signal or restart. Check service health before resending the same instruction; duplicate user instructions can create conflicting intent even when runtime execution itself is fenced.

Control Work From Chat

Ask Chat to create or edit a schedule, pause or resume it, change a task, stop new work from starting, answer a team question, or approve a pending change. Chat reads the current record and reports the saved result. If the target or a necessary decision is unclear, it asks a focused question.

For a supported integration change, an explicit request such as “send this reply to Alex” counts as approval for that change. It does not change the approval rules for future autonomous work. Read-only connections, disabled tools and selected resource limits still apply. MongoDB, Upstash and Google Analytics currently expose reads only; Chat explains a missing capability plainly.

Provider timeouts do not prove that a change failed. Chat keeps the same action record, explains what is uncertain and can record your confirmed result after you check the provider. It does not repeat an uncertain send or purchase. External login and credential entry still use integration setup.