Messages | Borago Board

When the app shows you a sentence, find it here by where it appeared. Each entry gives the sentence as the app words it, what it means, and the next step. A variable part, such as a port, a project name, a model or a time, is written in square brackets. A sentence that contains punctuation the site does not otherwise use is set in code, unchanged. The states behind these sentences are on the States page.

Where a sentence names the provider, the app prints its own label for the service, which is Claude, Codex for OpenAI, Grok, Gemini or Self-hosted model.

Banners at the top of the board

These strips sit under the top bar. The Docker ones appear only on the desktop and on a browser on the local network, since they are about the machine that runs the containers. Nothing shows until the board has tried and failed, and a state has to hold for a few seconds first.

Message	What it means	Next step
Docker is not set up on this machine. Project tasks run inside Docker containers - the board can install it for you.	No Docker command was found anywhere on this machine.	Press Set up Docker. The guide installs Docker with one administrator approval on Linux, or downloads the official Docker Desktop installer on macOS and Windows. See Installing Docker with the app.
The Docker install did not complete. The setup guide has the remaining steps.	A guided install ran and failed.	Press Open Docker setup. The guide shows what failed, a Try again button and the manual commands with copy buttons.
Docker is running, but this user cannot access it. The board can fix that with one administrator approval.	Linux. The daemon is up and this user is not in the docker group.	Press Fix access. One password adds your user to the group.
Your user was added to the docker group. Borago Board has to restart to see it.	The fix worked. A running program cannot pick up a group change on its own.	Press Finish, then Restart Borago Board now in the guide. Logging out and back in also works.
Could not fix Docker access. [reason]	The group change failed.	Press Open the fix and read the reason. The manual command is in the guide.
`Starting Docker… this can take a minute.`	Docker was installed but not running, and the board launched it. Docker Desktop takes up to a minute to boot its virtual machine.	Wait. The strip disappears when the daemon answers.
Docker is installed but not running. Starting it needs your administrator password.	Linux. The automatic attempt is not allowed to raise a password prompt, so the board stopped short of starting the service. A manual command may follow.	Press Start Docker, which raises the prompt, or run the printed command yourself.
Docker is installed but not running. [reason]	The launch failed or the daemon did not come up within about a minute. A manual command may follow.	Press Start Docker to try again, or start Docker yourself. Check Settings, Docker, where Start Docker automatically decides whether the board tries on its own.
Docker Desktop is still being installed. [reason] The board checks again shortly.	macOS. Docker Desktop is in Applications but Finder has not finished copying it, so opening it now would report it as damaged.	Wait. The board retries by itself for up to fifteen minutes. Start Docker forces a try.
`Installing Docker… keep the app open until it finishes.`	A setup job is running, whether or not the guide is open. Quitting the app mid-install can leave the package manager interrupted.	Keep the app open. Show progress opens the guide. The same strip says gVisor or Rosetta 2 when that is what is installing.
Docker is not installed or not reachable on your desktop. Project tasks run inside Docker containers and cannot be executed until Docker is available there.	Shown on the cloud browser and the phone. The connected desktop reports no Docker.	Fix Docker on the desktop. It cannot be started from a browser or a phone.
Update required to keep cloud sync working. This version is no longer supported for sync (update to [version] or later). Cloud sync is paused until you update. Your local board is unaffected.	The cloud refuses records from a desktop older than its minimum version.	Update the desktop app. Sync resumes on the next start.
Another computer is now linked to your account. Cloud sync is paused here. Your board keeps working, and nothing you do is lost - sign in again from Settings to link this computer and send it up.	Only one desktop syncs per account, and another one signed in. This one stopped syncing and its remote terminals stopped.	Open Settings, Account and sign in again. That links this desktop back and sends everything it changed meanwhile. The other desktop then gets this banner.

The To Do column

A hold banner appears at the top of the To Do column when the queue is not starting anything in a project. It has a label, a sentence and sometimes a time. A Resume button appears in the column header only where pressing it can do something. Manual runs with the Run button are never held.

Message	What it means	Next step
Auto-run paused - blocked work ([n] waiting) - Every To Do task overlaps blocked work on "[task]". Answer, retry or close it to continue.	Each queued task's text overlaps a Blocked task's, so starting one would step on half-done work in the shared container.	Open the named task and answer its question, move it back to To Do, or close it. No Resume is offered because the hold would return at once.
Auto-run paused - waiting on a prerequisite ([n] waiting) - Waiting on "[task]" to finish. Every To Do task declares a prerequisite that has not finished yet.	Each queued task names another task as a prerequisite with a task mention, and that task is not done.	Finish or close the prerequisite, or remove the mention from the waiting task's text.
Auto-run paused - provider rate limit - The provider returned a rate limit. Tasks already running are not affected. Resumes at [time].	The provider answered a run with a rate limit. The time is a real deadline.	Wait, or press Resume to run anyway.
Auto-run paused - waiting until [time] before starting anything new. Tasks already running are not affected.	The app restarted during a rate limit wait, so only the wait time is known.	Wait, or press Resume.
`Auto-run paused - sign-in needed - Sign in again to resume. The stored credential was rejected, so nothing new will start; runs resume by themselves once the new sign-in verifies.`	The provider rejected the stored API key, on a run or on the free check before one. Nothing was spent on the check.	Open the project's AI Auth tab and enter the key again. Saving a key the provider accepts lifts the hold. Resume also appears.
Auto-run paused - cost budget - [provider] spend has reached this machine's [budget] budget (about [spent] so far). Reset the spend to resume.	This machine's estimated spend for the provider reached the budget set on the project. Other providers in the project keep running.	Open the project's AI Auth tab, the provider's card, and press Reset spend or raise the budget. There is no Resume for this hold.
Auto-run paused - a task failed every retry - "[task]" failed every retry, which pauses the whole project queue. Resume to try again.	One task used up its six attempts. The whole project queue stops, not only that task.	Read the task's Blocked comment, fix the cause, then press Resume.
Auto-run paused - API credits exhausted - The [provider] API key has no remaining credits, so every run would fail the same way. Top up the provider account, then resume.	The provider account is empty. Not a rate limit and not this machine's budget.	Add credit at the provider, then press Resume. The blocked task's comment names the provider's billing page.
Auto-run paused - a task hit an error a retry cannot fix - "[task]" failed with an error a retry cannot fix ([error]). Fix it on the task, then resume.	The request itself was refused, for example a bad request or a forbidden model. A retry would fail identically, so the queue paused on the first failure.	Read the error on the task, change the task or the project settings, move the task to To Do, then press Resume.
Auto-run paused - a task hit an error a retry cannot fix - "[task]" could not reach [provider] after 6 attempts and the provider reports no incident - restart the project's container (a network change while it runs breaks its connectivity), then resume.	Six attempts failed to reach the provider while its status page was green, so the fault is almost certainly the container's own network. A wifi or hotspot change while the container runs is a known cause.	Restart the container from the board's container controls, move the task to To Do, then press Resume.
Auto-run paused - a task hit an error a retry cannot fix - "[task]" hit [provider] server errors on 6 consecutive attempts. Wait for the provider to recover, then resume.	The provider's status page confirms a problem.	Wait for the provider, move the task to To Do, then press Resume.
Auto-run paused - no access to the chosen model - Your plan has no access to [model], so every run would fail the same way. Pick a model your plan includes, or enable usage credits, then resume.	The provider refused the model, saying it requires usage credits. No wait fixes it.	Pick another model for the task or project in the AI Roles tab, or enable credits at the provider, then press Resume.
Auto-run paused - allow Docker access through the firewall - Container management is on, but this machine's firewall is blocking the container's access to Docker (port [port]). [rule]	With container management on, the container has to reach the policy proxy, and the host firewall drops that connection. Checked before any run starts.	Apply the rule from the project's Containers tab, under one administrator prompt, then press Resume.

Task cards and the task window

Message	What it means	Next step
The AI is working	The marker on a running card. The title turns amber and a timer counts the run.	Nothing. Open the card to watch the output.
Task may be stuck	A running card has produced nothing for 5 minutes.	Open the task. If the output shows a foreground command such as a dev server that never returns, stop the run. The run's own watchdog stops a silent run after 10 minutes on the hosted providers and 20 minutes on a self-hosted one.
Container not found - open task to see details	The project's container was not running when the run started. The task is Blocked.	Start the container from the board's container controls, then move the task back to To Do.
Waiting for your answer - open the task to reply. It cannot be moved to To Do until every question is answered.	The run paused with a question, or the pre-run review asked one.	Open the task and answer inline. Once every question is answered the task returns to To Do by itself.
Needs your attention - open the task to see what	The run finished with manual steps, or did not declare an outcome, or a review flagged the result.	Open the task and read the action comment. Moving the task to To Do or Planning clears the marker.
Waiting for [reason]	The run is waiting for something it started, such as a long build, and the app checks on it periodically. The task keeps its place.	Nothing. The task re-queues itself when the check succeeds, and reports a timeout if it never does.
This task is waiting on you - answer its question or clear the action first. You can still close it or move it to Blocked.	You tried to move a task with an unanswered question to To Do or In Progress. Doing so would start a fresh run that asks again and lose the answer being typed.	Answer the question. A drag attempt on such a card opens the task.
A task enters In Progress only when a run starts - run the task, or move it to To Do. It cannot be set to In Progress manually.	A board task cannot be dragged into In Progress. A user task can.	Move it to To Do and let the queue start it, or press Run.
Another task is already running. "[task]" is still running. One task runs at a time because they share the project container. This task has been moved to To Do and starts automatically when the container is free.	Run was pressed while the project already had a run in flight. The board queued the task instead of starting a second agent in the same container.	Press Got it. Nothing else to do. If the dialog says the task could not be queued, move it to To Do yourself.
Stop the AI run? In-progress work will be lost. The task moves back to Planning.	Confirmation before stopping a run, from the task window or by dragging a running card.	Stop run to stop it, otherwise Cancel. There is no resume of a stopped run.
Re-run this task? This task is done. Moving it to To Do puts it back in the queue - the AI will run it again.	Confirmation before dragging a done board task to To Do. Your own tasks are never run, so they move without asking.	Move & re-run to queue it, otherwise Cancel.
Unsaved changes. You have edited this task but have not saved it yet.	Closing the task window with an unsaved edit or an unsent comment.	Save and close, Keep editing or Discard. Escape and a click outside choose Keep editing.
[provider] stopped without declaring the task done. Its last output is above - check whether the work is actually finished before treating this as complete.	The run ended without stating an outcome, usually because the agent stopped intending to continue. There is no session resume, so nothing continued it. The task is in Done and marked Needs your attention.	Read the output. If the work is complete, clear the note. If it stopped part-way, move the task to To Do.
`Task was blocked — no reason provided. Review the [provider] output above, add any needed context as a comment, then retry.`	The run said Blocked and gave no comment.	Read the output, add a comment, then move the task to To Do.
Blocked after 6 failed process attempts. Last error: [error]. Review the task description, add any missing context as a comment, then move back to To Do to retry.	Every attempt failed. The delays between attempts were 1, 3, 5, 10 and 30 seconds.	Read the error, adjust the task, then move it to To Do. The whole project queue is paused until you press Resume.
Stopped retrying after [n] failed runs. [reason]	The app judged that another run would fail the same way.	Fix what the reason names, then move the task to To Do. The rest of the queue keeps running.
`The run made no progress for an extended period and was stopped. This usually means a long-running command was started in the foreground and never returned — e.g. a dev server or file watcher (npm run dev, vite, npm start).`	The stall watchdog killed a hung run. The partial output is kept. The project queue is not paused.	Change the approach, for example with a project instruction to run servers in the background with a timeout, then move the task to To Do.
The request could not be completed and won’t succeed on retry ([reason]). Fix the underlying issue, then move the task back to To Do.	A request error a retry cannot fix, for example a bad request, a forbidden resource or a model that does not exist.	Fix what the reason names, then move the task to To Do and press Resume on the queue.
The [provider] API key for this project has no remaining [credits or quota]. Add credit to the [provider] account ([where]), then move the task back to To Do to retry.	The provider account is empty. Each provider's version names its own billing page, and the Anthropic one also offers changing the provider or credential in the project's AI Auth tab.	Add credit at the provider, move the task to To Do, then press Resume.
[provider] could not be reached on 6 attempts, but the provider reports no incident - so the likely fault is this machine's or the container's own network. A network change (new wifi or a hotspot) while the container is running is a known cause. Restart the project's container, then move the task back to To Do and resume the queue.	Six unreachable attempts against a green status page.	Restart the container, move the task to To Do, press Resume.

Container start failures

A failed start, restart or rebuild is summarised into one sentence, shown inline where the button was pressed and as a notification titled Could not [start, restart or rebuild] the container for "[project]". The notification opens the project settings tab that holds the fix.

Message	What it means	Next step
Host port [port] is already in use, so the container could not start. Another project or another program on this machine is already listening on it. Change this project's published port, or stop whatever is holding it.	Another project or program holds the host port. A stopped sibling project publishes nothing, so the board also checks the ports it has handed out.	Open the Ports tab and change the host port, or stop the other program. The Ports tab suggests a free port.
Docker is not reachable, so the container could not start. Use the Start Docker button on the board, or start [the docker service or Docker Desktop], then try again.	The daemon was down at the moment of the start.	Press Start Docker on the banner, then start the container again.
A container named "[name]" already exists, so this project's container could not start. Remove or rename the existing one, or give this project a different container name.	A stale container holds the name, often from an earlier project with the same name.	Remove the old container, or change this project's container name in the Containers tab.
Docker Desktop refused to mount [path]: it is not shared from the host, which is what a folder that does not exist on this machine looks like (a Local path set on another device, for example). Point this project's Local path (Project Info tab) at a folder on this device, or share that folder under Docker Desktop's Settings, Resources, File Sharing.	macOS or Windows. The project's local path came from another device and does not exist here.	Open Project Info and set the Local path to a folder on this device, or leave it empty to keep the code inside the container. Set in code here only because of its colon.
The folder this project mounts does not exist: [path]. Check the project's local path, then start it again.	Linux. A bind-mounted folder is missing.	Fix the Local path in Project Info, or the mount in the Docker Compose tab.
A base image in this project's Dockerfile is not published for [architecture], which is what this container is being built for. Pick an image that has it, or set the container architecture (Containers tab) to one the image supports.	The pinned CPU architecture has no such base image.	Change the image in Dockerfiles, or the architecture in Containers.
The image on this machine was built for a different architecture than the one this container is now set to. Rebuild the container (Containers tab) so the image is built for the selected architecture.	The architecture setting changed after the image was built.	Press Rebuild in the container controls or the Containers tab.
A binary in this build is for a different CPU architecture than the container ("exec format error"). Set the container architecture (Containers tab) to the one the binary was built for, or install a build of it for this architecture.	A download in the Dockerfile fetched a binary for the wrong CPU.	Set the architecture in Containers. On a machine of the other kind it then runs under emulation, slower and without the gVisor sandbox.
The project image failed to build: [last error line]	The Dockerfile failed for a reason other than architecture.	Open Dockerfiles, fix the step named in the error, then start again.
The container failed to start, and Docker gave no reason.	Nothing in the transcript was recognised and Docker printed no error line.	Start it again from the Containers tab and read the log there.
The container is up, but cloning [url] into it failed: [reason]	Compose succeeded and the git clone after it did not. Common reasons are a key and URL that do not match, or a credential the device cannot decrypt.	Open Project Info and check the repository URL against the credential. An SSH key needs an SSH URL, a token needs an HTTPS URL.
This project's workspace folder is not on this machine: [path]. Point its Local path (Project Info tab) at a folder on this device - the board can create one for you - or leave it empty to keep the code inside the container.	The start was refused before Docker ran, because the synced local path does not exist here.	Open Project Info. The board offers to create a workspace folder for the project on this device.
The container is set to [architecture], but this [native architecture] machine cannot run that architecture: [why].	The start was refused before the build. The daemon reports no emulation for the pinned architecture.	Set the architecture back to Default in Containers, or install emulation. On a native Linux engine the notice includes the command that registers it until the next reboot.

The notification bell

Titles only, since the body is usually one of the sentences above. The full list of kinds, colours and where a click lands is on the States page.

Message	What it means	Next step
[provider] sign-in failed (HTTP 401)	A run's credential was rejected. The task is back in To Do and the project queue is held.	Click it to open the project's AI Auth tab and enter the key again.
[provider] sign-in failed - checked before the run	The free check before a run found the credential rejected. Nothing was spent.	Same. The queue resumes by itself once a key is accepted.
Task blocked: "[task]"	The run ended in Blocked.	Click it to open the task and read the Blocked comment.
Task done - manual steps required: "[task]"	The run finished and left steps for you, or a pull request to open.	Click it to open the task. Clear the note when done.
[provider] asked a question: "[task]"	The run paused with a question while nobody had the task open. The task is Blocked until answered.	Click it to open the task and answer.
Question waiting: "[task]"	A task with an unanswered question was closed, so it was moved to Blocked.	Same.
The review has questions about this task	The pre-run review, which runs after a task is saved, posted questions as comments. They hold the queue until answered.	Open the task and answer, or rewrite the task, which retires questions about the old wording.
The review suggests a clearer wording	The pre-run review proposed a rewrite. Nothing is applied by itself.	Open the task and apply the wording yourself if you agree.
Post-run review flagged something	A cheap model judged the run's diff against the task and found a gap. Never re-queues.	Open the task, read the verdict, decide whether to run again.
[provider] rate limit - project queue paused	A run hit a rate limit. The notice shows when runs resume, in your own clock format.	Wait, or press Resume in the To Do column.
Queue held - every To Do task overlaps blocked work	The blocked work hold above.	Unblock the named task.
Project queue paused - [provider] cost budget reached ([budget])	The cost budget hold above.	Reset spend in the provider's card on AI Auth.
Allow Docker access before the next task runs	The firewall hold above. Nothing was started.	Click it to open Containers and apply the rule.
Could not start the container for "[project]"	One of the container start failures above.	Click it. It opens the tab that holds the fix.
Container [started, restarted or rebuilt] for "[project]", but the repository was not cloned	The clone failure above.	Click it to open Project Info.
"[project]" runs under CPU emulation	The container is pinned to the other CPU architecture and runs emulated. Slower, and without the gVisor sandbox. Nothing is broken.	Nothing, or set the architecture back to Default in Containers.
"[project]": Dockerfile may need [x64 or arm64]	The Dockerfile pins a platform, adds i386 packages or downloads a binary for one architecture, and the container is being built for the other. The build may fail.	If it fails, set the architecture the notice names in Containers.
[project]: container tools added	A task installed tools and the board added them to the Dockerfile. They are in the running container now and disappear at the next recreate until it is restarted.	Click it. The prompt offers to start or restart the container so the change is permanent.
[project]: container settings changed on another device	Container settings synced in from another device. The running container keeps the old configuration until restarted.	Same.
[project]: container restarted unexpectedly	The container exited and Docker restarted it. Whatever it was running was lost.	Read the exit code. If it repeats, check the startup script.
[project]: container ran out of memory	The container exceeded its memory limit and was restarted.	Raise the limit in the project settings if this is normal for your build.
[project]: container keeps restarting	It failed on every check for the last few minutes. It will not recover by itself. No further notices until it settles.	Check the startup script, or the memory limit if the work is large.
Script "[name]" failed	A project script exited with a non-zero code or could not be run in the container.	Click it to open Scripts and read the output panel, which is the only copy of the log.
Saved git key not available on this device	The project links to a key in the vault that has not synced here or was deleted. Runs and terminals have no git credential.	Sign in and let the vault sync, or pick another saved key in Project Info.
Git credential unreadable	The stored git key cannot be decrypted with any key this device holds. The container's existing credential is left untouched.	Re-enter the key in Project Info.
[credential] removed from "[project]"	A change synced from another device removed a credential. The previous value is held on this machine for a while.	Click it. Restore the value, or delete it for good.
Flow "[flow]" failed, or could not run	A scheduled flow's run ended in an error, or was blocked, for example because the machine was asleep at the scheduled time. Missed windows are never caught up.	Click it to open the flow's page and its run log.
`Update available: v[version]`	A newer desktop version exists.	Click it. It opens the download page, or Settings, Application, or says the command to update with on a managed install.
`Update ready: v[version]. Downloaded. Restart Borago to apply.`	The update is downloaded.	Click it to restart into the new version. It waits if a run is in progress.
Cloud sync signed out	The 30-day cloud session expired while the desktop was off, or the password changed. Sync and the phone's relay stopped.	Open Settings, Account and sign in again.
`Cloud sync stopped: another desktop is now linked`	Another desktop took the account's single desktop link.	Sign in again from Settings, Account to link this one back.
Your stored credentials are not protected	The key that seals every stored credential is on disk in the clear. See the Settings section below.	Install or unlock a system keyring, or on macOS allow the app in the keychain.
Docker client installed	The Docker client that container management installs in the background has landed. Nothing to do.	Nothing.

Settings

Message	What it means	Next step
Your stored credentials are not protected. Borago Board was denied access to your keychain, so your stored credentials are saved unprotected. Anything with access to your files can read them.	macOS. The keychain prompt was answered Deny.	Allow the app in the macOS keychain, then restart it. A key written in the clear is re-sealed on the next launch that can reach the keychain.
Your stored credentials have only weak protection. No system keyring is available, so your stored credentials - AI provider keys, git keys and project secrets - are saved with weak protection. Anything with access to your files can read them.	Linux. No keyring is available, so the key has only weak protection.	Install and unlock a Secret Service keyring such as gnome-keyring or KWallet, then restart the app.
Your stored credentials are not protected. No system keyring is available, so your stored credentials - AI provider keys, git keys and project secrets - are saved unprotected. Anything with access to your files can read them.	Linux with no keyring. The key is on disk in the clear.	Same.
Your stored credentials are not protected. Your stored credentials are saved unprotected on this device. Anything with access to your files can read them.	No operating system protection was available and the cause is not one you can act on.	Nothing is blocked. Accept the risk, or move to a machine with a credential store.
The system keyring is locked, so Borago Board cannot read its encryption key this session. Unlock the keyring and try again.	Linux. The keyring that seals the app's key is locked this session, so no stored key or secret can be saved or read. Nothing stored is exposed or lost.	Unlock the keyring, for example by signing in to the desktop session again, then save once more.
Not connected yet - save to start syncing.	Cloud sync is on and has not made its first request.	Press Save.
Connected · last sync [time]	The last request the cloud answered succeeded. Counts of records sent and received follow.	Nothing.
`Error: Not authenticated — log in to cloud sync`	Cloud sync is on and no account is signed in on this device.	Sign in below the toggle.
Error: Your cloud session has expired - log in again (Settings > Cloud sync)	The session ran out or the password changed.	Sign in again.
`Error: Another desktop app is now linked to this account — sign in again here to link this one`	Another desktop took the link.	Sign in again here. The other desktop stops syncing.
Error: This account is deactivated - reactivate it from your cloud profile to resume syncing	The account was deactivated.	Reactivate it on the cloud profile page.
An active subscription is required to enable sync.	The account has no active plan, or its trial has ended. Sync needs a paid plan, after a free 30-day trial.	View profile. See Pricing.
Link this desktop app? Another desktop app is already linked to this account. Only one desktop app can be linked at a time. Continuing links this desktop and signs the other one out of cloud sync and remote terminals. Its local board keeps working - it just stops syncing until it is linked again.	You are signing in on a second desktop.	Log out other desktop & link this one, or Cancel.
The saved Docker path does not exist on this machine - it is being ignored and Docker is resolved automatically instead.	The Docker path in Settings, Docker names a file that is not there, usually a path synced from another machine.	Clear the field, or point it at this machine's Docker command.
Expose the board to your network? "This machine + LAN" serves the board to every device on your network. Anyone who can reach the port can open it, create tasks, and run the AI - with no login. Only enable this on a network you trust.	Confirmation before switching browser access from this machine only to the whole local network.	Enable LAN access on a network you trust, otherwise Cancel. For access from anywhere, use cloud sync instead.

The Docker setup guide

The guide is a checklist. Steps tick themselves as the board observes the Docker command appear and the daemon answer. The last row is the verdict, with a detail line under it.

Message	What it means	Next step
The board can install Docker with your administrator approval.	Linux, on a distribution the board can install on. One elevated script installs the distribution's own Docker packages, adds your user to the docker group, and installs the gVisor sandbox where the machine is eligible.	Press Install Docker. Expect one password prompt.
`The board downloads the official Docker Desktop installer and opens it; you finish the few clicks, and the checklist follows along.`	macOS or Windows. The installer is downloaded, verified against Docker's published checksum, then opened. On a Mac that is the image to drag Docker into Applications.	Press Download and open the installer and finish Docker's own steps.
This system is not one the board can install Docker on automatically - the steps below are the way.	An unsupported distribution.	Follow the commands shown, each with a copy button, and the link to Docker's guide.
Docker installed successfully	The verdict when Docker answers. On an eligible Linux machine it reads Docker and gVisor installed successfully.	Close the guide.
Borago Board has to be restarted before it can reach Docker.	The install worked and your user was added to the docker group, which a running program cannot pick up.	Press Restart Borago Board now. Where the machine cannot restart into the group, the guide offers Fix access, which grants this user access to Docker until the next login, or says to log out and back in.
Docker installed, without the gVisor sandbox	Docker works. The gVisor half of the script did not complete, so containers run on Docker's default runtime.	Run Set up gVisor sandboxing from Settings, Docker later. Docker still works without the sandbox.
Docker installed. gVisor is registered but did not pass its test	gVisor is registered with Docker and a sandboxed test container did not run, so project containers keep the default runtime.	The detail line gives the two commands that remove the registration.
`The system is installing its own updates first. Docker installs as soon as they finish, which on a new installation can take several minutes.`	The package manager is busy with unattended upgrades. The board waits for it.	Wait.
`The install did not complete: the administrator prompt was dismissed - press the button again to retry`	The password dialog was closed without a password. The board never asks twice on its own.	Press Try again.
`The install did not complete: the password was not accepted, or this account may not administer this machine`	The operating system refused the password after its own retries.	Check the account is an administrator, then Try again, or use the manual commands.
Docker installed, but the engine did not come up - it may need a log out and back in (the docker group change), or a reboot.	The packages installed and the daemon did not answer within the watch window.	Log out and back in, or reboot, then reopen the app.
Docker did not appear. If the installer is still open, finish it - the board keeps watching in the background.	macOS or Windows. The installer ran and no Docker command appeared within fifteen minutes.	Finish the installer. On Windows, if it asked you to restart or log out, do that.
Stopped. Try again, or use the manual steps below.	You pressed Cancel on a stoppable step.	Try again, or follow the manual steps.

Confirmation dialogs elsewhere

Message	What it means	Next step
Delete project. This moves [project] and its [n] tasks to the recycle bin for 30 days, and stops its container.	Deleting a project is reversible for 30 days. Typing the project name is required.	Type the name and press Delete project, or Cancel.
Project deleted. You can restore it from the recycle bin for 30 days.	Shown right after a delete.	Restore undoes it at once. Data & Recovery opens the recycle bin in Settings. Close keeps the deletion.
Restart container? This recreates [container] so compose changes take effect. It re-applies the Dockerfile too, so tools a task installed are built back in.	Restart recreates the container. It asks first only when the project's code lives only inside the container, because recreating it resets the working directory.	Commit and send uncommitted work to the remote, or copy it out, then Restart. A plain Stop then Start keeps the working directory.
Rebuild container? This rebuilds the Docker image from scratch, ignoring the build cache, and recreates [container]. It can take a while and briefly interrupts the running container.	Rebuild is for a stale cached layer, such as a moved base image or newer packages. Restart already re-applies the Dockerfile.	Rebuild only when a cached layer is stale. The same warning about work inside the container applies.
`This project's code lives only inside the container (no local path), and recreating it resets /app: uncommitted changes and unpushed commits are permanently lost - a clean tree is re-cloned on start. Push or copy out anything you need first.`	The warning shown inside the restart and rebuild dialogs, and after saving project settings that need a restart, when the project has a repository URL and no local path.	Commit and send your work to the remote, or copy the files out through the terminal, before confirming.
Restart the container? Your changes are saved, but the running container [container] is still using the old configuration. Restart it for the change to take effect - this also re-applies the Dockerfile, so any tools a task installed are rebuilt in. You can also do this later from the board's container controls.	Shown after saving project settings that change the compose file.	Restart now, or Later.
Quit Borago Board? Quitting stops the task queue and any tasks the AI is currently running. They will not resume until you reopen the app.	Quitting from the tray or the menu while runs are in progress.	Quit, or Cancel and wait for the runs to finish. Interrupted runs return to To Do on the next start.
Discard this task?	Closing the create form with text in it.	Discard, or keep writing.

Source as Markdown: /docs/reference/messages.md · Updated 2026-10-17 · Was this right? Tell us