Release v0.4.0 · waibee-main/waibee-code

MultiEdit is gone: Edit takes several changes to one file in one call. A
permission rule or a skill's allowed-tools naming MultiEdit no longer matches
anything.
The Brave API key setting is gone. A key still in your settings file is ignored,
and web search works without it.
--mode is now refused where it used to be accepted and ignored, so
waibee --mode … <subcommand> exits instead of running.
waibee run --json reports one origin on a user message in place of the
steered, injected and synthetic flags.

Long jobs take fewer steps. Independent tool calls go out together, several
changes to one file go in one edit, and changes to several files go out at once.
Less of a file you did not ask about lands in the conversation: waibee searches
before reading a long file whole, and goes straight to the line it found.
waibee checks which interpreters are on your PATH at the start, so it stops
trying python on a machine that has only python3.

A dropped connection no longer costs you the answer: a reply cut off partway is
carried on from where it stopped instead of arriving empty or twice.
A long chat no longer breaks when it fills up. waibee shortens it and carries on,
including on a chat you came back to and while it is working, and the gauge shows
what is left.
A run that cannot finish hands back what it has: waibee spends its last turn
writing up what it found and where it stopped.
A reply blocked by the provider's content filter says so, instead of looking like
the model went quiet.
An edit with a quoting mistake comes back pointing at the exact spot, and a failed
edit no longer drags the next ones down with it.
The closing summary says what changed, what was checked and how, and anything left
open, without replaying the steps.

waibee no longer asks permission to look. ls, cat, grep, git status and
the like run straight away in every mode.
What waibee asks about is judged by what a command does, not how it is typed.
Spelling out a program's full path no longer skips the question, and a file in
your project named after a common command is not that command.
waibee leaves your unfinished work alone: files you changed and never committed
are never reverted, stashed or cleaned up.

Web search needs no key and no setup. waibee can search several things at once,
and the pages it used are listed under the answer: in the browser with each site's
icon, in the terminal as a numbered list. The Brave API key and its setup step are
gone.

A quieter screen: one accent colour, one rule above the input, and overlays that
share one frame and size themselves to what they hold.
The approval screens read properly again. Whole changed words are highlighted
instead of scattered letters, and nothing pops up over a question you owe an
answer to.
Ctrl+B sends every running helper to the background at once, so waibee carries
on while they finish.
Ctrl+Y walks the side panel and then hides it (it used to be Alt+Y, which a
Mac cannot type). /memory, /export and /new open while waibee is working.
A screenshot pasted while waibee is working goes with the message you queued. It
used to be dropped without a word.
Coming back to a chat brings its helpers back with it.
A file name in a tool card opens in your editor wherever the file lives.
Allowed and blocked hosts in /settings are a list: type one, Enter adds it, the
arrow keys pick one and Backspace removes it.

A chat opened on one project now uses that project's own skills, hooks and
permissions. It was using the setup of the folder the server was started in, so
every skill it offered came back "not found" and another project's hooks ran. The
same applies to a chat opened from an editor.
Answers no longer break apart while they are written: tables came out as rows of
bars, and words split down the middle.
Helpers behave: each shows its own model and running time, a card shows two lines
of what it found rather than the whole thing, and stopping one stops it on screen.
A queued message appears the moment you send it, opens for editing on click, and
goes away with the cross beside it.
Links an answer mentions are gathered under it, each with the site's icon.
Restarting the server no longer leaves a tool spinning for ever: work that died
with the old process is shown as interrupted.
A link shared as "watch only" can no longer make the server fetch anything from
the network on its behalf.

A new model appears without restarting waibee, and one your account no longer has
disappears the same way. /doctor says how old the list is.
An image a tool hands back reaches every model that reads images.

waibee remembers less, and less of the same thing: a correction replaces what it
corrects, and a full memory is tidied before anything is dropped. What it keeps is
what you insisted on, corrected, or said about how you want work done here.
/memory add <fact>, or add user for something about you; the browser's Memory
page has the same field.
A memory file you edited by hand keeps every line you wrote.

An error from the provider could carry your API key into the log file. It cannot
now, and the rules your organisation sets for what to hide are honoured.
Private mode leaves no trace in the log, and waibee audit status reports the
real state.
More is recorded: background commands, notebook edits, goals that ended on their
own, and setting changes (which setting, never its value).

A server whose MCP sign-in has expired says so in one line at startup.
A rule in a file next to the code outranks one at the root of the repository, and
anything you say outranks both.

Navigation Menu