Skip to content

Conversation

@trobrock
Copy link
Contributor

Summary

From #5956 there were a couple spots that were missed and don't use the new configuration preventing this from working properly.

Type of Change

  • Feature
  • Bug fix
  • Refactor / Code quality
  • Performance improvement
  • Documentation
  • Tests
  • Security fix
  • Build / Release
  • Other (specify below)

AI Assistance

  • This PR was created or reviewed with AI assistance

Testing

Manual testing locally

Related Issues

Relates to #5956
Discussion: LINK (if any)

Screenshots/Demos (for UX changes)

Before:

After:

Copilot AI review requested due to automatic review settings January 30, 2026 22:23
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a bug from PR #5956 where two locations continued to hardcode the 'j' key for newline entry instead of using the new configurable GOOSE_CLI_NEWLINE_KEY environment variable.

Changes:

  • Updates the key binding setup in input.rs to use get_newline_key() instead of hardcoded 'j'
  • Updates the user hint in completion.rs to dynamically display the configured newline key

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
crates/goose-cli/src/session/input.rs Updates the rustyline key binding to use the configurable newline key instead of hardcoded 'j'
crates/goose-cli/src/session/completion.rs Updates the hint message to display the actual configured newline key (e.g., "Ctrl-N") instead of always showing "Ctrl-J"

@zanesq zanesq merged commit f76a359 into block:main Jan 30, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants