Bake 0.4.6

Bake 0.4.6 starts new sessions with full access, as Pi does, adds /permission and more answers to an approval, draws Mermaid diagrams in answers, adds an opt-in visualize tool for charts, tables, and diagrams drawn while the model writes them, and gives the status line a state dot, a context gauge, and one palette. Linux remains its only released platform.

• New sessions have full access, as in Pi. A new session now starts with the danger-full-access preset: tools change any file you can, bash runs outside the sandbox, and nothing asks. Sessions you resume keep the permission they had. To keep the sandbox, set "permission": { "defaultPreset": "workspace-write" } in settings.json or run bake --permission workspace-write; a defaultPreset already saved, from settings.json or a 0.3 home, still applies. Under never, a Claude Code hook's ask is denied without asking; choose workspace-write to be asked.
• /permission switches the session. /permission lists the presets with their sandbox and approval policy and switches this session; Ctrl+S also saves the default for new sessions, and /permission workspace-write switches at once. The session file keeps the switch, and the next prompt tells the model.
• More answers to an approval. The approval panel says what the tool wants in words, such as bash wants to run outside the sandbox, shows the command or path first with the model's justification under it, and offers four choices, picked with ↑↓ or a key and confirmed with Enter: allow once (y), allow the same tool the same access for the rest of the session (a), switch the session to full access (f), or deny (n) with an optional note that the model reads with the refusal. Esc still cancels. A session grant is kept in the session file, so a resumed session does not ask again.
• A status line that shows the session's state at a glance. A dot leads the screen's last row: ○ idle, an orange ● while a turn or compaction runs, a yellow ◆ while Bake waits on you for an approval or a model, and a red ! after a failed turn, until the next prompt. A five-cell gauge before the context's share fills green and turns yellow, orange, and red as the context nears its limit; the prompt cache's share, when shown, is green when most of the prompt came from the cache and warms as less did; and a detached branch is yellow. The model name is in the terminal's normal colour and the rest stays dim. The colours come from one small palette: warm colours mean attention, and the thinking levels moved to cool ones, so xhigh is now violet rather than orange. Under NO_COLOR each state keeps its own glyph.
• Text copied from the transcript no longer carries an invisible byte-order mark (U+FEFF) from the output it was copied from, such as a CI log; it pasted as a stray character.
• Mermaid diagrams in answers. As in Pi 1.5, a ```mermaid code block in an answer is drawn as a diagram in box-drawing characters: flowcharts, sequence diagrams, and flat state, class, and entity-relationship diagrams, in the answer's colours, and in ASCII under the classic frame. A diagram too wide for the screen, or one using Mermaid that Bake cannot draw, shows its source as before, with a dim line saying why. While an answer streams, a diagram is drawn as far as its finished lines go. markdown.mermaid in settings.json, also under /settings, takes Pi's values: streaming (the default), final to draw a diagram once its code block is complete, or off. The model sees no change. The renderer is a port of OpenAI Codex's codex-mermaid (Apache-2.0).
• Charts, tables, and diagrams in the conversation, off by default. The new visualize tool lets the model show you a bar chart, a line chart, a table, or a Mermaid diagram, drawn as text while the model is still writing it: bars in eighth-of-a-cell steps ending in their values, a braille line plot ten rows high with its axis and labels, tables in box-drawing borders with numbers aligned right, and diagrams as an answer's Mermaid code block draws them, from the longest run of finished lines while they arrive. Several series get colours and a legend; with NO_COLOR they are told apart by glyph, and the classic frame draws in ASCII. The drawing reflows when the window is resized and is drawn again when a session is resumed. A diagram is drawn whatever markdown.mermaid says, since the model asked to show it. The model gets back one line saying what you were shown, never the drawing, and a call with a mistake, such as a row with the wrong number of values or Mermaid Bake cannot draw, fails with what to fix, naming the diagram's line or the limit it passes. Turn it on with bake -t +visualize or "defaultTools": ["+visualize"] (bake docs cli); it stays off by default until its effect on models has been measured.