Repository navigation
Meru v0.7.3
Release v0.7.3 - Secrets stay out of the log, spans and server errors
November 2026
Meru promised to hide every key from secrets.toml before it writes a log line or a span. Until now it did that only in transcripts and the tool_calls log. If an MCP server echoed a key back in an error, the key landed in merud.log, in any span you export, and in Settings. Now every one of those shows [secret:<name>] instead.
Upgrading from v0.7.2
Breaking changes
There are no breaking changes in this release. The config, the socket protocol, the transcripts and meru.db don't change.
New config keys
None.
Upgrade instructions
The one-line installer on a Mac. Run it again; it keeps your config.toml:
curl -fsSL https://github.com/aarora79/meru/releases/latest/download/install.sh | bashThe Mac installer. Download the disk image,
open it, and run "Install Meru.app". It leaves your config and memories alone.
Linux. Run install-linux.sh again; it keeps your config.toml:
curl -fsSL https://github.com/aarora79/meru/releases/latest/download/install-linux.sh | bashFrom source.
cd meru
git pull origin main
git checkout v0.7.3
go install ./cmd/merud ./cmd/meru
launchctl kickstart -k gui/$(id -u)/com.meru.merud # Linux: systemctl --user restart merudThen, on a Mac that reads Apple Notes: macOS drops the Full Disk Access grant
when the merud binary changes. In System Settings, open Privacy & Security,
Full Disk Access, and turn merud off and on again.
An older merud.log may still hold a key a server echoed back before this
release. To check, search the file for each value in secrets.toml. If you find
one, delete the log while merud is stopped, and change that key at its service.
Security fixes
- Secrets in the log, spans and server errors. One redactor now hides each stored secret of 8 or more characters in four places. It takes the new secret set each time
merudloadssecrets.toml, so a key you save in Settings is hidden from the next line on. (#239)dispatchbefore a transcript line or atool_callsrow, as before.- Every line of
merud.log: its message, its fields, and the text of any error. - Every span before it leaves
merud: its attributes, its events, which hold a recorded error's message, and its status. - Each MCP server's last error, before
meru mcp status,meru chatand Settings show it.
Closed issues
| Issue | Title | Closed by |
|---|---|---|
| #238 | Redact secrets in merud.log, spans and server errors, as the docs promise | PR #239 |
Pull requests included
| PR | Title |
|---|---|
| #239 | Redact secrets in merud.log, spans and server errors |
Contributors
- Amit Arora (@aarora79)
Full changelog: v0.7.2...v0.7.3