Buff Code
If something does not work
Buff Code, workspace and connector messages during installation, sign-in, context choice, model and tool calls: what they mean and what to do.
All the messages below are real: this is what Buff Code, the workspace and the connector actually write.
Find yours and do what the right-hand column says. Messages that the connector writes come in Russian
only; they are quoted as printed, with a translation.
| What you see | What it means and what to do |
|---|
buff: command not found after installation | The path is in the shell profile, but the current terminal has not read it. Open a new terminal or run source ~/.bashrc (or your shell’s profile). |
| macOS: “The developer cannot be verified” | The app is not notarised by Apple. System Settings → Privacy & Security → “Open Anyway”. See Installation. |
| Windows: “Windows protected your PC” | “More info” → “Run anyway”. Once. |
| The app hangs on the splash screen | Usually another copy of Buff Code started earlier. Close all windows and buff processes and start again. |
| “Buff Code is not set up: run buff to sign in to Buff, or connect your own provider with buff auth login” | buff run or buff models was started without a terminal (in a script, in CI) and cannot ask for a sign-in. Do the first sign-in interactively with buff in the same folder, or connect your own provider. |
| What you see | What it means and what to do |
|---|
| “Invalid connector address: …” or “The connector address must start with https://…” | The address does not parse as a URL. Take it from the workspace: the connector’s card, the “Buff Code sign-in” line — with https:// and the port. |
| “The company connector did not answer: …” | The gateway is unreachable from your machine: wrong network, VPN, the port is closed or the connector is stopped. Check with curl -I <address>; the administrator checks the connector log for the developer gateway: listening line. |
| A certificate error when connecting | The gateway’s certificate was issued by your certificate authority, which the machine does not trust. Point the NODE_EXTRA_CA_CERTS variable at its file before starting buff, or ask the administrator to install a public certificate. |
| “The backend did not issue a sign-in code” | The connector is connected to Buff, but Buff did not answer. Try again in a minute; if it repeats, the administrator checks the connector’s state in the workspace. |
| “The sign-in code has expired — start signing in again” | The code lives ten minutes. Run buff again and confirm the new code. |
| “Sign-in was declined in the cabinet” | “It wasn’t me” was clicked on the sign-in page. If it was you — start signing in again. |
| Workspace: “Too many wrong codes. Wait 10 minutes and start the sign-in in the console again” | Five wrong codes within ten minutes. Wait, run buff again and enter the new code carefully: eight letters, no digits and no vowels. |
| “The sign-in is damaged — sign in again” | The device was revoked in the workspace or its key on the machine did not match. Run buff and sign in again; if it was not you who revoked it, ask the organisation’s owner. |
| “You are not in any Buff organization yet…” | The sign-in went through, but you have not been added to any organisation yet. Ask the administrator to add you and choose the organisation again. |
этот коннектор работает для организации X, а вход выполнен в другую (“this connector serves organisation X, but the sign-in is to another one”) | You confirmed the sign-in in another organisation. /org — choose the one the connector is bound to. |
| What you see | What it means and what to do |
|---|
| “Choose an organization first: /org” | No context is chosen in this folder yet. Run /org, then /project. |
| “This is not among what is available to you: an organization, project or space without access” | What was chosen is no longer available to you — you were removed from the project or the project was deleted. Choose another one with /project. |
| “First choose a project in the Buff Code working context (/project)” | The project repository tools need a chosen project: “No project” is not enough for them. /project. |
| In another folder Buff Code asks for the organisation again | By design: the context is stored per folder. The sign-in is still one. |
| What you see | What it means and what to do |
|---|
| “The company connector returned no models for the organization X” | The administrator has not chosen a model for “Task development”, or the organisation has no plan. See Models and usage. |
/models is empty, there is no Buff provider | Not signed in or no context chosen. Check the status bar; /org. |
| Above the input field: “No model — sign in to Buff or connect your own provider” | You have not signed in yet (or clicked “Later” in the introduction), and there is no own provider either. “Sign in to Buff” and “Connect the provider” are right there. |
| A refusal due to the balance | The organisation’s balance has no funds. The owner can top it up; the turn is recorded but not charged. Balance and runway — “Balance and spending” (/balance). |
коннектор не достучался до Buff — попробуйте ещё раз (“the connector could not reach Buff — try again”) | The connector lost its connection to Buff. Try again; if it lasts, the administrator checks the connector in the workspace. |
| What you see | What it means and what to do |
|---|
/mcps has no buff, knowledge, repos servers | Not signed in, no context chosen, or the connector is old: knowledge needs v0.14.0, repositories — v0.15.0. |
| The model wrote “adding an entry”, but there is no entry | In buff run confirmation forms are cancelled, and nothing is written without confirmation. Work in the interface — the form will appear. See Knowledge base. |
| “Buff is still preparing the answer: the project repository is loading for the first time or the search is very broad” | Not an error: the first call in the project or a heavy search. The model repeats the call half a minute later. |
| A connection’s writing tool refused | The connection’s account has no write permission. This is a limit of the connection, not of Buff Code — ask the connector administrator. |
| What you see | What it means and what to do |
|---|
| Your own MCP server: “Did not start — Command not found…” | The server’s program is not on this machine or the path is wrong. “Edit” in “Extensions → MCP”; see Extensions. |
| A project hook or command does not run, and a bar about a check is above the input field | What came from the repository does not run until you have looked at it. “Check” in the settings, or /trust. |
| “Send the first message of the session: the commit message is composed in its context” | “Compose the message” in the Git window was clicked in a new session. Send a task, then try again — or write the message yourself. |
| “The model did not suggest a message — write it yourself or try again” | The model did not answer with text. Try again or write the commit message yourself. |
| An automation on the “Awaiting permission” tab | The run reached an action that the run mode does not allow. Open its session and answer the request; the mode is changed under “Edit”. |
| A workflow does not start, the agent edits the script | The workflow script failed the check — the agent got an error with a line number and fixes it itself. The run’s progress — “Workflows → Runs”. |
| What you see | What it means and what to do |
|---|
| “Only the organisation owner sees other people’s development sessions” | You opened another developer’s session without being the owner. By design. |
| “Development sessions are unavailable right now” | The record store is temporarily unavailable; work in Buff Code continues and records are not lost. Try again later. |
| “Calls without saved text” in a session | The turns had no text message from the developer — for example, only service calls. Expand “Service calls (N)”. |
| “No sessions in the selected period” | No session matched the filters for “Ask about the selection”. Widen the period or remove a filter. |
Write to the feedback page or to info@buff.systems: the version (buff --version),
the system, what you did and what you saw. Session records help sort it out faster — give the session’s
title or time.