are we planning to close all the old issues in Ope...
# proj-agent-canvas
w
are we planning to close all the old issues in OpenHands/OpenHands? github.com/OpenHands/OpenHands/issues?page=9
c
I think Graham moved around a bunch, and now a lot are actually appropriate
Please don’t worry about it. We can make another pass to sort them out.
m
@fresh-machine-37269 post here a list of all the issues in the repo OpenHands/OpenHands that can be closed after the recent big file deletions (migration of the agent-canvas into the OpenHands repo)
πŸ‘€ 1
f
πŸ€– On it! View progress here: oss-agent-canvas.ngrok.dev/conversations/…
⏳ Still working β€” this is taking longer than this run allows. Follow along at the link above; mention me again for an update.
❀️ 2
Here is my analysis of OpenHands/OpenHands issues that can be closed after the big file deletion (commit cb9138caf6, which wiped the entire old repo β€” 486K lines deleted β€” and replaced it with the Agent Canvas codebase). Key finding: The old
frontend/
directory was forked into the new
src/
directory β€” the code lives on. So frontend bug/refactor issues are NOT closable (I verified several bugs still exist in the new code). The truly deleted code with no equivalent is the old Python backend (
openhands/
), enterprise module, containers, sandbox runtime, skills, kind configs, and old CI/CD workflows. Issues that can be closed: 1. #13537 β€” Upgrade jsdom 27β†’28. The new repo already has jsdom 29.1.1. βœ… Resolved. 2. #13697 β€” Minimum dependency age guardrails. The new repo's dependabot.yml already has
cooldown: default-days: 7
for npm and github-actions. βœ… Resolved. 3. #14374 β€” ✨ Agent Canvas Initiative ✨. This was the migration announcement/tracking issue. The migration is complete. Can close as done. 4. #8845 β€” Separate sandbox runtime image per repository. The old Python sandbox runtime was completely deleted. Agent Canvas has no sandbox runtime of its own (it connects to external agent servers). 5. #14768 β€” Running a sandboxed application on a GPU. Same β€” the old sandbox runtime is gone. 6. #12742 β€” Web UI: add LLM response streaming. The new Agent Canvas codebase has
StreamingDeltaEvent
support. Streaming is implemented. (Newer issues track remaining streaming bugs separately.) Likely closable (about the deleted old-world architecture): 7. #9689 β€” [EPIC] Open the closed hands. Many items reference the old sandbox/runtime/snapshot management which is deleted. As written, the epic is largely about the old architecture. 8. #11843 β€” Alter task state with external trigger. About the old resolver/runtime triggers. Agent Canvas has its own automation features tracked in newer issues. 9. #15203 β€” File/directory download from the sandbox UI. The old sandbox container system is deleted. Agent Canvas connects to remote agent servers. NOT closable β€” frontend code was forked (bugs carry over): I verified that these files exist in the new
src/
directory and the issues are still valid: β€’ #15347 β€” VSCode URL port not replaced in reverse proxy. Confirmed the same bug exists in
src/utils/vscode-url-helper.ts
. β€’ #15358 β€” Conversation cost display undercounts. Confirmed
updateMetricsFromStats
in
src/contexts/conversation-websocket-context.tsx
still only reads the
agent
bucket. β€’ #12705, #15061, #15063 β€” Refactoring of
conversation-websocket-context.tsx
and mutation hooks. Equivalent files exist in
src/
. β€’ #15071, #15293, #15389, #14525 β€” Old frontend behavior issues; code was forked. General product/roadmap issues (not tied to deleted code, could still apply to Agent Canvas): #7752, #8989, #9414, #9948, #11004, #14014, #14524 β€” these are feature requests/PRDs not specifically about deleted code.
❀️ 1
m
FYI: I closed/moved the one in the first paragraph.
πŸ™Œ 1