Chat

The chat panel is the primary way you interact with Coframe Agent. You describe what you want in plain language, and the agent responds with its plan, progress updates, and results — all in real time.

What it looks like

How the conversation flows

1. You describe your intent — “Make the hero section feel more premium” or “Add a three-tier pricing table below the fold.”
2. The agent acknowledges and plans — it extracts requirements, creates tasks, and tells you what it’s going to do.
3. Progress streams in — as the agent works, you see tool calls, file edits, and reasoning in the chat.
4. You can follow up — ask for adjustments, clarifications, or new work at any point. The agent keeps full context from the session.

What you see in the chat

The chat renders more than plain text. Depending on what the agent is doing, you’ll see:

• Text responses — the agent’s reasoning and status updates.
• Tool call cards — expandable cards showing file edits, browser actions, shell commands, and other tool invocations.
• Reasoning blocks — chain-of-thought sections that show how the agent is thinking through a problem.
• Code snippets — inline diffs and highlighted code blocks.

All of these render through the same component pipeline used in the production editor, so what you see in the docs matches exactly what you see in the app.

Tips for effective prompts

See the chat tips guide for detailed advice on writing prompts that get the best results. The short version:

• Be specific about outcomes — “Make the CTA green” is better than “Make it look better.”
• Reference existing elements — “The hero section” or “the pricing cards” gives the agent clear targets.
• State constraints up front — “Keep the existing layout” or “Don’t change the navigation” prevents unwanted changes.