Skip to content

clai: Add ability to continue last conversation #2257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

uriyyo
Copy link

@uriyyo uriyyo commented Jul 19, 2025

Hi,

Thanks for clai, I'm using it all the time 🙌

One minor feature that I miss is the ability to continue the last conversation, cause my usage looks like this:

clai "first question"
clai "next question that basically related to first one"

So now it will be possible:

clai "first question"
clai -c "next question that basically related to first one"

I'm not sure if -c is a good option name, as it is usually used for configuration, so maybe -r/--resume would be a better option. I will be happy to update the implementation with better naming.

Copy link
Contributor

hyperlint-ai bot commented Jul 19, 2025

PR Change Summary

Added the ability to continue the last conversation in the clai CLI tool.

  • Introduced the '-c' option to continue the last conversation instead of starting a new one.
  • Updated usage instructions in the README to reflect the new option.
  • Provided a suggestion for renaming the option to '-r/--resume' for clarity.

Modified Files

  • clai/README.md

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

@uriyyo
Copy link
Author

uriyyo commented Jul 20, 2025

I don't know why coverage is not 100%(

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