-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[Bug]: "-t TASK" doesn't work with CLI mode #5719
Comments
@enyst sorry for the ping. Do you know the answer to this? |
Ah, I'm not sure Indeed there's another way, personally I use it via I think there was another bit somewhere (about IDE configurations) which covers more parameters... aha, it's for Please note that
Significant differences:
|
I just posted and realized what happened: |
Hi @enyst. Using 0.19.0 (which appears to have this fix), I'm still seeing the same prior behavior where "-t" doesn't appear to take effect:
I'm left with an empty prompt, and the foo.txt file was never created. The behavior that I'm expecting is that "-t" sets the first message to the agent, and then I get the interactive prompt for a followup conversation. |
Oops, I did intend to catch this last time! I think, I keep using |
No worries and thanks for re-opening the issue. |
Is there an existing issue for the same bug?
Describe the bug and reproduction steps
I'm writing some tooling around Openhands to make it work well in our monorepo, and I would like to start the CLI session with some company specific prompts. I tried using "-t TASK" but this appears to be ignored, even though it's printed in the usage. Is this a bug, or is there another way to start openhands w/ a prompt but then have it fall back into interactive CLI mode?
cli.py usage says:
Thanks for your help!
OpenHands Installation
Docker command in README
OpenHands Version
0.16.1
Operating System
MacOS
Logs, Errors, Screenshots, and Additional Context
No response
The text was updated successfully, but these errors were encountered: