Embedded web server module that provides Ktor server startup function and hosts static frontend build files (
built from web-ui/ React project)
- **workspace**: Sandboxed per-workspace file system and shell
hangs or beach-ball investigations
Keep GNU `gdb` installed only as a remote-protocol frontend or for non-native
targets. Do not waste incident time trying to make Homebrew
sqlite database for when vector databases are a poor fit for the data)
│ ├── frontend (Interfaces to interact with the backend)
│ │ ├── client (A native Python client which thinly wraps the configured
lexical rules and reuse applicable semantic results or scoped query IR without a cold frontend build. `fast` runs/reuses lexical rules only. Use `deep` when semantic evidence is needed
Keep `version.py` as the single source of truth and update only fallback labels in frontend code when changing the app version.
Current endpoints:
- `GET /api/version`
- `GET /api/config`
- `POST /api/config
MCP/tool, or other Codex-supported integration surfaces that work consistently across macOS and Windows.
## Frontend UI
- Toolbar, dock, and control icons must come from a mature icon set, not hand
ArchitectGPT**: ManagerGPT instructs ArchitectGPT to design the application's structure, encompassing both backend and frontend components, utilizing Python and FastAPI:
```sh
[*] "ManagerGPT": Executing task: "Develop a full stack app that
model naming, ownership, lifecycle, and mapping boundaries
- do not introduce aggregate or backend-for-frontend endpoints unless the simpler resource model is documented as insufficient
- document intentional architecture exceptions before
Watch for upstream changes and mirror them.
### Tauri IPC Is the Only Bridge
The frontend never touches the filesystem, never calls GitHub, never runs git. All external interaction goes through
AGENTS.md Shokunin AI Ecosystem
## Profile
Senior full-stack dev / indie-hacker. I build backend, frontend, mobile, content, business. Windows 11.
## Skills available (62 v4.2.3)
They activate automatically based on what
Consumer-independent behavior |
| **Headlamp patches** | `patches/` | Changes to the pinned Electron shell, backend, and frontend | Only when the product manifest or plugin APIs cannot express the behavior |
Headlamp source
infer implementation completion from historical decision status. Follow the conflict rules in `docs/README.md`.
## Frontend design
- For any UI/UX or renderer-facing change, read [`DESIGN.md`](DESIGN.md) and
[`docs/ui/README.md`](docs/ui/README.md) first.
- Read
Release Authority
Every release invocation must explicitly pass `-TestCategories`: one or more of
`assets`, `frontend`, `server`, `runtime`, `installers`, `dependencies`, `build`,
or `all` alone. Review the complete changes since the previous
device transport, and native tests.
- `tools/`: Network and Tweaks, each with Android libraries, a frontend, and CLI tests.
- `tool-sdk/`: tool plugin authoring APIs, runtime, and Gradle integration.
- `tool-reader
network/` and `tweaks/` contain concrete tool plugins.
- Each tool plugin has `android/` libraries, a `frontend/` web UI, and CLI tests in `cli/`. Standalone executables live inside their `../../skills/` packages.
- Shared
Tool Frontend Instructions
## npm Registry
- Use the repository registry from `.npmrc`: `https://openai.firewall.socket.dev/npm/`.
- Environment-level `NPM_CONFIG_REGISTRY` values may override `.npmrc`. Pass the repository registry explicitly when adding