You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat(output_window): add jump-to-user-message action with [u/]u keymap
Add navigation.goto_next_user_message / goto_prev_user_message and the
underlying renderer.get_next_user_message / get_prev_user_message, which
filter state.messages by role == 'user' so the cursor only lands on
user turns (not the assistant response between them).
Wire them through workflow (action + command_def), expose them in
opencode.api, and bind [u / ]u in the default output_window keymap next
to the existing ]] / [[ section-movement pair.
Tests cover role filtering, jump behavior, and the no-target notify case
in tests/unit/navigation_user_message_spec.lua.
* fix(navigation): load all messages before user-message jump under lazy render
Under lazy render only the most recent N messages have a line_start in
render_state, so goto_prev/next_user_message would silently no-op when
the target user message had not yet been rendered, falling through to
the 'No previous/next user message' notify.
Mirror the 'gg' binding in output_window.setup_keymaps and force a
full render via renderer.load_all_messages() before resolving the
target. Three new tests cover the lazy render interaction.
0 commit comments