Skip to content

feat: Add ability to view specific history by ID or path#7

Closed
insign wants to merge 1 commit intomainfrom
feat-history-view-id-4279561644893330610
Closed

feat: Add ability to view specific history by ID or path#7
insign wants to merge 1 commit intomainfrom
feat-history-view-id-4279561644893330610

Conversation

@insign
Copy link
Copy Markdown
Contributor

@insign insign commented Feb 26, 2026

This PR adds the ability to view detailed history for a specific context using the ask history command.

Previously, ask history only listed all available contexts. Now, users can provide an argument to view the messages within a specific context.

Supported arguments:

  • Partial ID: e.g., ask history f53b (matches context ID starting with f53b)
  • Exact Path: e.g., ask history /path/to/project
  • Current Directory: ask history . (resolves to the current working directory)

If multiple contexts match a partial ID, the command lists the matches and asks for more specificity. If no match is found, an error message is displayed.

Technical changes:

  • Refactored src/context/manager.rs to reuse printing logic (print_entry) between show_history (current context) and view_history (any context).
  • Updated src/cli/mod.rs to dispatch to view_history when args.history_subcommand is true and args.query is not empty.

PR created automatically by Jules for task 4279561644893330610 started by @insign

- Refactor `ContextManager::show_history` to extract printing logic
- Implement `ContextManager::view_history` to search and display contexts
- Update CLI handler to call `view_history` when `ask history` has arguments
- Supports partial ID matching, exact path matching, and `.` for current directory
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@insign insign closed this Mar 19, 2026
@insign insign deleted the feat-history-view-id-4279561644893330610 branch March 19, 2026 05:37
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.

1 participant