Repository navigation
Releases
v1.5.1
v1.5.0
What's Changed
- feat: TUI parity, port offsets, MCP, init --from, Homebrew and more by @maborak in #13
- docs(changelog): release 1.5.0 by @maborak in #15
Full Changelog: v1.4.1...v1.5.0
v1.4.1
What's Changed
Full Changelog: v1.4.0...v1.4.1
v1.4.0
Added
- Explicit remote-terminal permission with
serve --terminal --i-know-allow-remote-terminal-is-dangerous. Non-loopback
binds also require--i-know-this-is-dangerous; HTTPS tunnels additionally
require their public origin in--allow-origin. - A live connection indicator showing status-response latency, received
application payload rate, reply freshness, and slow/disconnected states. - A close control for the service-output panel below the terminal. Selecting a
service in the sidebar reopens the panel without closing any shell. - An editable same-origin API base URL, defaulting to the browser's origin so
the playground works through HTTPS tunnels.
Changed
- A non-loopback console keeps running with the Terminal box disabled when
remote-terminal permission is missing, rather than refusing to start. - Token/Copy lives in Config; theme selection and expandable keyboard help
occupy a compact sidebar footer. - API authentication failures return concise JSON
{"error":"invalid_api_key"}. Role denials return{"error":"forbidden"};
HTTP status codes remain unchanged. - Log separators mark recognizable multiline entries rather than every
physical line. Python tracebacks, chained exceptions and indented
continuations stay together; separate JSON records remain separate. Raw
logs, line counts and severity filtering are unchanged. Plain-text grouping
is best effort because the stream does not preserve logging-call boundaries.
Fixed
- Remote-terminal permission now admits explicitly trusted HTTPS tunnels while
retaining Host/Origin checks and operator-only access. - The API playground initializes one editable header-key control from the UI
session, avoiding duplicate token headers. Clearing or replacing the key
sticks, and theme changes no longer reload the API frame or discard edits. - API frames use the UI page's explicit credential instead of an ambient cookie
that another browser tab may have replaced with a different access role. - VIEW/mirror guests cannot override presenter scrolling with wheel, touch,
keyboard or scrollbar input. READ/WRITE guests still browse independently. - Following a log before its first creation no longer drops startup output.
Backlog replay and live following now share one file handle and an exact
consumed offset, preserving concurrent writes and incomplete final lines.
Security
- Terminals remain loopback-only by default and unavailable to every shared-link
role. Neither YAML terminal settings nor dangerous-bind or trusted-origin
settings alone authorize remote shells. Proxy headers never establish trust. - API base-URL edits remain same-origin; the playground never forwards the
current session key to another origin or persists it to local storage.
Upgrading
- Rebuild or install the release, restart
serve, and reload browser tabs.
Finish terminal work first: restarting closes shell sessions and invalidates
shared links, while managed services keep running. - OpenAPI uses one
tokenHeadersecurity scheme for reads and mutations. Clients
configured with the formersessionHeaderscheme name should use
tokenHeader; theX-Mabo-Ctl-TokenHTTP header is unchanged. - API clients parsing authentication errors should expect the JSON bodies above
instead of the previous plain-text login instructions.
Full Changelog: v1.3.0...v1.4.0
Merged in #12
v1.3.0
Web console
- Tabbed workspace, Monaco fonts, organized CONFIG sections and resizable sidebar.
- Opt-in interactive terminals with multiple sessions and a compact service-output dock.
- READ ONLY, VIEW and WRITE sharing links, guest monitoring, token rotation and revocation. VIEW mirrors navigation and visual cursor/click indicators; WRITE permits service lifecycle controls only.
- Configuration change detection and confirmed reloads.
- Recovery after sleep or network interruptions; fixes for duplicate output, stale controls and terminal sizing.
Security
Guest access is restricted server-side. Guests cannot use terminals or administer configuration, origins, tokens or shares. Terminals remain opt-in and loopback-only. Builds use Go 1.26.10 for standard-library security fixes.
Upgrade
Install the release, restart serve, then reload browser tabs. Restarting serve closes web terminal sessions and invalidates shared links; finish terminal work first. Managed services keep running. Shares, visitor records and CONFIG token changes are runtime-only.
See CHANGELOG.md for details.
v1.2.3
What's Changed
Full Changelog: v1.2.2...v1.2.3
v1.2.2
v1.2.1
v1.2.0
Highlights
- RapiDoc API reference —
/api-docsnow renders via a ~860KB vendored RapiDoc bundle (down from 3.7MB Scalar), still loopback-bound, session-token-gated, no CDN. The bundle route moved from/api-docs/scalar.jsto/api-docs/rapidoc.js. console_addrin mabo-ctl.yaml —mabo-ctl servebinds this address when no--addris given (default127.0.0.1:7999). An explicit--addrstill wins.- Free-port fallback — with no
--addr/console_addr, a taken default port now falls back to a kernel-chosen free port and prints the real address instead of failing.
Plus the pre-release wave now shipped: GET /health, GET /api-docs + /api/openapi.yaml, docs/API.md, tty: true attach, preflight machine-readiness, expect: free|listening tcp checks, logs --timestamps, surface drift gate, tcp/exec probes, open:, --port svc=n, full --version provenance, mabo-ctl init, --notify, schema --commands, doctor, JSON Schema, fish/powershell completions, per-service ready_timeout, env_file:, trusted origins, and the web console.
Full detail: CHANGELOG.md.
Full Changelog: https://github.com/maborak/mabo-ctl/commits/v1.2.0