Faster CLI is an advanced chat surface for runtime-oriented workspace help. Use it when normal workspace chat needs deeper diagnostic context or a more technical review path.

When to use this guide

• You need help understanding why a workspace action did not complete.
• A teammate asks for a more technical review of content, configuration, or workflow behavior.
• You want a diagnostic conversation separate from routine content drafting.

Before you start

• Know the workspace area or customer workflow you want to improve.
• Gather approved copy, media, offer details, or customer context before publishing anything public-facing.
• Decide who needs to review the result before it goes live or affects customers.

Do it manually

1. Open Faster CLI from Workspace or the app switcher.
2. Confirm the selected provider before starting technical work.
3. Choose Ask for review-first help or Auto for approved runtime work that can keep moving.
4. Describe the issue, workspace area, and expected result.
5. Reference the page, post, form, customer, campaign, file, or runtime process when relevant.
6. If the runtime is still connecting, send once and let Faster queue the message.
7. Use session history or Runtime processes when you need to reconnect, inspect active work, download a transcript, or start a clean session.
8. Return to the normal workspace editor for final approval or publishing.

Runtime composer controls

• Use the provider switcher when you need to move between available runtime providers for the next message or session.
• Use Ask when you want Faster to explain, review, or propose a next step before changes. Use Auto only when you are comfortable letting the approved runtime path continue without stopping after every step.
• Use session history to return to recent runtime work, start a clean session, or download a transcript when a teammate needs the context.
• Open Runtime processes when you need to see which runtime sessions are active, reconnecting, or available to stop after troubleshooting.

Session and process behavior

• If you reload or reopen the workspace, Faster looks for the active runtime session for the same workspace context and reconnects to it instead of starting a duplicate process.
• The session history, transcript, selected provider, and runtime process stay tied together while the session is active.
• Start a new session when you intentionally want a separate thread, a different provider, or a clean diagnostic trail.

Messages while connecting

If you send while the runtime is still connecting or reconnecting, Faster queues the message and sends it after the process is ready. Do not send the same message again unless the composer shows that the queued send failed.

Ask Faster AI

Try this prompt:

Review why this page update is not showing the expected content, list likely causes, and do not make changes until I approve the next step.

Review before publishing or using

• Use Faster CLI for focused diagnostics, not as a place to store permanent business rules.
• Do not paste passwords, tokens, or private customer details into chat.
• Confirm public-facing changes in the normal editor or preview before publishing.

Common mistakes

• If the answer is too technical, ask for a plain-language summary and next action.
• If several areas are involved, attach or name one artifact at a time.
• If a change could affect customers, payments, or live pages, pause and review manually.

Placeholders to replace later

• Screenshot placeholder: add an annotated screenshot with private customer data blurred.
• Video placeholder: add a short walkthrough that shows the manual path, the AI-assisted path, and the final review step.

Faster AI skills overview

For where Faster CLI fits as the advanced diagnostic surface alongside normal skill-shaped workspace chat, read the AI skills article. Faster AI Skills: Teach Your Workspace New Tricks.

Connected workflows

• Review AI drafts before publishing
• Review and approve AI page changes
• Create a lead capture form
• Create social posts