docs: refresh AGENTS.md guidance (#16923)

Co-authored-by: openhands <openhands@all-hands.dev>
This commit is contained in:
OpenHands Bot
2026-08-26 08:30:20 -04:00
committed by GitHub
parent f48eca6ab9
commit 59981caf7f
+1 -1
View File
@@ -13,7 +13,7 @@
- `VITE_WORKING_DIR` for the default workspace path sent when starting conversations.
- `VITE_ENABLE_BROWSER_TOOLS=false` to omit the `browser_tool_set` tool from new conversation payloads.
- `VITE_BASE_PATH` for serving the SPA under a subpath such as `/canvas`; pair it with `scripts/static-server.mjs --base-path` at runtime.
- Public skills are loaded from the `@openhands/extensions` npm package at build time via `SKILLS_CATALOG` (exported from `@openhands/extensions/skills`). The frontend's `SkillsService` maps catalog entries to `SkillInfo` objects and merges them with user/project skills fetched from the agent-server (with `load_public: false`). The agent-server no longer clones the extensions repo or uses `EXTENSIONS_REF` for public skills.
- Public skills are loaded from the `@openhands/extensions` npm package at build time via `SKILLS_CATALOG` (exported from `@openhands/extensions/skills`). The frontend's `SkillsService` maps catalog entries to `SkillInfo` objects and merges them with user/project skills fetched from the agent-server (with `load_public: false`). Bundled catalog skills use the persisted `enabled_skills` allow-list (defaulted from `DEFAULT_ENABLED_SKILL_NAMES`); user/project skills remain enabled unless named in `disabled_skills`. Keep this logic centralized in `src/utils/skill-enablement.ts`. The agent-server no longer clones the extensions repo or uses `EXTENSIONS_REF` for public skills.
- Default working-dir fallback is now the relative path `workspace/project` (exported as `DEFAULT_WORKING_DIR` from `src/api/agent-server-config.ts`); git-path heuristics and the default PLAN preview path should reuse that constant instead of hardcoding `/workspace/project`.
- Current Cloud behavior is implemented explicitly through the backend registry, Cloud service layer, and device authorization flow.
- Primary verification commands: `npm run lint`, `npm test`, `npm run build`, and `npm run build:lib`.