Every bot can use every app you connect, also bots you make later. No more cards to give a bot an app.
To keep an app from a bot, turn it off in that bot's settings or on the Apps page.
Team chats ask you once
After the lead answers for the team, a bot it gives work to replies only with its result.
One question to you for each message, at the end of the lead's answer, instead of one from each bot.
A bot handed the work no longer repeats what the others already said.
The Chief of Staff and your Project Manager, side by side
The head beside a project's gear always opens the Chief of Staff.
Pick a bot as the Project Manager in the project's settings, under Team.
Its head sits beside the Chief's: write to it in its own chat, and it talks to all the project's teams.
Delete account on hosted machines
On a machine we host for you, Settings now has Delete account too, on the web page and in the Android app.
It opens botdot.app's account deletion page, which says how to have your account deleted.
Self-hosted machines are unchanged.
Cards go when plans change
Tell a bot you won't need something and it takes its card back from Needs you.
A bot waiting for a login hears your message right away instead of minutes later.
Bots know all your accounts of an app
With two Gmail accounts, a bot sees both by address and uses the one you ask about.
A card for sending names the account it sends from.
After you connect an expired account again, every bot that used it goes on using it.
A teammate's addition goes into the work
When a bot writes again to a teammate that is working on the same task, the message goes into that work: no second run starts and nothing is done twice.
A message on something else still gets a run of its own.
You see an addition in the chat inside that run, as a message from that bot, and the bot that wrote still gets the answer.
Sign in on a bot's screen when you're ready
When you have to sign in yourself on a bot's computer, the bot first asks if you want to take over its screen now, and opens the page only after your yes.
When you're done on its screen, press I'm done: the bot carries on by itself.
Setup questions that fit your project
A new project's questions are written for it, not picked from a fixed list.
Each question follows from your answers before it, and setup ends as soon as enough is known.
The Project Manager's chat says so
The chat that opens from the compass beside a project's gear is headed "Project Manager", not the Chief's name.
Your other chats with the Chief keep its name.
One Project Manager for every team of a project
The head beside a project's gear is now its Project Manager: tell it what you want, and it hands each team its part.
It writes in the teams' chats for you, and their answers come back to its chat by themselves.
You see its messages in each team's chat under its own name, and you can still write there yourself.
Pick who leads your project
In the project's settings, under Team, pick a bot as the project lead.
It runs the project's chat and talks to its teams in its own name and face.
A team's lead can be changed from the team chat's panel, on the phone too.
A file opens beside the project chat
On a wide window, a file you open from a chat on a project page takes the board's place.
The chat stays in its column, so you can read the file and keep talking.
Close the file to get the board back.
The Project Manager's messages name their team
Each message about a team shows the team's name in its colour above it.
Your answer that went to one team shows that team too.
In the Chief's chat the project's name stands before the team.
Tap the name to open the team's chat.
Delete your account from Settings
Settings has Delete account, on the web page and in the Android app.
It lists what goes and says that off-site backups are removed after 14 days.
Type your account's name to confirm; you are then signed out everywhere.
The admin's own account is not deleted this way: the machine is removed by its admin.
Bots ask you themselves in a team's chat
A bot that needs your answer asks you directly, in its own reply, instead of asking another bot to ask you.
The team's lead no longer repeats a question a bot has already asked you.
Tidy up a project's board
The new button beside a project's gear asks the Chief to arrange the whole board: tiles lined up, no gaps, each sized to what it shows.
The project's chat opens beside the board so you see the Chief at work.
Not what you wanted? Tap Put it back under the Chief's reply.
A backup download starts at once
After you enter the passphrase in Settings → Backups, the file starts downloading right away.
Your computer's files are added at the end of it, while it downloads.
Bots in a team ask bots outside it
In a team's or group's chat, a bot that doesn't know something now asks the bot that does, even one outside the team.
It waits for the answer and replies to you with it.
Above its reply, "Asked …" opens to the question and the answer.
Bots use an app instead of giving you steps
Before a bot or the Chief tells you what to click in a service like Brevo or Stripe, it checks whether botdot connects it.
When it does, you get one Connect card and the bot does the setup itself.
One card for many of the same app action
When a bot deletes, archives or sends several things in a connected app at once, you get one card that lists each of them.
Each item shows its name, date and id, so you see exactly what goes.
One Allow covers just those items. Anything else still asks on its own.
Group your passwords into categories
Give any entry in Passwords a category, like Shopping or Bank, when you add or edit it.
Passwords lists each category under its own heading: tap a heading to fold it away.
Search finds categories too, and the Chief can sort entries into categories when you ask in chat.
Add and remove a team's bots in its settings
"Add a bot" under a team's members picks bots to join it, or asks the Chief for a new one.
✕ beside a member takes it out of the team. Its own chat and its other teams stay.
A team always keeps at least one bot.
Switch Claude without waiting for the old limit
Choosing an API key or returning to the subscription releases the pause left by the previous choice.
Your waiting messages and bots carry on automatically.
Open Setup from its address
Typing #setup into an open botdot tab now opens Setup without reloading the page.
In Setup you can switch the Claude account connected to botdot.
An open chat stays where you read
Opening the chat you are already in, from its key or a notification, no longer jumps up to an old "New" line.
The chat stays at its end while you wait for an answer, also in a team's chat beside a project.
Faster setup for hosted botdot
Hosted botdot opens while the bots' computer prepares in the background.
Dedicated demos can be opened repeatedly with their demo access code and start with fictional project data.
Hosted setup uses less temporary space
Hosted setup transfers the server image directly into the account, avoiding a large temporary archive that could stop installation.
If the transfer fails, setup reports the export or import error.
The Chief is one tap away in every project
A small Chief head beside the project's gear opens the Chief's chat about that project.
A number on it shows what waits for you there: new replies and cards to answer.
The same chat the Chief already uses for that project's plans and reports.
The Chief looks out for you
When you work late two nights running, your day has no gap for lunch, tomorrow starts early or too much has piled up, the Chief may say so once and offer one thing it can do about it.
At most once a day and twice a week, inside its usual messages.
Tap "Don't mention this" to stop one kind, or tell the Chief "don't worry about me" to stop them all.
New project starts on the first tap
In the Android app, the arrow on the New project screen opens the new project at once.
Before, the screen stayed as it was, and a second tap made the same project twice.
Answered once, gone everywhere
When you answer a bot in one chat, its question and answer buttons go from its other chats.
That holds for its own chat, its groups and its teams' chats, also after a reload.
A file on the board opens
On the phone, tapping a file in a project's Files tile opens that file, over its folder in Files.
A tap on the tile itself still opens the project's folder.
Answers show their question
In a group, an answer you tap under a bot's question shows that question above it, with the head of the bot that asked.
Tap it to go to the question.
The bots are told whose question your message answers.
Links show their site
A web address in a chat shows as its site, like x.com, with the site's icon, and opens the full address.
Bots write a link as a few words that say what it is.
Apps without your own key
The admin sets one Composio key on /admin, or botdot sets it for a hosted server, and every account connects Gmail and other apps without a key of its own.
A key you pasted yourself stays yours.
A simpler Setup
Without Advanced, Setup shows your phone as a QR code to scan, without Tailscale, Docker or extras.
Resetting the bots' computer says what goes in plain words, with no folder paths.
Storage names its rows plainly: Run history, Its files, Temporary files.
A team's row says who needs you
A folded team says who waits: a bot by name, or the team chat.
A bot in two teams lights only one of them.
Teams on a project's page are folded
Each team is one row: its bots' faces, its name and whether it needs you or is working.
Tap the row to open the team's chat. The arrow before it shows the team's bots.
A bot's own chat is still one tap away after you unfold its team.
Plain words
The Vault is now Passwords, and Connectors are Apps. Without Advanced, adding a password asks for a website, a username and the password, and nothing more.
Errors say what to do, not a status number. The chat says "Checking a website" or "Working on its computer".
The card for a quick check without AI says in one line what it can do.
A button to the newest message
When you read back up in a chat and a new message arrives below, a round arrow with its writer's head shows above the message box.
Tap it to go to the newest message. It goes away once you are there.
In the Chief's chat, a bot's chat, a team's chat and a room, on the web page and in the Android app.
Your goals follow the team's reports
When a team lead reports a number reached or a step done, the goal card on the board moves with it.
The Chief's chat of the project says what moved, with the number before, so you can set one back.
A dated task starts its bot on its day
A task you give a bot in a project for Friday, or every Monday, now starts that bot on that day, in the morning.
Tasks the Chief or the bots add still wait for the bot's turn.
Add a login later, the bot carries on
A login a bot asked for now waits in Needs you for a week, also after the bot stopped waiting.
Add it when you can: the bot picks up what it was doing.
The Chief tries a failed job again
When a job you approved fails, the Chief runs it again once by itself and tells you it did.
You can stop that run in the bot's chat; if it fails again, it is yours to decide.
Your bots say when they keep watch
A bot with a job that will run says "Watching, last 07:12" on its key instead of "Idle".
An unseen result, a run that did not finish and anything that needs you still show first.
Fewer technical words
Settings ends with an Advanced switch. Off, the screens leave out models, exact tools, schedules as code, scripts and tokens.
Your bots work as before: the Chief still changes all of it when you ask.
A new account starts with Advanced off; yours keeps what it showed.
A new bot gets going at once
When the Chief makes a bot, it adds its job and starts its first run straight away, and tells you what that run found.
If the bot needs a login or your OK first, the Chief starts it as soon as that is in place.
Every bot can do more on its own
Every bot can browse the web, change its files and use the computer with its browser, with no switch to turn on.
Bots ask each other without asking you; the setting for it is gone.
A bot uses a saved login once you let it on its request: the Vault no longer warns that no bot has it.
Token usage moved under Advanced in Settings.
Fewer rings for cards
A card that holds no bot's work up no longer rings your phone: it waits in Needs you, and the Chief names it in your morning brief.
A card a bot waits on now still rings at once.
Fewer cards from your bots
A note a bot removes is removed at once; ask the bot to bring it back within 30 days. Forgetting still asks you.
A bot gets helpers, its own AI job and a new secret in the Vault without a card.
In a shared room your bot reads its own files without asking; everything else, and its post, still waits for you.
When you ask a bot to change its task or rules, it does it at once; you can undo it in its settings.
The Chief notices, and picks the moment
A meeting in a project within the hour, a card waiting since yesterday or an overdue to-do no longer waits for the next fixed time: the Chief writes when it matters.
Every day starts with a brief and ends with a short close of the day.
Up to 8 messages a day; tell the Chief "less" or "more".
Nothing comes while you are writing, nor in quiet hours.
The Chief follows through
When the Chief says it will check something later, it does, and tells you what it found.
New mail that matters and a meeting within the hour reach you between the Chief's looks, when Gmail or Google Calendar is connected; what can't wait rings at high priority.
Kinds of messages you never react to stop coming by themselves.
Your bots' reports share the day's limit with the Chief: past it they still arrive, without a notification.
One answer from a team
In a project's team chat, when several bots answer, the team's lead now writes one joint answer at the end.
The bots' own replies fold under that answer; tap the row with their names to see them.
Bots in a team settle technical, reversible, free choices themselves and ask you only for money, access, steps that can't be undone or matters of taste.
One yes for all your bots
"Always allow" on an app's action can now be for all bots, when the action sends nothing to anyone, removes nothing and pays nothing.
The Connectors page lists what all bots may do, each with Revoke.
One bot in several teams
Add a bot to another team of a project and it stays in its first team too.
It can lead one team and help another; each team keeps its own lead.
The bot knows every team it is on, and in a team's chat it works for that team.
Fewer cards from the Chief
A bot the Chief makes for you gets everything it needs at once: the web, commands, a computer, its apps.
What you ask the Chief to change in a bot, or a tool you ask it to install, is done at once too.
After the Chief reads the web or an app, a change still waits for your OK, now on one card instead of two.
botdot on your computer updates itself
At 04:00 at night, when a newer version is out, botdot on your computer updates by itself.
Your bots carry on after it, and nothing waits for you.
Bad news comes with a fix
When a bot's job fails or doesn't run, the Chief finds out why and tells you with one step to fix it, ready for your yes.
A job running much longer than usual: the Chief says how late it is, why, and what happens next.
When something takes a while, the Chief says by when you'll hear back, and keeps to it.
An update keeps Bitwarden unlocked
After an update you no longer type your master password again: bots that need a login keep working.
A restart or a reboot without an update still locks it, as before.
A yes days later still does the work
Work that stopped on a card now waits a week for your answer, not a day.
Writing to the bot in the meantime no longer drops it: the bot carries on and is told what you wrote since, so it doesn't do twice what you already sorted.
A job tries again by itself
When Claude's servers are busy or a run didn't start, a job quietly tries again 5, 10 and 15 minutes later.
You hear of it only if the last try fails too.
The Chief watches your projects
When the Chief writes first, it now knows what is due in your projects: an overdue or today's to-do, today's event, a check-in or a plan that waits for you.
Your morning brief lists them under what needs your decision.
Fewer switches in the Vault
"Accept a self-signed certificate" and "Usable in its computer" are gone: both are on for every saved secret.
Bots no longer stop to ask you to turn them on.
A second account of the same app
Connect another Gmail (or any app) next to the one you have: Add account on Connectors, or ask the Chief.
Each bot uses one account, and adding an account moves no bot.
Connectors shows each account by its address, with the bots that use it.
A calmer home on the phone
Needs you comes first, above the Board's numbers.
The Board's numbers stand three to a row, so your bots show without scrolling.
What a working bot does reads on two lines, and bots fade out above the Chief instead of being cut.
Pick your bot's icon
In a bot's settings, tap its icon at the top and pick another from the 80 icons.
The icons are shown in the bot's colour, so you see how it will look.
The Chief can still change it when you ask.
Bots write in your language
Reports of scheduled jobs, skills and memory reviews come in the language of your screen, not in English.
The Chief's daily messages, checkups and project standups do the same.
A bot told to write in another language, or a message you write in one, still wins.
Bots can browse through a proxy
Add your HTTP or SOCKS5 proxies in Settings → Proxy, paste an address to fill the fields, and test where each one comes out.
Pick the proxy all bots use, or another one for a single bot in its settings.
The bot's browser never goes out directly: if the proxy is down, it stays closed and the bot tells you.
The desktop app for Linux
botdot now has a desktop app for Linux, as an AppImage, a .deb and an .rpm, for x64 and ARM.
It shows your botdot in a window of its own, with a tray icon, notifications and Open at login, and updates itself.
With no server, it can run botdot on the Linux computer itself, after your password.
Bots have a new look
Each bot is now a square in its colour with an icon that shows what it does, in place of the head with a hat.
A working bot has a turning ring around it; one that needs you or failed has a dot on its corner.
There are 80 icons to choose from, from invoices and data to travel and pets. Your bots get their icons by themselves within a few minutes. To change one, ask the Chief.
A bot's square moves once, quietly, when its state changes: a check when a run ends well, a single pulse when it needs you.
botdot installs on more Linux distributions
The installer now sets up Debian 12 and 13, Ubuntu 22.04 and newer, Fedora, RHEL and its rebuilds such as Rocky Linux and AlmaLinux.
On Fedora and the RHEL family it installs Docker and gVisor with dnf.
A machine botdot can't run on is told why before anything is installed.
A steadier, quicker browser for your bots
A bot's browser opens as soon as it is ready and the bot reads the page at once, instead of waiting a fixed time.
A browser that stopped is started again by itself, and a bot no longer repeats a click that already worked.
Bots type saved logins at a person's uneven pace and move the mouse faster, so sites flag them less.
Needs you comes first, and nothing is cut in half
On Home, what waits for your OK sits above the Board's numbers.
A long Board value ends at a whole word, and a key's status reads in full on two lines.
On a phone, buttons are easier to tap, and keys line up in three even columns.
A failed run shows a red line beside it, and the New line spans the whole chat.
Connect an app from its card, and the work goes on
When a bot or the Chief needs an app that isn't connected, you get one card: Connect Gmail for Writer.
Press Connect, sign in, and the bot has the app and carries on with the work that waited for it.
Not now puts the card away for a day.
A calmer project page
Your teams and their bots come first, right under what waits for you.
Objectives are small cards with a short trend line.
The board has no frame or grid paper, and the add buttons are quiet.
Bot heads in a project's Team step are full size again.
The Android app looks like the web page
Messages at the bottom, dialogs, sheets and menus are botdot's black and greys, no longer purple.
A message that something failed is red.
The chat's top bar and the project screens have no frames around their buttons and boxes.
Text uses two weights, regular and semibold, as on the web page.
Tiles can ask before they switch
Ask a bot to make a switch ask "are you sure" before it turns off, and it changes its tile in place.
Bots now change their own tiles when you ask, instead of saying it is already on the Board.
Your chats are conversations on Android
Each bot's chat, each group and the Chief now show in Android's Conversations section of the notification shade.
Long-press a chat's notification to make it a priority or to silence it, in the phone's own settings.
Long-press the botdot icon to jump straight to the Chief or a pinned bot.
A bot remembers its work after your OK
When a bot stops to ask for your OK, it now carries on where it stopped, with everything it had already read.
It no longer looks the same things up again before it gives you the result.
A quick correction reaches the Chief while it works
"Make it 9, not 8" or "also add Slack" sent while the Chief replies goes into that reply, as if you pressed Steer.
"How far are you?" is answered at once beside the reply.
Anything else waits its turn, as before.
A working bot says what it waits for
While Claude's servers are busy and the bot tries again, its line reads "Waiting for Claude's servers".
A bot that asked you for a login or a card shows "Waiting for your OK", as for an action that needs your OK.
Ask the Chief what a bot is waiting on: it sees which teammates it asked and since when.
Claude's usage limit no longer fails everything
When Claude's usage limit is reached, botdot holds the bots' work until it resets, instead of failing one message after another.
One line says when the bots carry on, and the work that waited starts by itself then.
The run that hit the limit carries on by itself after the reset.
Change direction names the project
At a check-in or a monthly review, Change direction now starts the Chief's chat with the project's name, so the Chief knows which project you mean.
It works the same on the web page and in the Android app.
A standup that breaks says so
When a team lead's standup fails, botdot asks once more before leaving that team out.
The Chief's standup message names a team that is missing, and when no lead answered at all, the project's Chief chat says there is no standup today.
The team reads your project's sources
Every bot of a project's teams now knows the files and links you added to the project, by name.
A bot reads a file you added, like a brief or a spec, whenever its work needs it, and opens a link on the web.
The morning standup counts the team chat
A lead's standup now includes what its team did in the project's team chat, not only in each bot's own chat.
To-dos the team ticked since the last standup count as done.
A project's "Never without asking" reaches its whole team
Every bot of every team in a project now reads the project's Never without asking list on each run, as you last changed it.
Bots added later, copied bots and bots from the Chief's suggestion follow it too, and a rule you remove is lifted for all of them.
Vault, Connectors and Activity read like Settings
The Vault is one list: Bitwarden is a row that opens its form, and each saved item is a row that opens it.
Connectors without a key is one list too: the key field and a link to get one.
Activity marks only runs that failed or are running, and on a phone the whole list shows.
Switches are one size everywhere.
Bots' browsers look more like a person's
Each bot's browser keeps the same identity from one start to the next, as a person's does.
Its time zone and place match the computer's address, and sites show in your language.
Bots type into forms key by key, pick from drop-down lists, and find text further down a page in one step.
No notification lost after a night offline
When the Android app connects again after hours away, every reply and card it missed still rings, also when many came at once.
A slow moment in the app no longer makes it skip events: chats and dots catch up on their own.
A connection that died quietly is noticed and opened again
After a laptop sleeps, the Wi-Fi changes or the phone wakes up, botdot notices within a minute that its connection went silent and connects again.
Replies, working lines and notifications no longer freeze while the app still looks connected.
Screen readers hear replies, the working line and messages
On the web page a screen reader reads a new reply in the open chat, and what a working bot or the Chief says it is doing when that changes.
Messages at the bottom of the page are read out too, an error at once.
Start typing to write in the open chat
On the web page, typing a letter with nothing selected puts it in the open chat's message box, so there is no need to click into the box first.
The digits still open bots and groups.
A Chief chat that can't open keeps your box on the chat you see
When a previous Chief chat can't be read, the message box keeps writing to the chat on screen, not to the one that didn't open.
The address in the browser stays on that chat too.
A file that failed to upload stays in the box
When a file's upload fails and you send the message anyway, the failed file stays in the box, so you see it did not go.
On Android, picking files from a cloud app no longer stutters.
The Chief's chat stays where you read
When you scroll back up in a Chief chat, a finished reply, a bot's report or a /btw answer no longer pulls you to the bottom.
At the bottom it still follows the newest message.
Esc in a dialog only closes the dialog
Esc on a question such as the password warning, or on a picture, closes it and leaves you in the chat you were in.
On the web page the keypad's Esc opens the Chief only when no dialog is open.
A failed Approve or Decline says why on its card
When an answer on a card in Needs you can't go through, the reason stays on that card until you tap it again, instead of a message that disappears.
Screen readers read it out.
Stop says when it did not work
Stop on a bot's run or the Chief's reply says it is stopping, or why it could not, on the web page and in the Android app.
On the web page Stop is easier to hit.
A reply from a notification that did not go is kept
When a reply you typed in a notification can't be sent, it waits in that chat's box with the reason, ready to send again.
Sent again, it starts its task once, even if the first try reached botdot.
What you typed waits for its chat
Text you typed and did not send stays in that bot's or group's box when you open another chat, and is there when you come back.
On a phone it is still there after Back too.
Taps on the list and keys land while bots work
The list, the keys and a phone's home stay as they are while a working bot's line changes elsewhere, so a tap or a key you focused is never lost.
The bots' heads keep moving smoothly instead of starting over every second.
A working bot's chat stays still
Each step a bot takes adds a line to its open steps and leaves the rest of the chat as it is: text you selected and a reply you opened stay.
The reply as it is written keeps growing after a dropped connection, a phone changing networks or a laptop waking up.
Camoufox is now Firefox 158
The bots' browser moves from Firefox 152 to 158, with the newest Camoufox.
Its disguise is more consistent: screen, graphics, fonts and voices agree with each other, so fewer sites tell it is a bot.
A chat keeps its place when something opens
Opening a run's steps, a folded message or a card at the end of a chat keeps the newest message in view: what opens grows upwards, and the line you clicked stays in sight.
Higher up in a chat, the line you opened stays where it was.
A plan above the message box, or a longer message being typed, no longer hides the newest message.
Upload from phone
The paperclip in a chat now offers From phone: scan the QR code and send photos or files from your phone.
They land in the message box, ready to send. Files has From phone too, into the folder you're in.
The code works for ten minutes, for that one place.
Add a bot to a team from the project page
A + at the end of each team's row opens your other bots: tick them and press Add.
A bot that is in another team of the project says so, and moves when you add it.
New bot asks the Chief of Staff for one in that team.
Files on a project's board
A project's board has a Files tile with the newest files of its folder.
Click a file to open it, or the tile to open the whole folder.
Don't want it? Take it off in the project's settings, like Calendar.
Feedback on hosted machines
On a hosted machine, Feedback is now beside Settings.
Your bug reports and feature requests, with their screenshots, go straight to the people who run your machine.
The admin chooses the External Virtual PC's size
The size of your account's External Virtual PC is now set by the admin, on the admin page, as where your computer is.
Settings → Computer shows where it is and its size.
The size you chose before stays.
Backups go off-site, and you download one when you want it
Settings → Backups shows when your account was last backed up off-site, together with the machine, every night.
Download makes a backup of your account now, encrypted with a passphrase you choose for it, and nothing of it stays on the server.
The nightly backups your account kept on the server are removed once it is backed up off-site, which frees their room.
Restore a downloaded backup as before, from Restore a backup on the setup page, on this server or another.
Bots stop asking you to install a browser for video
A bot that renders video uses the headless Chrome on its computer, and no longer asks you to install Firefox or Chromium first.
On a computer that predates it, the bot uses the Chromium already there.
The Chief of Staff no longer asks you for a link to Chromium or Chrome when a bot wants one: it tells the bot which browser to use.
Rename a project's team from its chat
Open a team's chat panel and edit its name at the top, as with any group.
The team in the project takes the new name too.
See what takes space in Settings → Storage
Settings → Storage shows how much your account's files take, as a bar and a row for each group: your computer, bots' files, projects, uploads, chats and memory, caches.
Open a group or a folder to see what is big in it, largest first, down to single files.
Open a folder or file in Files, ask the Chief about it, or delete it after a question on its row; clear the caches in one go.
The Chief can tell you what takes space too.
A team's plan shows in its chat
When a bot in a team or group chat makes a plan, it stands above the message box, as it does in the bot's own chat.
It follows the member at work, step by step, and folds into its reply when the turn ends.
Tables read cleanly
A table in a chat keeps each word whole and sizes its columns to what they hold.
A wide table scrolls sideways in its own box instead of squeezing its columns.
Columns of numbers line up on the right.
The Chief tells you when a backup stops working
When your backups are on and none has finished for two days, the Chief says so once, with the error.
On a machine with an admin page, the admin hears once when the off-site backup is late, and once when it works again.
Neither message comes at night: it waits until your quiet hours end.
Backups hold your computer's files and restore at any size
A backup now carries the files on your bots' computer: what they made in their folders and project folders there.
After a restore those files go back onto the computer as soon as it runs.
A backup larger than 256 MB restores from Setup: only the free space on the disk limits it.
The page asks for a passphrase of at least 12 characters, the length botdot takes.
Deleting asks first, in the Mac app too
Delete bot, and every other step that asks "Are you sure?", now asks in the page itself, so the question shows in the Mac app as well.
While a bot is being deleted, its button says "Deleting…" until it is gone.
Rename, a new folder and a new project ask for their name in the page too.
A chat stays at its newest message
Coming back to the window, or tapping a suggested answer, no longer takes the chat up to older messages.
New messages keep scrolling into view at the bottom.
Bots save secrets in the Vault, with your OK
A bot that made a password or an app secret, say on a server it set up, can now keep it in the Vault.
It asks on a card: the entry's name, its address and where the secret comes from. Nothing is saved until you tap Save.
Show on the card lets you see the secret first. It never appears in the bot's chat.
Show and Hide also sit beside every secret you type in the Vault.
An External Virtual PC's screen in Safari and the Mac app
Its screen now shows in Safari and in the Mac app, where it stayed on "Connecting to desktop stream...".
There it opens in botdot's own screen viewer, as the account's computer does: you watch until Take control.
Chrome, Edge, Brave, the Windows app and Android keep the smoother stream.
A project's page stays where you were
A button on a project's page, such as a To-do filter, no longer takes the page back to the top.
The same while you set a project up; a new screen still opens at its top.
A bot says a card waits in Needs you only when one does
Each bot reads what of it really waits in Needs you as it starts, so it no longer points you to a card you already answered.
A bot that asked the Chief for a missing command no longer says a card waits for you before the Chief asks.
A project's board is readable on a phone
On a phone the board's tiles stand one under another, full width, with text at its normal size.
They keep the order you gave them on a wider screen; you move and resize them there.
Bots render video without downloading a browser first
The bots' computer now comes with the headless Chrome that video tools such as Hyperframes use, so a render starts at once.
An existing computer gets it once it is updated to the new image.
The Team step shows the Chief at work
While the Chief puts your project's team together, the Team step says so, with the Chief at full size instead of a tiny head on an empty page.
If it takes longer than usual, it says it is almost there; if it fails, it says why, with Try again.
A team's cards stand under its lead
In a project, a team member's card in Needs you and the To-do shows the lead's face.
The card still names the bot that asks, and you still answer it with one tap.
A team's lead asks you for its team
In a project, a bot that needs a decision, an answer, a file or a login from you asks its team's lead, and the lead asks you in one message.
The lead passes your answer back to the bot.
An approval card is still the bot's own, and you still tap it yourself.
Setup knows your phone can reach botdot
On a botdot with its own domain, the Your phone step shows the address to open on your phone, instead of asking for Tailscale.
On your phone, choose Add to Home Screen there to use it like an app.
Tap an OK request to see what it is about
On Home and on a project's page, tapping the words of a request with No and Allow opens the bot's chat at its card, with the reason and what it runs again.
No and Allow answer it right there, as before.
A rule you give a bot reaches its work already going
Tell a bot "always write in English" while it works on something else, and that work follows it from its next step.
A bot that answers you while it carries on after your OK knows that work goes on, and no longer says it still waits for the card.
Remove a goal from its menu
A goal at the top of a project's board opens a ⋯ menu, like the cards under it; Show as is there too.
Remove in that menu takes the goal off the board at once.
A project shows only its own team's asks
A project's To-do lists what its team's bots ask you, and what was asked in its team chats, the Chief's asks there included.
What other bots ask, and the Chief's own chat, wait on Home only.
Files in a project open from the chat
A file a project's bot names in its reply, like install-docs/QUICK-INSTALL.md, now opens from the project's folder instead of saying it doesn't exist.
A file that really isn't there says "File not found".
Project work stays in its own chat
The Chief's weekly plan, standup and other work for a project now happen in a chat named after that project, not in whichever chat you used last.
Approval cards no longer end with a line saying where the Chief carries on.
Your messages stay in a bot's chat
A bot's chat on the web page no longer loses your messages and its replies when your other bots have been busy.
A message that waited its turn stays in the chat as it starts, until its run is there.
botdot on an iPhone
With the keyboard open, a chat keeps its header and its field on screen.
From the Home Screen, a document or a botdot page you open shows over the chat, still signed in; Close brings the chat back.
A download from the Home Screen opens the share sheet: Save to Files, AirDrop or another app.
The admin moves your computer
Where your account's computer is, this machine or the External Virtual PC, is now the admin's choice, on the admin page.
Settings shows where it is; the External Virtual PC's size is still yours.
A project's bots know its whole board
A bot in a project's team now sees the project's goals at the top of the board, not only the cards below them.
Ask it to remove a card or a goal in its chat and it does; if your words fit more than one, it asks which.
The Chief of Staff can remove them too when you ask.
Home shows every bot
Home always shows all your bots and chats, those in your projects' teams too.
The All or No project choice over the keys is gone.
Cards that fill their space
A card on an arranged board shows as many of its items as its size holds: make it taller and you see more.
A list card now keeps up to 15 items and a table up to 12 rows, the most important first, from its next refresh.
Projects for things that never end
A new project starts from "What shall we take on?": a goal, an ongoing matter like your home or your car, or a site.
Something ongoing has no 90 days: no delivery date, no day counter, and a short monthly review instead of the check-ins on days 30, 60 and 90.
Its goal is what should keep working, and its bots handle the recurring upkeep in their routines.
PDFs open beside the chat
A PDF a bot sends, or one you attach, opens in the viewer with all its pages, also a large scan.
On the phone, pinch with two fingers to zoom in.
Download stays where it was.
A mail draft shows its attachments
The card of a mail draft lists the files the mail carries.
Tap one to open it, as in the chat.
A device you stop using is signed out
A device that hasn't opened botdot for 90 days is signed out. One you use keeps going.
Signed out, it opens the sign-in page: your passkey signs you in again.
The admin can sign an account out everywhere, on every device at once.
How many more accounts fit
Sign-ups on the admin page says how many more accounts this machine has room for, from the RAM and disk it has free.
Set a maximum of accounts there, or leave it empty for none.
On a full machine a sign-up link makes no account: it says the machine is full and works again once there is room. Your own install link always works.
Block addresses and limit new accounts
One address makes at most 3 new accounts a day. Change the number under Sign-ups on the admin page.
Block an address or a range, IPv4 or IPv6, for a day, a week, a month or until you remove it.
A block stops either new accounts from there, or all access from there. Your own session is never cut off.
Every block, its removal, a new limit and each refusal are in the Audit log.
An audit log on the admin page
Audit log in the rail lists what was done on this machine, newest first: who, what, which account and when.
It keeps every action on the admin page, accounts made, passkeys added and sign-ins slowed down after failed tries.
Pick an account or an action to filter, and Older for what came before. Entries are kept for 13 months.
A bot you have read says Idle
A bot's key says Done after it finishes, until you open its chat.
Once you have seen the result, it says Idle, in every app.
Needs you and Couldn't finish stay until you act on them.
botdot on your Windows PC
The desktop app for Windows can run botdot on the PC itself: Run botdot on this PC, then make your passkey in the browser.
It sets up WSL if the PC hasn't got it, with one administrator prompt and a restart, and carries on after it.
botdot runs in a Linux of its own that can't reach your files or your network, and keeps running while you're signed in to Windows.
Update or remove it from the app's tray menu.
Closing a card is instant
X on a card's questions takes it off the board at once, without waiting for botdot.
Remove does the same, and a card botdot can't remove comes back with the reason.
The admin page in groups, with the accounts as a table
The rail has five groups: Accounts, Usage, Sign-ups, Feedback and Settings. The machine, Update, Shared rooms, Decision model, Replays and boat.dev are under Settings.
Accounts are a table: type part of a name to find one, click a column to sort, and pick a state to filter.
Click a row for its share, its update and every action: Change share, Update now, Suspend or Resume, New sign-in link and Delete.
Disk full, Near its RAM and long commands stay marked in the row.
A team's name opens its panel
Tap a team's name at the top of its chat to see its members and its notes, as in any group.
In the Android app this works in the chat over a project's page too, for a bot as well.
Every bot on Home again
Home shows the bots and chats of your projects' teams too.
All or No project over the keys: No project leaves only the bots in no team.
Each device remembers your choice.
The External Virtual PC keeps saving
The browser on the External Virtual PC can no longer block boat.dev from saving it, also after a restart.
You get a notification when boat.dev can't save it.
Work cut off by an update carries on
When botdot is updated or restarted while a bot works, the bot carries on with that request by itself once botdot is back.
The Chief of Staff carries on with a reply that was cut off, too, and so does a bot's turn in a group.
It goes on from where it was, without doing again what it already did.
After botdot was off for more than an hour, nothing starts by itself: ask again if you still want it.
Notifications ring as soon as you leave
A card that waits for you rings as soon as you leave botdot's page or window, not a minute later.
When notifications are off for the desktop app, its menu offers Turn on notifications.
botdot on your Mac
The desktop app can now run botdot on the Mac itself: choose "Run botdot on this Mac" when it starts.
It needs no Docker Desktop or Homebrew, and starts by itself when you log in.
Bots there can't reach your Mac or your home network.
The app's menu updates it and removes it.
Groups keep notes of what was settled
A group, a team's chat too, keeps short notes: decisions, what someone still owes, and facts.
Every bot in the group reads them in each turn, so nothing settled is lost when the chat moves on.
botdot adds them as the chat goes on, and the bots can add and remove them too.
See and change them in the group's settings. A note you wrote or changed stays as you wrote it.
The desktop app holds several botdots and stays in the tray
Add another botdot from the app's menu and switch between them without signing in again.
Closing the window keeps the app in the tray on Windows and in the menu bar on the Mac. Quit ends it.
The app opens when you log in to your computer. Turn this off with Open at login in its menu.
The desktop app notifies you
A bot's reply, a card that waits for you and a message in a shared room show as a notification on your Mac or PC.
A click brings botdot forward on that chat or on Needs you.
Nothing rings while botdot's window is in front, and reading a chat clears its notifications.
Download the desktop app, and it keeps itself up to date
The botdot app for Windows (also on ARM) and Mac (Apple silicon and Intel) is a download on GitHub, linked from the README.
The app looks for a new version when it starts and once a day, and asks once before it restarts into it.
Replies on the web page show as they are written
A reply being written shows everything that has come so far, with no slow letter-by-letter catch-up.
Bold text, code and links still show no marks before they are finished.
App names show in a bot's settings
Every app in a bot's Apps list shows its name next to its checkbox again.
Skills and the bots it may message sit in one row each, across the whole width.
Android shows replies as they come
A reply being written appears as soon as it arrives, no longer trailing behind letter by letter.
Bold, code and links still appear once their marks close, never as stray asterisks.
Android opens chats again
The app no longer stops when a group chat, or any chat with replies, opens.
Replies that grow letter by letter work as before.
A project's folder takes its new name
Rename a project and its folder on the account's computer is renamed too.
While a bot of the project is working, the folder waits and is renamed once the bot is done.
A folder named by an earlier name catches up after this update.
Replies on Android grow letter by letter
A reply being written appears letter by letter at a steady pace, not in jumps of several words.
Bold, code and links appear once their marks close, never as stray asterisks.
A long reply grows without slowing the chat, in bot, Chief of Staff and group chats.
With Remove animations on, a reply is shown as it comes.
Start from scratch asks the name first
Start from scratch asks what to call the project before it makes it.
The project's folder is named after it, not "New project (2)".
Back returns to the start screen, on the web page and in the Android app.
A new project starts with where you want to go
The start screen of a new project says "You know where. We'll work out how."
Its field asks for a goal, a site or an idea, on the web page and in the Android app.
A bot's browser opens again after it fails
When a bot's browser crashes or closes, the bot can open it again right away.
A slow page no longer closes the browser while it opens.
One + for a new bot or a new project
The Bots and Projects switch is gone also before your first project.
The + in the rail asks: New bot or New project. New bot opens a new chat with the Chief of Staff, ready to describe it.
On a phone the logo's arrow opens Home, New bot and New project, on the web page and in the Android app.
One bot at a time on a shared screen
On the External Virtual PC two bots no longer click and type over each other: the screen and browser are one run's at a time.
Another bot waits a moment, then hears who is using them and works on with its shell and files.
The screen is free again when the run ends, or after 2 minutes unused.
Start from scratch, right under the field
On a new project, Start from scratch now sits right under the field for the site or idea, not at the foot of the page.
It still makes an empty project at once, on the web page and in the Android app.
Stop works on the External Virtual PC too
Stop now ends what a bot runs on its External Virtual PC, also what it left in the background.
A command there that holds too much memory is stopped, and the bot is told why, so one bot can't slow down the others.
Switch spaces on a phone
On a phone or a narrow window the Bots | Projects switch is gone: tap the title to go to Home or another project.
In a project the field at the bottom writes to its team.
A chat opened in a project fills the screen, and Back takes you to the project.
Each bot in one place in the Android app
A project's bots are no longer on Home: they are keys on the project's page, one row per team, with a crown on the lead.
Tap a team's name to open its team chat; hold it to see the team.
Home's Needs you lists every ask and marks a project's ask with its square; a project lists only its own.
Each bot lives in one place
A bot in a project's team now shows only in that project, not on Home.
A project shows its team as a row: the team's name opens its chat, then a key for each bot, the lead with a crown.
A project shows only its own asks; Home shows every ask, with the project's square on the ones from a project.
In a project, 1 to 9 open its bots and Esc opens the Chief.
Projects in a rail on the left
In a wide window with projects, a narrow rail on the left replaces the Bots | Projects switch.
Home and each project are one click away, and a project's square shows how many asks wait in it.
Home opens the Chief, a project opens its team chat, and the chat stays where it is.
Search and Settings are at the bottom of the rail.
Spaces in the Android app
The Bots | Projects switch is gone: Home and each project are spaces.
On a phone, tap the title to switch space; each project shows how many things wait for you.
On a wide screen, a rail on the left holds Home, your projects, search and settings.
A project opens its team chat; the app opens again in the space you left.
A botdot app for your computer
A new app for Windows and Mac shows your botdot in a window of its own.
Type your botdot's address once and sign in with your passkey in your browser.
Links to other sites open in your browser, and the window keeps its size and place.
Change a card by chat
Ask a bot of the project or the Chief to change a card ("add a graph to the Buildr card"): it knows the board's cards and changes the right one.
A change keeps what the card already knows: its repository, its period, what it counts. The Chief asks only what the change leaves open.
The admin page shows what runs long
An account's card shows how many commands run longer than five minutes, and the oldest.
RAM turns red when an account holds more than 85% of its memory for ten minutes.
A bot's commands end with its work
What a bot runs now ends when its run ends, also what it left in the background.
A command that runs too long or holds too much memory is stopped, and the bot is told why.
Programs nobody owns any more are cleared by themselves, so one forgotten command no longer slows the whole account.
A wider project board
In a project, drag the chat's left edge to give the board more room or less.
The width is the same as the chat in Bots; a double-click puts it back.
Bots and Projects keep the same frame
Switching between Bots and Projects in a wide window no longer moves the top bar or the switch.
The chat on the right keeps the same width in both, the one you set with its handle.
No empty screenshots from background programs
A bot that starts a program in the background no longer leaves a picture of its empty screen under its reply.
Screenshots under a reply are now the ones the bot took to look at something.
One chat beside your project
In a wide window a project shows its board and one chat on the right, like a bot's chat beside the keypad.
Opening a project shows its team's chat; a message without @ goes to the team's lead.
A bot, the team or the Chief picked in the list or on the floor takes that place, and its row stays highlighted.
The button at the top of the chat hides it and gives the board the whole width.
Drag a project's tiles anywhere
Drag any tile on a project's home to move it, or drag its edge or corner to resize it.
On a phone, hold a tile, then drag it.
The Arrange button is gone: a click on a tile still opens it.
Change a goal from the Android app
"Change" in a goal's menu asks the Chief to change it.
The Chief's chat opens over the Projects screen, as a bot's chat does.
Change a goal by telling the Chief
The pencil on a project's goal asks the Chief to change it: its target, its name, or the project's dates.
The Chief's chat opens at the bottom of the Projects screen, and the goal updates as it changes.
The Chief of Staff on a project's floor opens there too.
A project shows only its own bots
A project's home shows the bots of its teams, and no other bot of yours.
A bot in no team stays in Bots and appears on no project.
Adding a bot the Chief suggests always puts it in a team of the project.
Setup questions fit a project just for you
"What do they do today?" is now "How is it done today?", so it reads right after "Only me".
Chips for a project only for you are written as you speaking.
Long reminders arrive whole
A reminder keeps up to 2000 characters, ten times more than before.
A list stays a list: each item keeps its own line.
One that is still too long is refused, and the bot shortens or splits it. Nothing is cut off.
A bot's phone emulator shows on the screen
A bot testing an app on a phone emulator opens it in a window on the External Virtual PC.
A bot says something is on the screen only after it checked.
A project starts with a board
The Chief proposes goals and live cards along with the team.
Untick what you don't want before Create.
After Create, the board shows the goals, the cards, the team and the To-do.
Team cards show what each bot needs
A proposed bot shows the computer, saved logins and SSH keys it needs.
One that isn't saved yet has a button to pick or add it.
Create is the one OK: nothing waits in Needs you after it.
Setup questions that fit your project
The Chief picks the questions for what you start: a homelab gets asked what you run and what needs care, a wedding what done looks like.
Stories and the SWOT show only where they fit.
Without a SWOT, your answer to "What first?" becomes the first item of the plan.
The proposed team can be one bot when that is enough.
Cards reach your own servers
A project's settings have Logins: pick the Vault logins its cards may use.
A card can then read your own servers and services, such as Proxmox, over your network or Tailscale.
A card that needs a login it doesn't have says which server, with Add login.
A calmer new-project setup
A new project starts with one field for your site or idea; the clip in it adds files and links.
One question per screen, with the answer it builds on shown above it.
The delivery date has its own question: in 1 month, in 3 months, end of year, a date, or Indefinite.
The review is one SWOT and one list of your answers, each changed with a tap; Delete is in the ⋯ menu.
Delete a project during its setup
The gear at the end of the setup's steps opens the project's settings, with Delete, before the setup is done.
Right-click a project in the left column for its settings or to delete it; on Android, long-press it in the projects list.
A new project's questions follow your answers
Each question's suggested answers now build on what you said before it, so a home project gets home answers, not startup ones.
Change an earlier answer and the later suggestions are made again.
A run's steps in your language
The steps under a bot's reply and the line of a working bot follow the language in Settings.
Bots and the Chief write the steps of their commands in that language too.
Runs from before keep the words they had.
Start a project from scratch
A new project's first screen has Start from scratch: one tap makes an empty project, with no questions and no team.
It opens on its blank board; add pieces and cards from there, and name it in the project's settings.
A new project asks for its delivery date
The new project's review asks when it should be delivered: pick a day, or No date for an open-ended project.
The team the Chief proposes, its suggestions and the project's bots plan with that date.
Change it any time in the project's settings.
Cards on the board read the project's files
A card on a project's board now reads that project's folder: the drafts and files its bots made.
It reads only its own project's folder, and changes nothing there.
A new card answers in your language
A card's name, its questions and their suggested answers are now in the language you asked in, not another one.
The card the Chief of Staff builds after your answers keeps that language too.
boat.dev machines keep saving
A browser on a boat.dev machine no longer blocks its snapshots.
The admin page says when boat.dev can't save a machine.
Arrange your project's board on Android
The Android app shows your board as you arranged it, scaled to the screen; pinch with two fingers to zoom.
Tap the arrange button beside the gear, then long-press a tile and drag it, or drag near its edge or corner to resize it.
Arrange your project's board
The new button beside the gear lets you drag any tile anywhere and pull its edges or corner to resize it.
Tiles never overlap: one in the way slides down.
Your arrangement is kept for the project and looks the same on every screen.
Ask the Chief to move a tile for you, such as "put the calendar at the top".
A new project starts with an empty board
A project you make from now on shows only its name and New card.
New card offers 90 days, Goals, Teams, Calendar and To-do: add the ones you want.
Project settings turn each of them on or off. Projects you already have stay as they are.
Cards on the project board in the Android app
The Android app shows the cards Claude made at the top of a project's board, two to a line.
New card, the Chief of Staff's questions, the card being built and its menu with Change, Refresh and Remove work as on the web page.
Ask for a card on your project's board
On a project's board, New card takes what you want to see in your own words: open GitHub issues, customer calls, competitor prices, anything.
The Chief of Staff asks up to three short questions, then builds the card from the web or your connected apps while you watch.
Each card refreshes by itself once a day; its menu has Change, Refresh and Remove.
Projects: more chats side by side
The row of chats on the Projects screen now spans the whole width, so a wide screen shows more chats at once.
Chats narrow a little before one goes under +N.
Projects: drafts are saved in the project's folder
A project's bots save each draft or other piece of work as a file in the project's folder as they make it, and name that file when they say it is ready.
A lead checks the folder before its team report: work with no file there is reported as not written yet, never as waiting for your review.
Web: "Can't reach botdot" reads as one line again
When botdot can't be reached, or Claude is signed out, the line now sits under the logo, the full width of the list, instead of one letter per line beside it.
One slow answer while the page loads no longer shows the line: it appears only when botdot stays silent for 2 seconds.
Projects: several chats open side by side
A bot's chat you open on the Projects screen stays open when you open the next one, as many as fit the width.
Each open chat works as a full chat: send, reply, stop a run, answer cards and attach files there.
Each open chat counts as read; minimize one to turn it into a bar with its unread count.
Several projects on the phone
Tap the project's name at the top of Projects to switch: every project is a tree of its teams and their bots, and New project starts another.
The gear beside the name opens the project's settings, saved as you change them.
Open the project's folder from its settings to see its files.
Projects on Android: chats slide up over the floor
Tap a bot on the Projects screen and its chat slides up from the bottom; drag it up for full height, down to close.
Tap a team's name to open the team's chat: its lead first, and each reply signed by the bot that wrote it.
Type @ in any chat to mention one of your projects, and the bot gets what the project holds now.
Mention a project in a chat
Type @ and a project's name, like @Botdot, and the bot gets its goal, objectives, teams and open to-dos.
It works in a bot's chat, the Chief's chat and a group, where every member reads it.
Bots use your time zone
botdot takes your device's time zone when it has none of its own.
Bots say and set times in your time, not in UTC.
A time zone you chose in setup stays as it is.
Settings in groups
A bot's settings stand in three groups, each on its own surface: how it runs, what it uses, who and what it may.
No more line under every row, on every settings screen of the web page and the Android app.
The category chips no longer have a label above them.
Every project has a folder
Each project gets a folder that all its bots read and write, also the bots without a computer.
Open it from the project's settings: Folder, then Open. It works like a bot's Files.
Deleting a project asks whether its folder stays or goes.
What's new shows only what is new
A new account no longer opens with an old What's new window.
Notes with similar names now come in the right order.
The Projects screens on the same scale
Text on Projects comes in the same six sizes as the rest of the app.
Spacing and rounded corners follow the same scale, on the web page and on Android.
Lighter surfaces instead of frames
The open bot, Needs you, the message box, cards and menus sit on a lighter surface, with no frame around them.
The chat beside the bots is a lighter pane, with no line between them.
Secondary buttons, chips and fields are filled instead of outlined, on the web page and in the Android app.
A calmer Android app
Text comes in six sizes, so names, messages and titles line up across every screen.
Spacing and rounded corners follow one scale, the same as on the web page.
To-do items stay put under the mouse
Pointing at an item no longer moves its text or hides its day.
Delete appears in its own spot beside the item.
A calendar for the project, shared with your bots
The office floor has a Calendar: this week, and what comes next.
Open it for the month. Add an event on any day, with a time if it has one, and move or delete it.
It also shows the day 30, 60 and 90 check-ins, to-dos with a day, repeating ones included, and your bots' scheduled jobs.
The project's bots and the Chief of Staff read it and add their own events.
Leads take the week's plan and report to you
Each item of the week's plan names the team that does it.
When you approve the plan, each team's lead starts on its items and splits them among its members.
A new lead asks you how often to report: daily, twice a week or weekly.
The latest report shows in the team's panel in Projects, where you can also change how often it comes.
Team bots know their team
A bot in a project team knows the project, its 90-day goal, its team and who leads it.
The lead answers for the team: it splits your request among the members and brings back one reply.
You can still write to any member directly, and members ask you when they need a decision.
A team's chat answers like a group
A message that names nobody goes to the bots whose part it is, as in any group; the lead takes the ones that fit nobody.
The lead hands work on by naming members in the chat, so their answers show there.
Bots in a team's chat name and ask only the team's members.
Each team has its own chat
Click a team's name in Projects to open its chat at the bottom of the screen.
A message without @ goes to the team's lead, who brings in the members it needs.
Write @name to reach one member directly.
Several projects
Projects lists every project you run; + starts a new one with the Chief.
Each project is a tree of its teams and their bots: fold it, or tap a bot to open its chat.
Tap a project to see its floor. Each keeps its own goals and teams, and a bot can work in more than one.
On a phone, tap the project's name at the top to switch.
Routines named for what they do
A new team's routines are named for the bot's job, not for when they run.
The calendar now says what each routine does, beside its time.
Easier to read answers and Board values
A bot's or the Chief's answer keeps its lines short on a wide screen, in groups too.
A Board value in words, like "Eco until 17:00", fits one line; numbers stay big.
Quieter keys on home
A key's status words are grey now, and its colour sits only in the small dot before them.
"Needs you" still stands out in amber and bold, so what waits for you is easy to spot.
Projects on Android: To-do, calendar, standup and decisions
The To-do under the office floor has All, You, Bots and Done, and a task gets a bot, a day and a repeat.
The Calendar shows this week on the floor; tap it for the month, and add, move or delete an event.
The morning standup is one card, with Reply into the lead's chat when a team waits for you.
Your last decisions sit under the To-do: type one, with "because" and the reason.
Company is now Projects
The place beside your bots is called Projects: the switch reads "Bots | Projects".
Everything you set up there stays as it was: goal, objectives, teams and their leads.
Projects on Android: goals as pace charts, plan teams and lead reports
Each goal is a card above the floor: a pace chart, a bar or its status, picked from the card. One read from an app says when it last updated.
On day 1 a goal shows its target, the day and the first check-in date instead of an empty chart.
Each item of the week's plan shows the team that does it.
A team's sheet has Reports, how often its lead reports, and the latest report.
Goals as pace charts
Each goal with a number shows as a chart: where it stands against the line to its target over the 90 days.
Pick how a goal shows from its card: pace chart, bar or status. A goal with no number shows its steps to tick.
On day 1 a goal shows its target, the day and the first check-in date instead of an empty chart.
The floor keeps the teams in the main area; the Chief, bots without a team and New team sit in a narrow column.
One to-do for the project, shared with your bots
The panel beside the office floor is now the project's To-do, with All, You, Bots and Done.
Add a task for yourself or any bot of the project, with a day, and make it repeat daily, weekly, monthly or every few days.
When you tick a repeating task, the next one appears with its next date.
The bots of the project and the Chief of Staff see the list too: they add tasks, hand them on and tick off their own.
Project settings
The gear beside a project's name opens its settings: name, colour, goal and objectives, teams and leads, reports, the morning standup and the rules.
Every change is saved as you make it, and changes from the Chief show at once.
Archive a project to move it under Archived at the end of the list; botdot starts nothing for it until you bring it back.
Delete removes a project after you confirm. Its bots stay.
A decisions log for each project
Projects keeps your decisions with the reason and the day, under You: type one, such as "No paid ads because it is too early".
Tell the Chief of Staff or a team's lead a decision in chat and it writes it down for you.
Your answer at a day 30, 60 or 90 check-in is logged too.
The project's bots read the latest decisions in every run, so they stop asking what you settled.
Product cards on the phone
The Android app shows a bot's shopping results as product cards too: its pick on top, the rest as rows.
Open goes to the store; Save puts the product in the bot's Saved-products file.
Shopping results as product cards
When a bot finds products to buy, its pick shows as a card: photo, price, rating, store, why and delivery.
The other results are rows under it; tap one to open the store.
Save puts the product in the bot's Saved-products file, which you find in Files.
Morning standup
Each workday at 09:00 every team lead writes three lines: done, next, blocked.
The Chief sends you one message with all of them, and Projects shows them on one card.
What waits for you shows first, with Reply into the lead's chat.
Ask the Chief to change the time or switch it off; nothing starts in quiet hours.
Jobs say when they run in plain words
A card for a new or changed job now says when it runs, like "Daily at 08:00", instead of a cron code.
It also says what kind of job it is: a run of the bot with AI, or a script with no AI.
In Polish, schedules are now written in Polish everywhere.
Clear notes under the Chief's reply
When a change waits for your OK, the note under the reply says so, for example "Job “Morning news” waits for your OK".
No more "Created undefined" or "Added job undefined".
Goals that update themselves
A goal's number can come from a connected app, such as active subscriptions in Stripe: pick Update from an app on its card, or tell the Chief.
botdot reads it every day (or week) and the chart moves on its own.
The card shows when it last updated. If a read fails, you hear it once, not every day.
An empty chat starts with its jobs
A bot's empty chat shows its head and name in the middle, with the message box right under them.
Its jobs sit under the box: a tap runs one now.
A new Chief chat looks the same, with the Chief's own jobs.
With the first message the box goes back to the foot of the chat.
Projects: bot chats docked at the bottom
Click a bot on the Projects screen and its chat opens at the bottom of the screen, with the project still in view.
Open more chats side by side; a minimized one is a bar with its unread count, and the rest wait under +N.
Drag a chat sideways to reorder the row; your open chats are kept on this device.
On a phone the chat slides up from the bottom; drag it up for full height.
Company: the office floor on the phone
A running company opens on its office floor in the Android app: the objectives, the Chief's office and a room per team.
Tap a team's room to see its bots and move the crown with Make lead.
Answer the day 30, 60 and 90 check-ins and approve or change the week's plan from the phone.
Company: set up your company on the phone
The Android app has the switch at the top of the list too: Bots, or Company.
Say what you are working on, answer the Chief's questions and write your stories on the phone.
Review the proposed team, change it in a line with Undo, and create it from the phone.
Company: check-ins on day 30, 60 and 90, and the week's plan
A line under your company's name shows days 30, 60 and 90.
On each of those days the Chief of Staff shows every objective on track or behind: Keep going, Change direction or Stop.
Each Monday the Chief drafts three things for the week, each tied to an objective. Approve it, or say what to change.
As your company grows, the Chief suggests one new bot at a time. Add it, or dismiss it.
Company: the Chief proposes your team
In the Team step the Chief of Staff proposes three to five bots from your answers.
Rename or remove a bot, switch its routine, choose when it asks first, and connect its apps on its card.
Ask the Chief to change the team in a line, with Undo, or add a copy of a bot you already have.
Create makes the bots and their teams, each team led by its first bot.
Company: a place for your company
A switch at the top of the list: Bots, or Company.
In Company, say what you are working on: your site, or your idea in one sentence.
Add files and links the Chief of Staff can read.
Company: your company's home is an office floor
Each team is a room: its lead sits at the head with a crown, the team's questions counted on the lead.
Bots at work or waiting for you sit at a desk with what they do now; the others wait on a bench.
The whiteboard shows your objectives, the Chief of Staff sits in a glass office beside it.
You: what waits for your OK and your tasks. Write "@Bot task" to hand a task to that bot.
Company: the Chief helps you describe it
Give your site, and the Chief of Staff reads it and fills in what it can.
A new idea gets five quick questions, with answers to pick with one tap.
Write what you want your users to be able to do, then see a quick SWOT with one first test.
Bots after Projects opens the Chief
Switching from Projects to Bots now opens the Chief of Staff's chat.
A chat you opened on Projects no longer keeps the Projects screen up.
A tidier account card on the admin page
Each account shows one button, Change share; Suspend, Resume, New sign-in link and Delete are under ⋯.
Delete turns red only in the box where you type the account's name.
Dates read "Joined Oct 18 · seen 2 h ago"; hover one for the full date.
The state is a coloured dot and a word, and the use numbers line up on the right.
Every bot's status is back on home
Under each bot's name one short line says how it is: Idle, Needs you, unread replies, Done or Couldn't finish.
While a bot works, the line says what it is doing right now.
The Chief of Staff's key shows its status too.
External Virtual PC: a slow screen keeps starting
When the External Virtual PC is slow to open its screen, the Computer window shows Starting… and tries again, instead of saying it can't be reached.
When it really can't be reached, the message says why.
Admin: see why a run failed
On the admin page, click a failed run in an account's usage to see the line of its error.
Addresses, paths, quoted text, ids and secrets in it are hidden before it reaches the page.
The Android app speaks Polish
When your account's language is Polish, the whole Android app is in Polish: screens, cards, buttons, notifications and messages.
Dates, times and counts follow the language too.
What your bots and the Chief write stays as they wrote it.
The web page in Polish
With Polski chosen in Settings, every screen of the web page speaks Polish: home, chats, Needs you, Board, Files, settings and dialogs.
Dates and times follow Polish too.
What your bots and the Chief of Staff write stays as they wrote it.
Needs you and notifications in Polish
With Polski chosen, cards in Needs you, their buttons and warnings are in Polish.
So are botdot's notifications, its error messages, when the checkup runs and the model and effort labels.
What a bot or the Chief writes stays as they wrote it.
A finished run's steps stay folded
When a run ends, its steps fold into one line, even if you opened them to watch it work.
Tap the line to open them again.
A click that cannot be undone waits for your OK
When a bot is about to confirm something a web page says cannot be undone, it asks you first on a card in Needs you.
Your no stands until you ask the bot again, also when it carries on later; taking control of its screen counts as a no.
Asking for it in chat is not enough: the card still asks. A page that only mentions it opens no card.
A quieter home and chat in the Android app
Each bot is its head and its name: one dot says it works, needs you or has new replies.
The Board's numbers sit in rows without boxes, and Allow or No answers a permission right on home.
A task in a chat is your message, one steps line and the reply as plain text; hold it to reply, see the details or copy.
Settings are one list that saves by itself.
A quieter home, chat and settings on the web page
Each key shows only a bot's head and name; one dot says it works, needs you or has new replies.
The Board's numbers never get cut, and what needs you can be allowed right on home.
Chats have no frames: your message, one steps line and the reply as plain text, with Details and Copy on hover.
Every settings screen is one plain list, and a short "Saved" shows when a change is kept.
Settings in Polish
Settings has a Language row: English or Polski, on the web page and in the Android app.
Settings itself is in Polish now; the other screens follow in the next updates.
The choice is kept for the account, so the web page and the phone always match.
Steps show while a bot works
Open the steps line of a working bot to see every step it took so far.
New steps appear while it stays open, on the web page and in the Android app.
A bot's plan keeps up
The plan above the message box follows the bot's steps again after the phone changed networks or was in the background.
The same on the web page when its connection dropped for a moment.
Reply to a task in a bot's chat
Reply on a task's block sends your next message to that task. On the phone, press and hold the block.
To a task at work it goes in at its next step. To a finished one it carries on in the same block.
The chip above the box says what you reply to. Tap ✕ to send a message of its own.
Each task in a bot's chat is one block
What you asked, the work and the reply sit together in one frame per task.
The steps fold into one line: how many, the skills it changed, the bots it messaged. Tap it for the timeline.
A task at work shows what it is doing now and its own Stop button.
On a phone a long reply shows its first paragraph and More. Links are never folded.
A skill's chip opens that skill
Tap "Changed the skill …" under a reply: the bot's settings open on that skill, its instructions shown.
The same for a skill at the start of your own message in a bot's chat.
A skill that is gone opens the bot's Skills.
Replays have their own place on the admin page
"Replays an hour" moved out of Decision model into a new Replays section.
Every section of the admin page says in one line what it is for.
One account's usage on the admin page
Click an account in the Usage table to open its own numbers below it: runs a day over 30 days, outcomes, failures and features.
Each failed run is listed: when, why (ran over 4 h, Claude usage limit, timed out…), which bot by number, from a chat or a job, how long it took and which tools failed.
It also shows active days, cards answered and the typical answer time, web vs Android, activation, week 1 and week 4, and its version.
A follow-up joins the work it belongs to
Write "try again", "check X too" or a short correction while a bot works, and the bot takes it into what it is doing instead of starting over beside it.
A quick question such as "how far are you?" gets a short answer and starts nothing.
Anything else still starts beside the work in progress, as before.
A no to a login holds
When you decline a bot's login pop-up, the bot doesn't ask you for it again on its own.
Declined by mistake? Tell the bot to ask again, or save the login in the Vault.
A bot no longer asks you for a password that only its own computer has, such as a local mail bridge's.
A bot's runs know about each other
When a bot works on two or three things at once, each run sees what the others were asked and their plan.
A run that was already working hears when a new one starts beside it.
A bot checks what its other runs are doing before it says something is done or not done.
Usage counts on the admin page
The admin page has a Usage section: weekly active accounts, activation, week 1 and week 4 retention.
It also shows runs, failures by kind, how often replies were corrected and which features accounts use.
Each account hands over counts once a day: no messages, files or names, and nothing leaves the machine.
Mention a file with @ in a bot's chat
Type @ and part of a name: the bot's files and folders come first, from botdot, its computer and its shared projects.
Pick a folder, or type / after its name, to look inside it.
A picked file shows as a chip in your message; tap it to open the file.
The bot is told where the file is, and gets a small text file's text with it.
Files: every file of a bot in one place
Open Files from a bot's chat or its settings, on the web and on Android. It replaces the Workspace and Files sections.
Its folder on botdot, on the computer and in each shared project, side by side, as a list or a grid with pictures.
Select, rename, delete, upload by dragging, and move or copy to any of its places.
Keep any file on botdot in mind from its menu.
A bot's new main assignment is tried before you approve it
When a bot proposes to rewrite its main assignment or rules, it is first tried on its last 20 tasks.
Its card then says how it did, for example "Better on 14 of 20 past tasks, worse on 1."
After you approve, "Undo last change" in the bot's settings puts the old text back in one tap.
The Chief's weekly report lists what changed, with its score.
The External Virtual PC's browser starts again
Screenshots and open_browser work again on the External Virtual PC: its screen stopped starting after a library update.
If the screen ever fails to start, the bot's error now names what didn't start, with the last lines of its log.
The Chief tests a skill before proposing it
A skill the Chief's weekly review proposes is first tried on the bot's last 20 tasks, with and without it.
Its card says how it did, for example "Better on 14 of 20 past tasks, worse on 1."
A skill that did worse gets no card; the review's report names it.
The machine's admin turns this on with "Replays an hour".
Routine jobs move from AI to scripts once proven
The Chief can try a script beside a bot's AI job for a week, without asking you first.
If every run gave the same answer, one card offers the swap. If one differs, the AI job stays.
After a swap, one tap brings the AI job back exactly as it was.
Copying a bot's files no longer stops half way
A copy whose External Virtual PC started again in the middle packs the files again and carries on by itself.
When it still fails, it says why instead of "handed out nothing".
Caches that tools fill again by themselves stay behind, so copies are smaller and faster.
Bots reach the shared External Virtual PC again
Bots that each had an External Virtual PC of their own now move to the account's one even when no new machine can be made: the first bot's machine becomes the account's.
A move that was refused because too many machines were running is tried again by itself after 10 minutes.
Camoufox on the External Virtual PC
Bots on the External Virtual PC find and open Camoufox, also before their first screen tool.
Camoufox is the browser of its desktop: links you open there go to Camoufox, not Chrome.
One computer choice for all your bots
Settings → Computer chooses where every bot's computer is: this machine or the External Virtual PC.
Switching moves all bots with a computer there, with their files if you choose Copy files.
A bot's settings now only switch its computer on or off.
Shared projects: one folder several bots work in
In a bot's Workspace, + Project makes a folder on the computer that the bots you pick share.
Each of them is told about it and works on the same files there.
Upload into it, make folders, change its bots or delete it from any of their Workspaces.
Folders in a bot's workspace, on the computer too
Upload folder puts a whole folder, with its subfolders, into a bot's Workspace.
On the computer, the Workspace now makes folders, uploads, renames and moves, as it does on botdot.
What you set up there is where the bot's commands run, under the same path.
A bot's question for you is no longer lost between bots
When a bot asks a teammate for something and the teammate needs your OK, the asking bot puts the question to you.
If it doesn't, the question now opens in the teammate's own chat, with its answer buttons, instead of staying folded.
Questions show as a card again
When a bot asks several questions and adds a line after them, you get the card with a box under each question, not the raw [[ask: …]] text.
A stray [[ask: …]] inside a sentence shows as plain words, never with brackets.
Browser logins go along when a bot's computer moves
With Copy files, a bot's browser profile moves with its folder, so it stays signed in.
Works both ways between this machine and boat.dev.
Caches stay behind.
One boat.dev machine for all your bots there
Bots on boat.dev now share one machine of the account's, each in a folder of its own, so you pay for one machine instead of one per bot.
They share its screen and its browser too, as bots on this machine share its computer.
A bot that must be kept apart can still have a machine of its own: ask the Chief.
A bot that already had its own machine has its files copied over by itself, and its old machine is let go only after the copy succeeds.
A bot on boat.dev clicks, types and browses there
A bot whose computer is on boat.dev now works on its own machine's screen, with its own Camoufox, as on this machine.
It signs in with your saved logins there too, typed by botdot and never seen by the bot.
The first screen tool on a new machine sets the screen up, which takes a few minutes, once.
See the screen of a bot on boat.dev
The screen of a bot whose computer is on boat.dev now shows its machine's desktop, on the web and on the phone.
Take control to use its mouse and keyboard; until then you only watch.
Opening it starts the machine, and it stays on while you watch.
A bot on boat.dev uses saved logins
A bot whose computer is on boat.dev can use a saved login, SSH key or file in a command on its machine, as on this machine.
A GitHub login there pushes with git.
The secret is there for that one command and never shown to the bot.
Files go along when a bot's computer moves
Switching a bot between this machine and boat.dev asks: Copy files or Start empty.
Its folder is copied in the background; its settings show how far it is.
Browser logins and Tailscale stay on this machine: boat.dev has no browser.
boat.dev machines named after their account and bot
On boat.dev, each bot's machine is now named botdot, then the account, the bot's name and its id, so the admin sees whose it is.
Machines made before take the new name the next time they start. Their files stay.
Bots' computers work again on servers with several accounts
The live screen shows again, and a bot's computer tools run again.
When a screen can't be shown, its window says so.
A bot on boat.dev shows its own machine
Its computer button shows its boat.dev machine: its size and whether it is on.
No more screen, reset or update of the account's computer for a bot that works on boat.dev.
Bots sign in to git by themselves
A bot's git and ssh use the SSH keys you share with it, not only on its computer.
A GitHub App you share with a bot lets its git clone and push over HTTPS, with a token that ends within the hour.
Nothing is written into the repository, and the bot never sees the key.
Bots hand over files from their computer
A bot with a computer attaches a file it made there, or a download, straight to its reply.
It can send such a file to a teammate too.
Files you give a bot with a computer are on its computer as well.
Files a teammate handed over open again
A file a bot names in its reply opens even when a teammate handed it over, like a script or a log one bot made for another.
A file a bot made in one of its folders opens from its plain name too.
Bots commit under their own name
A bot's git commits carry its name, on botdot and on its computer, with no setup.
A bot's folder is no longer an empty git repository, so git there stops failing with "no commits yet".
Choosing a bot's computer
In a bot's settings, one Computer choice says where it works: none, this machine (free) or boat.dev (costs).
It shows once boat.dev is set up; until then the Uses the computer switch stays.
The size of boat.dev machines
In Settings, choose how big the account's boat.dev machines are: from 2 CPUs to 16, each with its price per hour.
A bot's machine takes the new size the next time it starts. Its files stay.
Nothing left running on the computer
What a bot's command leaves running in the background ends with the command.
A program a bot starts on its screen ends when that screen rests or ends.
Should processes pile up anyway, the computer's status says "Left behind".
The admin picks the decision model
The admin page's Group router is now Decision model: Haiku or Jev latest.
The same choice decides who answers in a group and whether a note wakes a bot.
Jev is always its newest version; a saved choice of Jev moves to it.
A bot's computer on boat.dev
In a bot's settings, a bot that uses the computer can work on a machine of its own on boat.dev instead of this machine.
It starts on the bot's first command and stops after 30 minutes unused. This machine stays free; boat.dev costs.
It has commands and files only: no screen, no browser and no saved logins.
Site icons before links
A link in a reply now shows the site's small icon before it, on the web page and in the Android app.
botdot fetches each icon itself and keeps it for a week, so the site never sees you or your phone.
A site without an icon shows a grey globe.
Script jobs can use saved SSH keys
A script job can reach a server over SSH with a key from the Vault, for checks like a morning infra review.
botdot signs for the script, so the key is never in the script, a file or its environment.
Settings folds
Every section of Settings now opens and closes with a tap on its title, on the web page and in the Android app.
They are all closed when Settings opens, so the whole page fits on one screen.
Script jobs can use saved logins
A script job can call an API with a login from the Vault: botdot sends the request, and the script never sees the secret.
The card of a script job lists the logins it uses, and a login added later waits for your OK again.
The Chief now sets up routines that only count or check as scripts, so the AI runs only when the script finds something.
Bots wake only for notes that need them
The admin can switch on Wake bots only when needed, under Group router.
A note from a teammate or a webhook that can wait then starts no run: the bot reads it on its next run.
It shows as Later under the notes waiting. Questions, approvals, deadlines and anything unclear still wake the bot.
The admin picks the group router
The admin page has a Group router: Haiku, or Jev with an OpenRouter key.
Jev picks who answers in a group in a fraction of a second.
When Jev can't answer, Haiku picks as before.
In a group, only the right bots answer
A message without a mention goes to the one or two members whose part it is, picked in about a second.
A greeting or a question for everyone still goes to every member, and so does anything the pick is unsure of.
Mentions and @all work as before, and any member can still hand the work on.
The web page moves instead of jumping
The Board grows out of its key and shrinks back into it.
On a phone a chat slides in over the list, and Back slides it away.
Settings, files, dialogs, toasts and folds slide or fade in; an answered card in Needs you moves to its place.
A key that finishes its work pops once. With reduced motion turned on, everything only fades.
A bot's runs, listed above its message box
With two or three runs going, each one has a row above the message box: what you asked, what it is doing now, and its own Stop.
A run that waits for your OK says so in its row; tap it to see the card.
A finished run gets a check and folds away. With one run, the line under the chat stays as it was.
A long task no longer holds up a group
A bot still working after 90 seconds keeps working in the background, and the next bot answers.
Its result lands in the group when it is done, and the bots it names take over from there.
Your next message no longer waits for a bot that works in the background.
The Chief answers when its memory is slow
A message to the Chief no longer fails with a raw "No deferred tool marker" error when looking through its notes takes a few seconds.
If a message ever fails to reach Claude, the Chief says so plainly and asks you to send it again.
Shared rooms and the Board fit a narrow list
On a tablet, the Shared rooms row in the list stays one line instead of a column of letters.
It says only how many invitations wait, and nothing when none do.
The Board's row shows its first tile cut short when no tile fits whole, instead of an empty row.
Select all bots when importing skills
The bot list in Import a skill has Select all and Deselect all, like the list of skills above it.
A bot with skills turned off keeps its box as it is.
Bots in a group read each other before they answer
A message you send while the bots are still answering your last one waits until they are done, then they answer it knowing what was said.
A bot that answers after another is told who already answered, and adds only what is new or passes.
Messages to different bots in the group still go at the same time.
Saving in the Vault no longer makes you wait
Adding a login, an SSH key or a file, and choosing which bots may use an item, close their dialog right away while Bitwarden saves.
If Bitwarden says no, the dialog comes back as you left it, with the reason.
Sync and Lock, importing skills and duplicating a bot work the same way, with a small line that says how it went.
See how many runs a bot has going
A bot working on two or three things at once says "Working ×2" or "Working ×3" on its key.
Its chat says it at the top too.
A new skill is in "/" at once
A skill you add to a bot shows in its "/" list right away on the web page, not a minute later.
The same goes for a skill a bot or the Chief writes for it.
A run no longer fails when the Claude sign-in is renewed
A bot whose run was cut off by a renewed Claude sign-in carries on where it stopped, by itself.
"Claude refused my sign-in" now shows only when the sign-in is really gone.
File names in a bot's Files list read again
Each file's name stays on one line, cut short with "…" when it is too long; hover it for the full name.
In a narrow window the size, date, Keep in mind and Delete move below the name instead of squeezing it.
A page's buttons answer at once
"Keep it up to date" closes its dialog right away, and a small line says the schedule is being saved, then that it is done.
Refresh now and Stop say at once that they are working, and Board flips the moment you tap it.
If something fails, it says so, and a tap tries again, with what you entered kept.
Mention a page or a tile in a chat
Type @ and a page's title, like @IssueList, and the bot gets what the page says now.
A tile of the Board works the same way: @LivingRoom hands over its value.
It works in a bot's chat, the Chief's chat and a group, where every member reads it.
Smoother movement in the Android app
Screens slide in from the side and back out, and Back follows your finger.
The Board grows in and shrinks back; the settings panel and the viewer slide in from the right.
A card you answer in Needs you fades away and the rest move up; folded lines open smoothly.
A key going from Working to Done says so with a short pop.
Always allow covers every call of that action
"Always allow" on a connected-app card lets the bot do that action from now on with any details: another pull request, another recipient.
Before you confirm, it says which bot and which action it lets through.
A bot's settings list these under Always approved, each with Revoke.
Reconnect says what it is doing
The Reconnect card shows that it opens the sign-in, then that it waits for it, then that the app is connected.
When connecting fails, the reason stays in the card in plain words, with Try again.
The Connectors page no longer stays blank when an app's connection comes back without a status.
A paused account is no dead end
The page of an account the admin paused has Use another account: it signs this browser or phone out and opens the sign-in.
Signing in with another passkey in the same browser ends the session it had.
A page or app open when the account is paused shows the paused screen at once.
A bot's answer to you is no longer hidden as a reply to a bot
When a teammate brings a bot its results late, the bot's reply is shown to you as a normal reply.
You get its question and buttons in that bot's chat, not a copy in the teammate's chat.
Messages that really go between bots stay folded.
Disconnect removes the app
Disconnect on the Connectors page takes the app off your list and off its bots every time.
If Composio didn't confirm, botdot says the app may still be connected there.
An answer passed on by the Chief closes the question
When you answer a bot's question elsewhere, on a card in Needs you or in the Chief's chat, and the Chief passes it on, the bot's question closes.
Its answer buttons go, and its key no longer says "Needs you".
The app no longer freezes with a page on the Board
With a page shown on the Board, every refresh held up the whole app for seconds, longer on a busy machine.
The Board now reads that page once and again only when a page changes, so chats and replies come straight away.
An answer button is tapped once
Tapping an answer under a bot's question shows your message and "Working" at once, and the buttons go.
The buttons no longer come back while the app catches up, so a second tap can't send the same answer twice.
If the answer couldn't be sent, the buttons come back and a new tap sends the same message once.
A reply stands where it ended
A reply that ends after a /btw or another task now shows below them, at the end of the chat.
Your own messages keep their order, and a bot at work keeps its line at the bottom.
Group chats follow the same order.
Bots write in their group chats
A bot can now post in a group it is in on its own, for example a scheduled report for the team.
Its post shows under its name and you are notified, as for a new message.
Only the bots it names answer it.
Pages from your bots in the Chief's chat
When a bot saves a page in a task the Chief gave it, the Chief's reply shows the page. A tap opens it.
The Chief names the page by its title.
Back to chat works from a document
Back to chat on a document opened from a chat now opens that chat. Before, only the address changed.
A page opened as a document goes back to the chat of the bot or Chief of Staff it belongs to.
The browser's back and forward between a chat and a document work too.
Pages on the Board
A page can be a tile on your Board: its first numbers or first lines, and how long ago it was updated. A tap opens it.
Tap Board in the page's bar to put it there, or use the switch beside each page in Settings > Pages.
No page is on the Board until you put it there. The bin on its tile takes it off; the page stays.
Refresh the Board now
The age beside the Board's title is now a button: tap it and every tile reads its value again at once.
Its arrows turn while it reads. On a phone, pulling the Board down does the same.
A tile read a few seconds ago is left alone, so tapping again doesn't flood its source.
The yes button wears the bot's colour
When a bot asks a yes or no question, its yes button is filled with the bot's colour and the no stays outlined.
The Chief's yes is in the Chief's colour.
Choose the Board tiles on home
The pencil beside the row of Board cards on home, or a long press on a phone, lists every tile of the Board.
Check the ones you want there, uncheck the rest, and drag them into your order. It is saved at once.
Until you choose, the row shows every tile, as before. The Chief can set it too: "put Proxmox CPU on home".
An open botdot window takes each update by itself
A botdot window left open, also one installed from Chrome, loads the new version on its own after an update.
It waits until nothing would be lost: no dialog open and no message typed and not sent.
Skills and "/btw" show as chips
A skill or "/btw" at the start of your message shows as a blue chip, in the message box and in your sent message.
A name that is no skill of the bot stays plain text, so you see at once whether it runs something.
"/btw" passes work on to a busy bot
"/btw check the backups too" to a working bot now goes into the work it is doing: it reads it at its next step.
A "/btw" question is still answered at once, as before.
Rooms are joined by their invite link
New room asks for a name only, then shows the room's invite link to copy or share.
Inviting an account by its name is gone; invitations already sent still work.
The Rooms screens are shorter: no explanations under titles and fields.
Plain words when a connected app fails
Save to Google Docs no longer shows Google's raw error: you get one short sentence instead.
When Google Docs wasn't given the access it needs, a Reconnect button connects it again and saves.
Errors botdot doesn't know yet are put in one sentence by Claude.
Bots stay readable beside an open page
With a page open beside a chat, the keys on the home screen now stand one or two a row instead of three.
Every key keeps its head, name and status, and nothing scrolls sideways.
Connectors use your own Composio key
botdot no longer makes a Composio account for you: the ones nobody claimed stopped working.
Connectors ask for an API key from your own Composio project, with a link to get one at composio.dev.
The key sits at the top of Connectors, on the web page and in the Android app: add, replace or remove it there.
Without a working key, Connectors show only the key field.
Ask for a change right on a Board tile
On the web page, the pencil on a tile (or a right-click) opens a small box: say what should change and send it.
On the phone, hold a tile to open the same box.
It goes to the Chief of Staff as a new chat that names the tile, and the Chief changes it.
Removing a tile is the trash in the same box.
A Reconnect card when a job finds an app signed out
When a bot's scheduled job finds a connected app signed out, its chat shows a card with a Reconnect button.
At most once a day per app, so a job that runs every hour does not fill the chat.
Connect the app again and the next sign-out gets its card at once.
Board tiles say how fresh they are
A tile or heading that reads its own value now says only how long ago it last read it, like "1 min ago".
Where the value comes from ("http · 1 min") shows on hover on the web page.
The count of sources under the Board's title is gone.
A reply the Chief drafts for you unasked is a mail card too
When the Chief spots a mail you owe a reply to, its draft shows as the same card as in a chat: To, Subject and the text.
Send now sends it after your OK, and Not now leaves it unsent.
A job you ask for is set up at once
When you ask the Chief of Staff for a bot's job, it is added without a card, also after the Chief read the web in that chat.
A job the Chief sets up on its own after the web still waits for your OK.
A bot that needs you shows its question in its chat
When a bot's key says Needs you, its chat now shows the question, however far back it was asked.
Its answer buttons stay under that question, also after the Chief or another bot wrote to it since.
Replies you owe, drafted in your style
Say "learn how I write" and the Chief of Staff reads your sent mail and keeps a short note on how you write.
When an email has waited 2 days or more for your answer, the Chief writes first with a draft reply: Send or Change.
The Chief makes Gmail drafts without asking; sending still waits for your OK.
A mail draft is one card in the Chief's chat
A mail waiting to be sent shows as a card with To, Subject and its text, and Send now and Not now on it.
Not now keeps it in Drafts, and Send now stays on the card.
A corrected draft folds the version before it, and a sent mail folds to its subject and the time it went.
Replies between bots are folded
In a bot's chat, its reply to another bot or the Chief of Staff is one line: whom it answered and the first words.
Tap the line to read the whole reply.
The message that started it shows its first words too.
Claim the Composio account botdot made for you
Until it is yours, the top of Connectors asks for your email: Claim sends Composio's invite.
The invite is good for 24 hours; the line says when it runs out and can send it again.
Connecting your first app asks for the email too. The line goes away once you have accepted.
The Chief briefs you at the times you name
Tell the Chief when you want to hear from it, like "at 9 and 16": its first message of the day is then a short brief with links.
The brief has four parts: needs your decision, waiting on others, ready for you, changed since the last one.
Once a week the Chief may offer one bot or job for something you keep doing yourself.
After you first connect your mail or calendar, the Chief tells you once what it learned and proposes three things.
Connectors say plainly when Composio refuses the key
When Composio stops accepting the key, the Connectors page says whose key it is: botdot's own Composio account or yours.
One step fixes it: New Composio account (botdot and your bots stay as they are), or paste a new key of your own.
The apps you had show with Connect again, and bots get them back once connected.
botdot first fetches the newest key of its own Composio account, so a replaced key keeps working by itself.
The Chief of Staff has scheduled jobs of its own
Ask it, e.g. "every weekday at 8 tell me what's new on Hacker News".
At that time it looks it up and writes what it found in its chat.
These jobs only read: they change nothing and send nothing.
Its settings list them, with a switch and Remove.
Interactive pages look like botdot
A bot builds an interactive page from botdot's own style kit: the app's dark colours, Geist, cards, pills, tables and a kanban.
It starts from a template (plain HTML, Svelte, or a roadmap with views, filters and cards that open) and adapts it.
Everything comes with botdot, so the page loads nothing from the internet and works on a phone too.
Bots still prefer a page of blocks; they make an interactive one when you ask for something blocks can't do.
Interactive pages
A bot that uses the computer can publish a small site it built as a page: views to switch, filters, a kanban, cards that open.
It runs isolated on an address of its own: it can't see your account or reach the internet, and a link out asks you first.
Versions lets you go back to an older one; Download gives you its files as a zip.
After an update, port 8443 carries these pages; on a public domain keep it open.
Tables you can sort, search and filter
A bot's page and the Board can show a table: tap a header to sort, type to search, and pick All, Done or another state to filter.
States show as coloured pills, and issue and pull request numbers open as links.
On a phone a table turns into a list, and a long one shows 10 rows a page.
A table tied to a Board tile stays live and keeps your sort and filter.
Bots know how to build a good-looking page
Every bot and the Chief of Staff now have a skill for pages: a big title, the key numbers with their change, charts side by side, status pills and what waits for you.
Numbers on a page are tied to Board tiles where they can be, so they stay live; "Keep up to date" rewrites only the words.
Ask for "an overview", "a status page" or "a weekly report" to get one.
A bot's page looks like the Board
Pages can open with a big title and a lead line, and show numbers with their change and a line of recent values, charts side by side, status pills and callouts.
Numbers tied to a Board tile stay live while the page is open, with no rewrite.
Copy, Open as document and Download write the numbers and charts out as text and tables.
Ask a bot for a page "with live numbers" to get one.
Your bots at a glance, on the home screen
The Board's values sit over your bots as small live cards with their recent values; on a phone they scroll sideways.
Needs you is one card: how many things wait, what they are, and Review.
Each bot shows a status and when it last did something: Working (with a running line), Needs you, unread, Done or Idle.
Pinned bots are larger. Hotkeys, Esc, Ctrl+K and your order work as before.
The Chief notices what's coming in your mail and calendar
When Gmail, Google Calendar or Outlook is connected, the Chief's own messages also look at your next 48 hours: a check-in that opens, a ticket that hasn't come, an invitation you haven't answered.
It only reads: it never sends, changes or deletes anything there, and asks you nothing on a card.
If it can help, it offers one step with Yes and No buttons.
Ask the Chief of Staff "/btw" while it works
Start a message with /btw while the Chief is replying, and it answers at once.
The answer comes from what it is doing right now; its reply goes on.
Its next reply knows what it told you.
The Board looks like a status page
Each heading says which bots its tiles come from, and you can show one heading at a time.
A number shows how it changed ("▲ 0.8 since 08:00") with a line of its recent values; charts have a legend, and a tap or hover says the values.
Switches and buttons under a heading sit together in one Controls box. "Live" at the top says how fresh the newest value is.
On a phone the tiles go one across, numbers two across. Ask the Chief for a chart, a status or a callout on a tile.
Rename your Chief of Staff in its settings
Its settings now start with a Name field, like a bot's.
Leave it empty to go back to "Chief of Staff".
You can still ask the Chief for a new name in its chat.
Save to Google Docs connects it for you
In a document's Export menu, Google Docs not connected yet: one tap opens the Google sign-in, and on the web page the document is saved as soon as you're done.
On the phone, sign in in the browser, then tap Google Docs again to save.
If connected apps aren't set up on this server, the row says "Not set up" and tells you why.
Pages from the Chief of Staff
Ask the Chief for a report or an overview: it saves it as a page, with a chip under its reply that opens it.
The Chief's pages are listed in its settings and in Settings, Pages, beside your bots' pages.
Tap Keep up to date on one of its pages: the Chief rewrites it on that schedule, with no card to approve.
The Chief of Staff keeps files in mind, as a bot does
Its settings now have Files: what you attached in its chats, to open, keep in mind or delete.
A file kept in mind comes with every reply of the Chief: tap Keep in mind, or ask it to.
Its settings also have Workspace, to see and manage every file in its folder.
The Chief's settings show what you always approved
"Always approved" in the Chief's settings lists what you said to always allow on its cards.
Actions in connected apps, like sending email with Gmail, and changes it may make after reading the web, like reminders.
Revoke takes one back at once: the Chief asks you again next time.
What's new shows everything since your last look
After an update, What's new now lists every change since the one you saw last, not only the newest three.
The newest three show in full; tap any other title to see its points.
Settings → Updates lists everything a waiting version brings, too.
Shared rooms: your bots and other accounts' bots in one chat
When the admin turns shared rooms on in the admin page, Rooms shows in the list: chats with people of other accounts on this machine and their bots.
Make a room, invite an account by its name or with a link, and @mention a bot to have it answer.
Each bot's settings say whether it may be in rooms and who may mention it there.
Your own bot mentioned by you works with its tools, each step on a card for your OK; what it posts to the room waits for your OK too.
The Chief hands a bot a task without asking
After the Chief read the web in a chat, giving a bot a task no longer waits for your OK on a card.
The bot starts right away and treats that task as outside content: what it saves is marked so, and its own cards still ask you first.
Making, changing or deleting bots, jobs and the rest still wait after the web, as before.
A bot's own key on the keypad
In a bot's settings, "Key on the keypad" gives it its own digit, 1 to 9.
In a wide window that digit opens its chat wherever it stands, also from a folded category.
The digits no bot holds still number the other keys by their place.
The Chief can set it for you too: ask it to give a bot a key.
Save a report to Google Docs
Export on a document now has Save to Google Docs, on the web page and on the phone.
It needs Google Docs connected on the Connectors page; the new document opens once it is saved.
Reports as documents on the phone
A long reply in the Android app has "Open as document" under it.
It opens full screen; Export saves it to Downloads as Word, PDF or Markdown, or shares the PDF.
Pages: every bot's pages in one place
Settings has Pages now: the pages of all your bots in one list.
The pages kept up to date come first, then the others, each with its bot and when it was last updated.
Tap one to open it, and to keep it up to date from there.
Pages: reports and overviews your bots keep for you
Ask a bot for a page, a report or an overview: it saves it as a page, with a chip under its reply that opens it.
Each bot's pages are listed in its settings, with when they were last updated.
Tap Keep up to date on a page and pick how often: the bot rewrites it on that schedule, with no card to approve.
It stays quiet unless something needs you, or tells you every time if you choose so.
Open a report as a document
A long reply, with sections or a table, has "Open as document" under it.
It opens in a tab of its own, full width, with its sections beside it.
Export it as Word, PDF or Markdown, copy its text or print it.
A Markdown file in the viewer opens the same way.
Answer the Chief's own messages with one tap
When the Chief of Staff writes first and offers something, its message can end with answer buttons, such as Yes and Not now.
A tap answers it as if you had typed it; 👍 and 👎 stay under the message.
A bot's offer to check later needs only your yes
When a bot offers to look again later and you tap Yes, the check is set up at once.
No second card in Needs you for it: it runs once, at the time the bot said.
Repeating jobs, scripts and checks more than a week ahead still wait for your OK.
Bots offer the next step
When an answer has a date or a deadline, a bot says what to do and when, and offers to take that one step for you.
Tap Yes and it does it; tap No and it doesn't offer that again in the chat.
Bots check what they can in your connected apps before they answer.
A bot can set a reminder: at that time a ⏰ message shows in its chat, with a notification.
Ask a working bot a quick side question with /btw
Start a message to a bot that is working with /btw, for example "/btw how far are you?".
It answers in seconds from what it is doing, without stopping or slowing the work.
It can't look anything up for that answer: send a normal message for real work.
To a bot that is not working, /btw is an ordinary message.
Notifications from shared rooms
A new message in a shared room rings you, on the web page and in the Android app: who wrote it, in the room's name, and the start of the text.
What you write yourself rings nothing, and the web page rings nothing while you use it.
Tap the notification to open the room.
A busy bot answers at once
A message to a bot that is working no longer waits: the bot starts on it right away, beside what it is doing.
The same for a teammate's request, so a bot that asks another for help is not held up.
Up to three at once per bot; a fourth message waits as before. Scheduled jobs still wait until the bot is free.
Questions come back to the chat you asked in
When a bot asks a teammate and the teammate needs your OK, the question now shows in the chat where you asked, not in the teammate's chat.
Your answer goes back to the teammate, which carries on with its work.
Bots stop asking about full memory
A bot no longer tells you its pinned notes are full or asks which one to drop: everything is saved and found when it matters.
Bots keep more in mind on every task: up to 15,000 characters of pinned notes, and up to 10 files.
When the files a bot keeps in mind are full, it saves facts in its memory instead of asking you.
Times on the Board stay current
A tile that says "5 minutes ago" now moves on by itself, also in the Board line above your bots.
Coming back to the app shows the current times straight away.
See what a waiting update brings
When a new version waits for your account, Settings → Updates lists its What's new under "Update now".
"Update automatically" now says in two lines what On and Off do.
Settings and group settings drop a few hints that only repeated what the screen already says.
See how many tokens your bots used
Settings has a new Usage section: pick Today, 7 days, 30 days or your own days.
It shows input, output and cache tokens as Claude Code reports them, per bot and per day.
The Chief of Staff has its own row, and a group's turn counts for the bot that took it.
Counting starts with this update.
A bot knows what you decided in its groups
When a bot asked a teammate for something and starts again with the answer, it now sees what you wrote meanwhile in its groups.
It no longer asks you again in its own chat about something you already decided in a group.
Every file in a bot's folder
A bot's settings have a Workspace next to Files: every file in its folder, not only what you gave it.
Open a file in the viewer or download it, upload into a folder, make folders, rename, move and delete.
What botdot keeps there to run the bot is shown read-only, and a delete always says first what goes.
For a bot that uses the computer, its folder there opens too while the computer is on.
Activity shows the work in groups
Settings → Activity now lists a bot's turns in a group too, live and past, with the group's name.
The count of running tasks beside Activity includes them.
Questions in a job's report show their buttons
When a scheduled job asks you something in its report, you now get the answer buttons or the card of questions.
Before, the choices line showed as plain text at the end of the message.
Copy a code block in one tap
Every code block in a chat has a Copy button in its top-right corner, on the web page and in the Android app.
It copies the code exactly as written, ready to paste into a terminal or a file.
A diagram has one too: it copies the diagram's source.
Notes are saved without asking you
A bot adds and changes notes, the shared ones and what you said too, without a card in Needs you.
A line under its reply says what it saved or changed, marked when it came after outside content.
Removing a shared note or what you said, and forgetting, still ask.
See the plan of longer work
When a bot or the Chief works through several steps, its plan shows above the message box, with each step done, at work or still to do.
Tap the plan to fold it to one line, or open it again. Each chat remembers your choice.
Once the work is done, the plan folds under the reply. If it was stopped, it says at which step, until you dismiss it.
Pinned groups go anywhere
Drag a pinned group above a pinned bot, or a bot below a group, in the list or on the keypad.
The keys 1 to 9 follow your new order.
The order is the same on the web page and in the Android app.
One card for everything a bot asks in one task
When a bot, or the Chief in one chat, asks for several things at once, Needs you shows them on one card.
"Allow all" and "Decline all" answer every item; each item keeps its own buttons too.
A Vault secret still needs its own Allow on its own item.
Your phone rings once for the card, not once per item.
Fewer permission cards
A tool a bot's settings don't allow no longer puts a card in Needs you by itself.
A bot asks for a permission only when its task needs one, with its reason on the card.
After your yes it still carries on with the work that waited.
Fewer cards: "Always allow" on more of them
After the Chief read the web, a card for a reminder, your Board, quiet hours or how often it writes first has "Always allow".
Ask the Chief to take it back.
The admin's own account chooses when it updates too
Settings → Updates now shows "Update automatically" and "Update now" on the admin's own account.
Turn it off, and "Update every account" leaves your own bots on the version they run until you choose, up to the deadline.
The admin page's card of your own account says what waits for it and has "Update now".
No more number on Settings
The Settings button no longer shows a number for the tasks your bots are running.
Settings shows them beside Activity instead, kept up to date while the page is open.
The files you send open everywhere
A file you attach in a Chief chat or a group now opens when you tap it, as a bot's file does.
Text, Markdown and tables open in the viewer; a PDF or a zip downloads.
It works for a message that still waits its turn too.
Choose when your account moves to a new version
Settings has Updates: turn off "Update automatically" and your bots keep working when the admin updates botdot.
When a new version is ready, Settings says so: tap "Update now" whenever it suits you.
If you wait, your account moves by itself after the admin's deadline, a week unless the admin set another.
The admin page shows which accounts wait, and the admin sets the deadline there.
Struck-through text and checklists in replies
Text a bot writes between two pairs of tildes is now drawn struck through, without the tildes.
A list item that starts with [x] or [ ] shows a ticked or empty checkbox instead of the brackets.
It works in chats and in Markdown files opened in the viewer, on the web page and in the Android app.
Needs you takes you back to your chat
After you answer the last card on Needs you, the app goes back to the chat you came from by itself.
Your answer stays on screen for a moment first, so you can read it.
Opened from the Board, it goes back to the Board. Opened with nothing waiting, it stays.
Bots in a group hand work on by themselves
When the next step is another member's work, a bot names that member and hands it on, without asking you first.
A choice or an OK that is yours still comes to you as a question.
You can lift a bot's rule for one thing
When one of a bot's own rules stops what you asked, it asks you on a card instead of refusing.
Choose "Allow once", or "Allow always for this bot" to let it do exactly that from now on.
The bot's settings list the rules you lifted, and you can revoke each one.
Bots keep the skills they learn
A bot now saves a skill it wrote right away: no more "Wants to keep a skill it wrote" card in Needs you.
A short line under its reply says "Saved the skill …"; tap it to see the skill in the bot's settings.
You can still edit or delete any skill there.
A bot can keep a saved secret in a file
When a program needs a secret in a config or env file (Traefik, a systemd unit), the bot asks you on a card, and botdot writes the file. The bot never sees the secret.
The card says who can read the file: every bot on the account's computer, or anyone on that server.
The Vault shows where each secret is kept, with "Remove the file".
Any file in the Vault
"Add a file" in the Vault now takes any file, not only a .pem key: a .conf, a .env, a certificate, a file with no extension.
It can still be at most 64 KB, and bots still use it in one command without seeing what is in it.
Screenshots in Feedback
The Feedback form beside Settings has "Add screenshot": add up to three pictures (PNG, JPEG or WebP, at most 5 MB each) to a bug report or a feature request.
Each one shows as a small preview you can remove before sending.
The admin of your machine sees each screenshot whole, as it is, next to your text.
A bot asked by a teammate asks you properly
When one bot asks another to do something that needs your OK, the second bot now asks you with answer buttons or a card of questions.
That bot shows "Asks" in the list and you get a notification, as with any other question.
Your answer starts the bot again on the task, with your word.
A working bot says what its command is for
While a bot runs a command, its line under the chat says what the command does, such as "Check disk space", instead of only "Running a command".
On its computer the line says "Looking at its screen", "Clicking", "Typing" and the like.
The command itself, a password or what was typed never shows in the line.
Bots can use several saved logins at once
A bot can now use up to 8 saved logins in one command or one API call, for services that need several keys together, such as OVH's API.
Each login still needs to be shared with the bot, and in a command each needs "Usable in its computer", which the bot asks you for one login at a time.
A note to a bot now starts it
A note one bot leaves another starts that bot as soon as it is free, so it acts on it without waiting for its next run.
"Notes waiting" in a bot's chat says how long the oldest note has waited, and "Run now" starts the bot with its notes.
Open files without downloading them
Files from bots, files you attach and file paths a bot names in its reply now open in a viewer next to the chat, or full screen on Android.
Markdown is formatted, a CSV is a table you can sort and search, and images and other text show as they are.
A file on a bot's computer opens while the computer is on; the viewer offers to start it.
Times on the Board keep counting
A tile that says how long ago something happened now moves on by itself: "9 hours ago" becomes "10 hours ago" without its bot writing again.
After a week it shows the date instead, such as "12 Oct".
Ask the Chief to switch an older tile that shows a fixed "… ago" to the new kind.
Run a bot's skill by typing /
In a bot's chat, type / at the start of the message to see that bot's skills, your Claude account's included, with what each one is for.
Pick one, or keep typing its name, then write what it should work on: /weekly-report for May.
The bot runs that skill on the rest of your message. A name it has no skill of is sent as an ordinary message.
A bot remembers the files you gave it
Every task of a bot now lists the files you gave it, and it can always read them, even without the Read permission.
"Keep in mind" a file (a CV, a price list): its text, or the bot's own summary of it, comes with every task.
Bot settings have a Files section: open, keep in mind or delete each file. You can also tell the bot, or ask the Chief.
Skills from your Claude account reach your bots
A skill from your Claude account that is ticked in a bot's settings now works in its runs; before, the bot could not find it.
Each skill shows once in a bot's settings, even when your Claude account keeps two copies of it.
Duplicate a bot
"Duplicate" in a bot's settings makes a second bot with the same settings, such as Coder 2, to work in parallel.
The copy gets its main assignment, rules, tools, skills, connected apps and the Vault entries it may use. You see the list before it is made.
Its memory, chats, jobs and groups are not copied. You can also ask the Chief for a copy.
What's new after an update
After botdot is updated, a short note like this one says what changed.
It shows once: closed on the web page, it doesn't show in the Android app, and the reverse.
A bot can use helpers
A new switch in a bot's settings, "Can use helpers", lets it split big work into parts that helpers do at the same time, within one run.
For code, each helper works on its own branch, and the bot merges them before it replies.
Off by default. A bot that needs helpers asks you on a card in Needs you.