The workspace

Workspace

The workspace has three areas: the chat, the preview, and a three tab panel on the right.

The chat and its two threads

A switch above the input holds two values: Code and Automations. Each thread keeps its own memory. MaShop never reads the turns of one thread inside the other.

Four actions sit on a reply.

• Copy puts the answer in your clipboard.
• Retry re sends your previous message exactly as it was. That is a new turn, and it is billed.
• Stop cuts the generation. What already arrived stays, marked Interrupted. The cancellation reaches the provider, which stops generating and stops billing.
• New conversation opens a blank thread. MaShop starts with none of the previous messages.

The Conversations panel lists your threads, fifty at most, newest first. Each collaborator sees only their own.

The preview shows what is online

The middle pane is a frame on your deployed site. Before the first deployment there is nothing to frame, so MaShop shows a placeholder instead of a broken runtime.

While the first build runs you get a clickable address rather than a frame. That address may not serve the fresh build yet.

So the preview trails the editor by one deployment. To see a change live, publish it.

Tasks, Files and Versions

Tasks is the default tab. It is a chronological feed of every tool call in the current conversation, newest first. Each line shows working, done or failed, with its duration. The feed keeps running across turns and resets when you change conversation.

Files lists the pages of your site and of your back office, grouped by application, plus your email templates. Clicking a page shows it in the preview. Code opens in the editor.

Versions has its own page in this section: Undo and restore.

Editing by hand stays inside MaShop

Ctrl+S saves your edited files in the MaShop workspace. Nothing is sent to your GitHub repository.

Update then rebuilds your site from GitHub, so a hand edit never reaches the live site. There is no button anywhere that pushes those edits.

For anything you want online, ask the assistant to make the change. Its generations do commit to your repository.

Workspace files are capped at 5 MB per file, 50 MB per upload and 200 files per request.

Deleting a file or a conversation cannot be undone. Neither has a trash. A deleted file leaves the workspace at once, and a deleted conversation is erased with its messages.

Build logs

View logs opens the build output in the bottom drawer, streamed live as it happens, with a status: building, ready, failed or canceled. This is where the reason for a failed update is written, and the only place it is written.

Who can do what

Three roles exist: viewer, editor, owner. A viewer cannot use the chat at all, because a single message can trigger a tool that changes the project.

The refusal a viewer receives reads Store not found, so a blocked viewer may believe the project has disappeared. It has not.

On a phone

The same workspace, driven by a bottom dock. The publish button is called Deploy there, and it never changes name.

On the Automations tab the dock drops four commands: Deploy, Settings, GitHub and Supabase. They belong to code work, and their width was crowding out the Automations navigation. Deploy and Settings stay in the profile menu. GitHub and Supabase stay in the top bar, outside Automations.

Rate limits

Ten messages per minute, one hundred per hour. Both are counted on real generations, and the message tells you when the counter resets.