Chat and Agent mode

Start from home

Chat opens on a centered composer with six creation modes underneath — Image, Video, Websites, Docs, Sheets, and Slides. Picking one opens that mode's page, with starter prompts that prefill the composer and wait for your edit; nothing sends until you do. The active mode shows as a dismissible chip in the composer, and moving between home and a mode keeps your draft and any staged attachments.

Choose a mode

• Ask is read-only. Use it to explain, compare, summarize, or inspect without making changes.
• Plan researches what's available and returns an inline markdown plan for you to review before anything runs.
• Agent (the default) uses the tools and connected services available in the current context to complete work.

Change mode from the selector beside the chat input before sending a message.

Recover or branch a turn

Every accepted user message creates a checkpoint before Cheqq begins the turn. Use Restore or Fork from the divider immediately above that message:

• Restore returns the conversation and captured local state to the point before the message while retaining the abandoned future as a recoverable branch.
• Fork starts an independent conversation from that earlier prefix and, on supported surfaces, duplicates the primary artifact.
• Undo restore returns to the preserved future after the latest applicable restore.

External actions that already happened are not reversible. A partial checkpoint identifies local state Cheqq could not capture. See History and recovery for the full behavior and artifact boundaries.

Write an effective request

State the outcome first, then add constraints, the relevant Wapp or service, and how you'll judge success. Attach a file when the task depends on its contents.

For example:

Review the attached vendor list, identify missing contact details, and plan the updates. Do not change any records yet.

Generate images and videos

Open the + menu beside the prompt and choose Create image or Create video to force that output. The model picker only lists admin-approved models that can produce the selected output, including each model's supported input-modality icons and current credit burn.

The picker shows the models you've curated. Manage models (pinned at the bottom of the picker) opens the full approved catalogue grouped by provider, with search, modality, and pricing hints — tick the ones you want offered and the picker shows only those. Your selection follows your account; if you never curate, the picker shows the admin-featured set.

You don't have to use the menu — in ordinary Agent mode, Cheqq can decide to generate an image or video on its own whenever it judges that's the best response to your request, as long as the workspace has an approved model for it. Use the + menu when you want to guarantee that output or pick a specific model; otherwise just describe what you want.

In video mode, describe the scene, subject, camera movement, and desired outcome. You can attach an image for models that support image-to-video generation. Generated videos appear in the conversation with playback controls and remain available as private workspace files.

Video generation can take several minutes. The generation is priced by its actual duration and selected resolution/audio variant rather than as text tokens.

Edit an existing image or video

Generation can build on what's already in the conversation. Asking for a change to an image — "make it warmer", "remove the background" — edits the picture you're looking at rather than starting over.

Videos can be edited too, on models that accept video input. Video mode gains an operation control — Generate, Extend, or Remix: extend continues a clip past its last frame, remix restyles it. Attach the clip you mean, or leave it off and the conversation's most recent video is edited. You can also just ask the agent — "extend this video by another scene" — from an ordinary Agent-mode turn. Edits are billed at the model's own video-input rate, and every edited clip records its lineage back to the original.

Control tool approval

The tool-approval control beside the chat input has three options:

• Manual — Cheqq asks before every tool call runs, saved as your default.
• YOLO — tool calls auto-approve, saved as your default.
• YOLO (this session only) — auto-approves for the current session without changing your saved default; it turns itself off when the session ends.

Turning on persistent YOLO shows a confirmation dialog first — it applies to every tool call, including ones made by delegated subagents, and can mean unintended changes if something goes wrong. When Manual is active, each proposed tool call appears as a card with Approve and Deny — read the action and its target before approving anything that changes data or an external service. Sending a new message while an approval is still pending automatically denies it.

Watch delegated work

When Cheqq delegates part of a request to a subagent (for example, building out a workflow), you'll see a nested card with that subagent's real streamed output and tool calls underneath, not generic "working…" filler text. The card's header reflects its actual state: running, awaiting your approval, completed, or errored.

Follow tool activity

While the agent works, its thinking, narration, and tool calls stream into one timeline. Tool calls are described in plain language from what they're actually doing — "Searching the web for supplier reviews" rather than a raw tool name — and on models that expose their reasoning, the agent's thinking streams between them. The timeline highlights the current step while the turn runs and collapses to a one-line summary when it finishes; open it to read the full trail, which survives reloading the thread.

Approvals, browser handoffs, plans, rich results, generated artifacts, and delegated-agent cards remain separate so an important interaction cannot disappear inside the timeline.

Work from a plan

When Plan mode presents a plan, review its scope, summary, and any clarifying questions it asks first. Selecting Implement this plan switches the conversation to Agent mode and starts the work as a tracked task list; Dismiss leaves the plan in place without acting on it.

If a run stalls or returns an error, keep the conversation open and follow Troubleshooting.