Skip to main content
Overcut includes a chat interface, so you can work with the platform conversationally. Anything you can do in the Overcut UI, you can ask Overcut to do via chat: explain a workflow, trigger a run, read execution logs, or set up agents, skills, and MCP servers. Select Assistant in the project sidebar to open the full-page chat. You can also pop the chat out into a floating panel or dock it to the side of the screen and keep the conversation going while you work.
Overcut chat acts as you. Everything it does runs with your own user permissions, so it can only see and change what your workspace role allows.

​
What you can and cannot do via chat

Chat covers the Overcut platform itself: if you can see it or configure it in the UI, you can ask for it in chat. For example, you can ask Overcut to:
  • Explain, create, and edit workflows, and trigger workflow runs
  • Read executions and logs, and explain why a run failed
  • Create and configure agents, and assign skills and MCP servers to them
  • Register project skills, install MCP servers, and manage project secrets
  • Configure repositories, channels, custom-event webhooks, and orchestrations
Chat does not work directly on your integrated external systems. Overcut will not open a pull request, push code, update a ticket, or post a chat message from the conversation. That work runs through workflows, with their guardrails, approvals, and settings. Ask Overcut to build or trigger the right workflow instead.

​
Write a message

When the full-page chat is empty, the input cycles through example prompts to show the kinds of questions and requests you can start with. They are inspiration, not commands: type your own message in your own words.
  • Press Enter to send your message.
  • Press Shift+Enter to add a new line.
  • The send button stays disabled until your message contains text, so empty messages cannot be sent.

​
Ask questions and inspect context

Read-only help is available immediately, with no preparation. For example, you can ask Overcut to:
  • Explain what a workflow does and how it is triggered
  • Summarize a workflow execution or read its logs to explain why a run failed
  • List the agents, skills, MCP servers, or repositories configured in the project
  • Answer questions about how to use the platform
Read-only requests never change your project configuration or workflows. If Overcut cannot access the context you are asking about, it tells you what is missing.

​
Task Overcut with changes

When your request changes something, such as creating a workflow or installing an MCP server, Overcut may pause to prepare before it acts. During that preparation you may see two status messages:
  • Loading skill: Overcut is loading a built-in task skill that provides the guidance and capabilities for your request.
  • Equipping tools: Overcut is enabling the write tools the action needs.
Both states are expected behavior, not errors. There is nothing to install or configure; Overcut continues on its own after a short wait, and the loaded capabilities stay available for the rest of the conversation.
Built-in task skills are loaded by Overcut during a conversation. They are separate from the repository-backed Skills your team adds to a project and assigns to agents.

​
Suggested next messages

After Overcut replies, a suggested next message may appear as ghost text in the input. Press Tab to accept it, or start typing to replace it with your own message. Suggestions only appear when there is a clear follow-up, so not every reply produces one.

​
Conversation history

Recent conversations are saved per project, so you can reopen a thread and continue where you left off. History is stored in your browser, and Overcut automatically removes old conversations and caps how many are kept per project, so the oldest threads eventually disappear.

​
Confirmations and permissions

Preparing capabilities does not bypass safeguards. For sensitive or destructive actions, Overcut asks for confirmation before it continues, and your workspace permissions and approval requirements still apply. If your permissions do not allow an action, Overcut cannot complete it.

​
Troubleshooting

If a request does not complete, check for these common causes:
  • Missing permissions: your workspace role may not allow the change you asked for.
  • Unavailable context: Overcut may not be able to read the workflow, execution, or resource you referenced. Ask it to inspect the available context first.
  • Confirmation pending: Overcut may be waiting for you to approve a sensitive action.
  • Outside chat’s scope: work on external systems, like opening a pull request, belongs in a workflow. Ask Overcut to build or trigger one instead.