Chat and composer

You work with 3D-Agent in a chat. Type what you want in the composer at the bottom, and the agent does it in Blender.

Send a prompt

• Press Enter to send and Shift+Enter for a new line.
• Press ↑ or ↓ at the start or end of the text to go through your previous prompts.

The composer is locked while Blender isn’t connected, and until you confirm your account email.

Send a message while the agent works

You can type while 3D-Agent works, to correct or add to what it’s doing. Press Enter or click the arrow: your message is queued. It waits at the top of the message box, under Queued, and goes as its own prompt when the run finishes. While the agent works, the message box says Queue a message….

Send now

To give the agent your message without waiting for the run to finish, click Send now on the queued message. It’s added to the run that’s going: the agent doesn’t stop, and reads your message at its next step.

• Until then, your message shows greyed out under the reply, with Added to this run · read at the agent's next step. Once the agent reads it, it moves into the reply, where the agent read it.
• A message sent now doesn’t use another prompt. It shares the run’s steps. See Steps per prompt.
• Images queued with it go with it. A message with documents has no Send now: it waits for the run to finish.
• If the run ends before the agent reads it, it goes back to the queue and is sent as its own prompt, and the app tells you: This couldn't be added to the run, so it's queued. Uses 1 prompt.
• If you stop the run (or it ends with an error, or 3D-Agent closes) before the agent reads it, the message stays in the chat where you sent it, greyed, with Not read and the reason. It isn’t sent by itself. Click Send to send it as a new prompt, or Send now while the agent is working. Its pencil puts it back in the message box, and ✕ removes it.

To stop the agent instead, click the stop button.

The queue

When the run finishes, 3D-Agent sends the queued message as a new prompt. Several queued messages go one at a time, in the order you wrote them. Each queued message uses a prompt, like any message you send. See What uses a prompt.

A queued message can include images and documents. While the agent works, add them the usual way: click +, drag them into the composer, or paste them. See Attach images and Attach documents. What you add goes with the message you queue, and the composer starts empty for your next message. A queued message can be images with no text. The queued message shows its images as small thumbnails, and a paperclip when it includes documents.

• To change a queued message, click its pencil (or its text). The message leaves the queue and goes back into the composer with its images and documents. Send it again while the agent works and it goes back to its place in the queue. If you’re typing another message, send or clear it first: until then the pencil is greyed out.
• To remove a queued message, click its ✕.
• A queued message uses the composer’s settings, such as Plan, at the moment it’s sent. The settings can’t change while the agent works.
• @image and @video requests wait until the run ends. The composer shows Image and video requests can be sent once this run ends.
• Signing out or switching accounts removes all queued messages.

Why wasn’t a queued message sent?

3D-Agent sends a queued message by itself only after a run finishes normally. Queued messages wait for you when you stop the run, when the run ends with an error, when you leave the chat, or when 3D-Agent restarts. A queued message also waits for you when an image or document queued with it can’t be read.

A queued message that waits for you is listed under Not sent, below the queued messages that will send; hold the pointer over Not sent to see why. It keeps its images and documents. Click Send to send it. While the agent is working, the button reads Send now and adds the message to the run without using another prompt (a message with documents goes when the run finishes instead). Click its pencil to change it, or ✕ to remove it.

Stop a turn

Click the red stop button, Stop generating, to end the turn. With nothing typed, the stop button sits where the send arrow usually is.

When you type during a run, the arrow takes that place and the stop button moves to its left. A click on the arrow queues your message and never stops the run. A double-click on the send arrow never stops the run either.

Stopping a run keeps your queued messages but doesn’t send them, and a message the agent hadn’t read yet stays in the chat as Not read. See Why wasn’t a queued message sent?

If the agent asks you a question, the chat shows Waiting for your answer. Answer in the question card, not the composer. Answering doesn’t use a prompt.

Attach images

Click + → Add Images, drag images into the composer, or paste them.

• PNG, JPEG or WebP
• Up to 4 images per message
• Up to 900 KB each and 1,200 KB in total

Use a sketch, a photo or a render you want to match as a reference.

Attach documents

Click + → Add documents or files to add text, PDF, Office or code files, up to 20 MB each. The document becomes part of the conversation.

To share documents with every chat in a project, see Projects and attachments.

Mention objects

Type @ to list the objects in your open Blender scene, and pick one to point the agent at it:

The same menu turns on @image and @video, which use prompts from your monthly plan. See Chat commands.

Plan mode

Plan mode makes the agent write a plan before it changes anything. Use it for big or unclear tasks. It’s available on every plan.

1. Click Plan in the composer. The pill turns orange, and the composer gets an orange dashed frame.
2. Send your prompt: what you want and what it’s for. The agent may ask questions first. Answering them doesn’t use a prompt.
3. The agent replies with a plan and leaves the scene alone. Ask for changes until the plan is right.
4. Under the plan, click Implement to build it in this chat, or New chat to build it in a fresh chat without the back-and-forth. Copy copies the plan.

Implement is also ⌘⇧Enter on macOS and Ctrl+Shift+Enter on Windows. Implement and New chat turn Plan mode off. Otherwise it stays on until you turn it off.

You can also paste a prompt you wrote elsewhere and ask Plan mode to turn it into a plan.

Reasoning effort

The Reasoning effort button in the composer sets how long the agent thinks before it acts. It shows High or Extra-high.

• High is available on every plan.
• Extra-high thinks longer before acting, which helps with hard problems. It uses more of your plan’s budget per turn. Pro and Ultra include Extra-high and start on it. On other plans, Extra-high shows a lock, and clicking it opens the plans.

During your first-month boost, reasoning effort is set automatically. Reasoning effort isn’t used for images and video, so the button is greyed out while an @image or @video chip is in the message.

Approve a tool call

When the agent wants to use a tool from an MCP server you added, 3D-Agent asks first with Tool Approval Required. The dialog names the tool and shows its Tool Parameters. Check them before you approve: a tool, or text in the chat, could try to make the agent do something harmful.

• Deny skips this call.
• Allow Once runs this call.
• Allow in thread runs this call and allows that tool for the rest of the chat.

Tool approvals apply only to the chat they were given in. 3D-Agent’s own Blender tools don’t ask for approval.

Long chats

Every turn sends the chat’s history, images included, so very long chats reply slower. You don’t need to do anything: you can keep working in the same chat.

A chat with too many large images can still grow too big to send. Then This chat has too many large images offers Continue in new chat. A new chat starts without the conversation history, but your work stays. Your Blender file and its checkpoints don’t change.

Next steps