OpenHands / OpenHands/software-agent-sdk
Canvas Extensions: manifest API-scope field + CSRF confirmation + reserved names
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 539
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 137
Description
Manifest-declared API-scope field (declared/logged only at first, groundwork for future enforcement). Confirm CSRF coverage on the new canvas-extensions routes. Reserved-name/path list so an extension can't register a name or page path that collides with core Canvas navigation.
Context: agent_server's current auth (agent_server/dependencies.py) is a single shared X-Session-API-Key checked via check_session_api_key() — no per-route or per-scope authorization exists anywhere in that layer today. An API-scope field on the manifest is genuinely new infrastructure, not an extension of an existing mechanism — there's nothing to hook into yet.
Parallel to the frontend/CLI phases, non-blocking for them.
Blocked by: OpenHands/software-agent-sdk#4352
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the blocked issue #4352 and agent_server/dependencies.py, especially check_session_api_key(), then locate the new canvas-extensions routes and their manifest handling. Done means the manifest scope is declared and logged, CSRF coverage is confirmed for those routes, and reserved names and page paths cannot collide with core Canvas navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100