The deployable extension output is dist/. Load dist/ in Chrome as an unpacked extension, or point deployment tooling at that folder. npm run build runs TypeScript, Vite, and a post-build check that verifies dist/manifest.json, the side panel entry, and the background service worker exist.

Static assets, including the extension icon assets, live in public/ and are copied into dist/ during the build.

The app opens in the Chrome side panel. The top icon menu includes Add URL, URLs, Gitea repos, Workspaces, and Add Issue. Add URL is enabled only for an active tab base URL that is not already in the URLs list. URLs can be deleted from the list. Add Issue is enabled when the active tab base URL is already linked to a Gitea repo; it creates an issue, uploads screenshots and files as issue assets, and can apply the ready label after uploads. The same view lists existing repo issues; selecting one opens a comment form with screenshots and file attachments.

Builds generate public/local-context.json from /Users/Tabitha/.openclaw/workspace_Father. That snapshot links known workspaces to local Gitea repos and is copied into dist/ so the built extension is self-contained.

Extension Management

See docs/extension-management.md before loading, reloading, testing, or automating the Chrome extension.

Use the Codex Chrome extension with the Chrome profile named Silma. Do not use Profile 1.

Codex

Codex setup and action commands are declared in .codex/environments/environment.toml:

Setup: npm ci
Dev: npm run dev:codex
Build: npm run build:codex
Preview: npm run preview

Gitea Workflows

.gitea/workflows/build.yml builds the extension on pushes to main and pull requests.
.gitea/workflows/issue-opened-placeholder.yml runs when a new issue is opened and prints 200 okay.