feat(aliases): add oclog for live opencode log tailing#41
Merged
Conversation
Surfaced during AI-011-validation (2026-05-17): the opencode TUI shows
"thinking..." for tens of seconds without indication of whether the model
is streaming, hung, or waiting on a tool call. The fastest way to know is
to tail the most recent log file in a parallel Ghostty split/tab.
Adds the alias to `.zsh/aliases.zsh` next to `oc` so it deploys via
setup-linux.sh on every shell:
alias oclog='tail -F "$(ls -t ~/.local/share/opencode/log/*.log | head -1)" \
| grep --line-buffered -vE "file\.watcher\.updated|bus type=message\.part\.delta"'
The filter strips two extremely chatty event types so the signal/noise
stays workable:
- file.watcher.updated -- inotify events, dozens per second in active repos
- bus type=message.part.delta -- per-token publish events during streams
Useful signals you DO see after filtering: service=llm ... stream (request
sent), service=tool.registry started/completed (tool execution), ERROR
lines, snapshot timings. Runbook 40-runbooks/guide-opencode-go-setup.md
already documents the pattern under "Live log tailing"; this PR is the
package-and-deploy side of that workflow.
Test: tests/aliases.bats line ~37, asserts the alias is present and
points at the right log path. 24/24 bats green locally.
This was referenced May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Surfaced during AI-011-validation (2026-05-17). The opencode TUI shows "thinking..." for tens of seconds with no indication whether the model is streaming, hung mid-tool-call, or waiting on a congested upstream provider. The fastest way to know is to tail the newest log file in a parallel Ghostty split/tab.
Adds the alias to
.zsh/aliases.zshnext toocso it deploys viasetup-linux.shon every shell.The filter strips two very chatty event types so signal/noise stays workable:
file.watcher.updated— inotify events, dozens per second on any active repobus type=message.part.delta— per-token publish events during streamingUseful signals you DO see after filtering:
service=llm ... stream(request sent),service=tool.registry started/completed(tool execution),ERRORlines, snapshot timings.Workflow
Open Ghostty,
Ctrl+Shift+Eto split, in one paneoc, in the otheroclog. Documented under "Live log tailing" in the runbook40-runbooks/guide-opencode-go-setup.md.Test plan
bats tests/aliases.bats— 24/24 green (new test feat(tmux): focus-events, vi visual-mode bindings, slower status refresh #8 asserts oclog present and points at opencode/log path)bash -n .zsh/aliases.zsh+zsh -n .zsh/aliases.zshclean.zshrcafter merge, runoclogin a split whileocruns in another — confirm filtered live log streamsCross-links
~/Projects/knowledge/10_projects/dotfiles/40-runbooks/guide-opencode-go-setup.mdsection "Live log tailing"