I want to delete last few events from the conversa...
# questions
l
I want to delete last few events from the conversation history in software agent sdk. Is it enough to remove those events from .conversation/conv_id/events/ directory?
m
A priori yes but you can have problems if you are using a condenser
Which version are you using?
l
1.14.0 for openhands-sdk and openhands-tools. I do use condenser a lot.
m
Perhaps update the version. We are at 1.31 now
And in the last version you can also fork the conversation
l
I removed the events from .conversation directory. It is working in 1.14.0 version. By the way, I use uv for package management. Looks like pypi and uv versions are far behind github release cycle.
m
@nutritious-balloon-65098 can you look if the above mag is true? If it is the case open an issue in software-agent-sdk
n
I'm on it! Vasco can track my progress here.
It doesn’t look true (at least when comparing GitHub Releases vs PyPI): • GitHub latest release for `OpenHands/software-agent-sdk`: v1.31.0 (published 2026-07-02T18:58Z) • PyPI latest: ◦ `openhands-sdk`: 1.31.0 (uploaded 2026-07-02T185827Z) ◦ `openhands-tools`: 1.31.0 (uploaded 2026-07-02T185828Z) So PyPI is essentially in sync with the GitHub release tag (minutes apart), and tools like
uv
should be able to resolve 1.31.0 from PyPI. If someone is “stuck” on 1.14.0, likely causes are local/project constraints rather than PyPI lag, e.g.: • pinned versions in
pyproject.toml
• an existing
uv.lock
that pins 1.14.0 • using
uv sync --frozen
•
uv
exclude-newer
/ a date cutoff • using a corporate PyPI mirror that syncs slowly Given the above, I would not open an issue claiming PyPI/uv are behind GitHub releases, because the data doesn’t support it. If you want, paste the relevant parts of your
pyproject.toml
+
uv.lock
(or tell me if you’re using
exclude-newer
/ a mirror), and I can point to the exact reason you’re not picking up 1.31.0.
m
@late-queen-51746