v0.6.0

0.6.0 - 2026-10-05

Highlights

tail --follow streams again. v0.5.0 shipped a regression: with no --filter-regex, the filter compiled to a match-nothing pattern, so --follow printed nothing at all. If you adopted --follow on 0.5.0 it has been silently doing nothing. An invalid --filter-regex now reports the error instead of streaming your whole unfiltered log.

Live lines also carry real line numbers now. They used to print as 0 |, because the writer broadcast each line before it had a position. tail --follow on a piped or PTY job now numbers continuously, and restarts at 1 after a log rotation.

expect answers questions about the past. It scanned from the end of the log, so it only ever matched output written after the call. Asking whether an error had already happened always timed out. It now searches the whole log first, then keeps watching for new lines.

bgrun expect api "error" --timeout 5s   # finds an error already logged

MCP server. bgrun mcp speaks JSON-RPC 2.0 over stdio and exposes 15 commands as tools for agent clients.

printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' | bgrun mcp

Added

• Add bgrun mcp, a stateless stdio MCP server exposing 15 daemon commands as tools

Fixed

• Fix tail --follow printing nothing when no --filter-regex was given (regression in 0.5.0)
• Fix tail --follow --filter-regex <invalid> silently streaming the whole unfiltered log
• Fix tail --follow printing 0 as the line number for live lines
• Fix expect timing out on a pattern that was already in the log
• Fix diff line numbers collapsing after a log rotation

Changed

• Add last_diff_lines to bgrun status --json output

MCP requests are handled one at a time, so a long wait blocks later calls. Poll diff when you need to interleave.

Full Changelog: v0.5.0...v0.6.0