Skip to content
BlogStart for free

Chat

Chats, commands, and context

Use chats to organize requests and responses. Chats in the same project share the project files, so a change in one chat affects the others.

Use the mode selector in the prompt composer:

Mode What it does
Plan Discuss the feature and agree on an approach before making changes.
Build Ask Buildryn to implement a change in the project.

When a plan is ready, choose Implement plan on its card, or switch to Build and request the agreed implementation. Wait for completion, then inspect the files and resolve change review.

For help writing the request, see Prompting best practices.

  1. Open the chat-title selector to see existing conversations.
  2. Select a chat to load its saved history.
  3. Choose New chat for a separate discussion within the project.

Buildryn generates chat titles from the conversation. Use Load older messages and Load newer messages where available to move through history.

A new chat is useful for a new feature or a focused debugging discussion. To experiment on a separate copy of source, duplicate the project instead.

Open the conversation selector and use Delete chat for the selected conversation. Read any confirmation before proceeding. Copy information you need first.

Deleting a chat removes its conversation history while leaving project files in place. To restore files, use change review or historical recovery.

Type @ and select an existing file, or use Reference in chat from that file’s explorer actions. Explain the reason for the reference: inspection, a targeted edit, comparison, or a bug in that file.

Save your edits before asking the AI to inspect a file.

In a browser that supports speech recognition, select Speak your prompt using the microphone control. Allow microphone access if prompted, then speak your request. Use the control again to stop listening.

Review the recognized text, especially command names, file names, and Minecraft identifiers. Check the mode and submit when ready.

Speech recognition uses US English. Unsupported browsers hide the microphone control; you can type or paste your prompt instead.

Type / at the start of the prompt to open the command picker, then select a command. These controls perform a project action rather than sending a natural-language feature request.

Command Action When to use it
/repair Repair the latest failed build using AI credits. A Paper or Fabric build failed and you want help fixing it.
/build Build or package the project. Saved source is ready for a fresh artifact.
/deployment Start a deployment from the latest artifact. A successful build is ready for a test session.

Available commands depend on the project type; /repair is available in Paper and Fabric projects. Build and deployment permissions still apply. A deployment uses the latest artifact, so first build any source changes you want to test. The command picker is the reference for available commands; do not assume arbitrary slash words are supported.

The AI has a limited working context containing relevant project content, conversation state, and a summary of earlier work. Open the context indicator to inspect usage and the displayed contributions.

The percentage shows how much of the AI’s working context is in use. Check Settings → Billing for your credit balance and charges.

Keep current requirements explicit and reference the files that matter to the task. Avoid repeatedly pasting large unchanged material when the project already contains it.

Buildryn automatically summarizes earlier conversation context when needed to make room for ongoing work. You do not need to run a command. Project files remain unchanged.

A summary can condense earlier details. Restate exact requirements, identifiers, or compatibility rules when they matter to your next request.

During a run, the chat can display progress stages, public summaries, tool activity, response text, and file updates. Wait for completion before treating a partially displayed result as final.

If the page disconnects, return to the project and inspect saved history and run state. You can run one request at a time in a project. Your account may also limit concurrent requests across projects.

Use the stop-generation control to interrupt a request. Wait until the interface confirms it has ended before submitting another. Inspect saved files and pending change review; stopping a request does not undo changes already applied.

Buildryn may charge for AI work completed before cancellation. If the connection drops, reopen the project and check saved history and run state before retrying.

Use Good response or Bad response to rate a result. Copy copies response text. Copy message link helps point collaborators to the exact message; they still need project access.

Revert to this message is available only when the message has suitable project history. It changes project state, so read history and recovery before using it.

  • Enter: submit the prompt when the composer is ready.
  • Shift + Enter: add a line break.
  • Ctrl + P: toggle Plan/Build in the application.
  • Escape: close an open picker or relevant preview.

See editing files for editor shortcuts and notifications for completion notifications while the app is open.

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.