Site chat

Chat is how you build in Modulify. It lives in the panel down the left of the editor, beside the live preview, and every change you make by describing it starts there.

One conversation per project

There is one chat per project and it never resets. There is no new chat button, no session list and no way to open a second thread beside the first.

The transcript belongs to the site rather than to you. Everyone who can reach the workspace that owns the project reads the same messages, each one carrying the name and avatar of whoever sent it, and a run a teammate starts streams into your panel too.

That continuity is the point. Context you gave three messages ago is still in play, so "make that section wider" is a complete request with nothing to re-describe.

The panel

The panel opens on the most recent 10 messages and pulls older ones in as you scroll up. When there is nothing left to load, the top reads Start of conversation. A project nobody has written in yet reads No messages in this session yet.

Your workspace's remaining credit count sits above the chat box. Click the number to open the plan and credits modal. See Credits.

Collapsing the panel, and where it goes on a phone, are covered in Tabs and visibility.

Send a message

The box reads Describe what you want to build or change.... Enter sends and Shift + Enter starts a new line.

Along the bottom of the box, left to right:

• + opens the attach menu: Manage connectors, Manage skills, Attach file, Take a screenshot, Pick a file and Pick an attachment.
• The mode picker, Build or Plan. See Plan and Build modes.
• The model picker. See Models and effort.
• A microphone. It records up to 2 minutes behind a level meter and a timer, then transcribes into the box at your cursor. Under a second is refused with Recording too short.
• The send button.

The whole toolbar goes inactive while the preview is still syncing and while a version is being restored, so nothing is sent into a project that is mid change.

For what a message can carry beyond text, see Attachments and context, Skills and Connectors. For how to phrase the request itself, see Writing prompts.

What a running message looks like

Before anything streams back you get an animated indicator with a line that rotates as it works, Working on it..., Fine-tuning..., Polishing the details..., and a live timer counting up beside it. Two phases name themselves instead: Requesting... and Compacting context....

Then the reply builds itself in place.

Thinking

A Thinking... row appears while the model reasons, and settles into Thought for 12s when it stops. Click it to read the reasoning in full.

Actions

Each thing Modulify does shows as a row naming the action and, for file work, the file. Several actions running together collapse into a single row that names the one currently running with a 3/7 counter beside it, and reads Did 7 actions once the batch finishes. A failed action turns that row's icon red.

Click any row to open the activity view, which lists everything the message did, with a Back button and an N actions count in its header.

Task list

Work with more than a couple of steps gets a checklist panel headed 3/5 tasks, striking each step through as it completes. It adds · all done and folds itself away when the last one lands.

Stop a run

A Stop button appears next to the send button while a run is active, taking the microphone's place.

Stopping ends the job for everyone in the project, marks any action still running as stopped, clears the task list and drops a Generation stopped divider into the transcript.

It does not roll anything back. Files already written stay written. To get back to an earlier state, restore a snapshot from Versions.

When it asks you something

A run can pause and put a question to you rather than guess. The question appears in a panel with its options lettered a., b., c., and clicking one answers it and lets the run continue.

You can ignore the options and type your own answer in the chat box instead. Sending it resolves the question rather than starting a new run. Anything sitting in the message queue waits until you answer.

Markers in the transcript

Thin dividers mark things that happened to the conversation rather than to the site. Several carry an info icon with the full explanation.

Marker	What it means
Context compacted	The conversation grew too long, so everything above it was summarized into a shorter context
New session started	The assistant stops carrying the messages above and continues fresh from there, which keeps generations fast
Generation stopped	Somebody pressed Stop
Switched to Plan mode, Switched to Build mode	The mode changed partway through
Approval requested	A plan was presented and is waiting

Neither compaction nor a new session touches your chat history. Every message stays where it was and stays readable. What changes is how much of it the assistant still carries forward, so detail from far back is worth restating.

When a run fails

A failed run replaces its reply with a red block titled Generation failed!, the reason underneath and Error code: with a code like SC-3001. A retry arrow sits in the corner of the most recent reply. Retry deletes that reply and runs the same request again.

Two outcomes come back amber rather than red, because they are not really failures. Generation interrupted reads This generation stopped before it finished. Retry to run it again., and Generation already running means something is in flight for this project already.

With no credits left the message is not sent at all, and reads You are out of AI credits, so this message was not sent.

What chat can and cannot change

Beyond writing your site's files, chat reaches most of the editor. It can run SQL and create a database, read and write storage, set and delete secrets, create, edit and run crons, generate and edit images, call your connectors, query the site's analytics, add and remove languages, publish, and rename the project or change its description.

Three things are deliberately out of its reach, and asking gets you told to do them yourself.

• Visibility and sharing. Chat refuses with visibility and sharing cannot be changed from chat and points you at the site settings.
• Domains, plans, credits and workspace members. No tool exists for any of them.
• Deleting the project, and restoring a version. Both stay manual.

Delete the transcript

Open the Settings tab and scroll to Danger zone. The Delete chat row holds the button, disabled while a generation is running (Wait for the current generation to finish.) and when there is nothing to delete (You have no chat to delete.).

The confirmation reads Delete this chat? and warns that it permanently deletes the transcript for everyone in the project and throws away whatever the team had queued. Your project, its pages and its content stay exactly as they are. It cannot be undone.

Next

• Plan and Build modes covers the approval step and what each mode changes.
• Writing prompts is how to phrase a request well.
• Message queue covers sending while a run is still going.
• Versions is how you undo a run you did not want.