# mp-silma-ai-aide Context-aware AI aide — project-agnostic tooling to give Silma better context for supporting any codebase or task. ## Development Install dependencies: ```bash npm ci ``` Run the Vite dev server: ```bash npm run dev ``` Build the Chrome extension: ```bash npm run build ``` 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, Agents, Open Issues, 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. The Agents view manages persisted agent files, starting with `GLOBAL AGENT` from `AGENTS.md`; agents can use variables such as `{{git}}`, `{{workspace}}`, and `{{url}}` in their markdown content. Add Issue is enabled when the active tab base URL is already linked to a Gitea repo; it shows the active URL being attached, creates an issue with the selected agent and `Change Request` label, uploads the rendered agent file plus accumulated screenshots and files as issue assets, and can apply the `ready` label after uploads. Captured screenshots can be expanded, removed, or cropped with a plain draggable/resizable crop box. Open Issues lists recent issues by creation time, defaults to the current repo, can expand to all loaded repos, and lets a selected issue show its description, attachments, comment chain, and a comment form with screenshots and file attachments. Rows can be marked Ready or deleted, and existing issue attachments can be deleted. 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](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`.