directory contains a two-process workspace chat demo: a Python backend
and a React frontend.
## Conventions
### Backend (`backend/`)
- **Framework**: Starlette (not FastAPI) served with uvicorn.
- **Dependencies**: managed via `uv` with
goes for code comments.
## Project layout
- `backend/` — Go backend (Fiber HTTP, GORM, MCP server)
- `frontend/` — Vue3 frontend, and the single source of UI for **both** the web and desktop builds
AgentRQ Frontend Design System
This document outlines the core design principles and UI patterns to ensure consistency across the AgentRQ application.
## 1. General Aesthetic
- **Minimalist & High-Density**: Prioritize information
with-release` to also link-check `cargo build --release` for the bin
+ mcp-server + frontend, or `--with-ollama` to add a live Ollama smoke test.
Definition-of-Done for v4.0
scout`, `vc-sequential-thinking`, and `vc-problem-solving` may assist
- UI/frontend -> surface vc-frontend-design skill plus vc-research-agent
- Refactor/simplify -> vc-code-simplifier for pure style or RESEARCH -> PLAN
preview or build the VitePress docs.
- `cd desktop && bun run dev`: run the desktop frontend in Vite.
- `cd desktop && bun run build`: type-check and produce a production web build
Desktop releases target **macOS and Linux only**. The phone UI is a separate web frontend.
- **Frontend:** SolidJS, strict TypeScript, Vite.
- **Backend:** Node.js, Electron, node-pty.
- **Package manager:** npm. CI uses
client tests): `npm run verify`
- Backend changes: run `npm run test:server` when possible.
- Frontend changes: run `npm run test:client` when possible.
- MCP changes: run `npm run mcp:typecheck
atomically — the running proxy picks up changes immediately without restart.
**Partial update flow:**
1. Frontend builds a patch object with only fields the user changed (compared to the last loaded
local Goose
- `just dev` — run the Tauri app in dev mode
- `just fmt` — format frontend and Tauri/Rust files
- `just fmt-check` — check frontend and Tauri/Rust formatting
- `just lint` — Biome lint
cuDNN Frontend — Agent Guide
cuDNN Frontend (FE) is a **header-only C++ library** plus a **Python package** (`nvidia-cudnn-frontend`, imported as `cudnn`) that wraps the cuDNN Graph
python/cudnn — Agent Guide
The `cudnn` Python package: pybind11-backed graph API plus pure-Python **frontend-only OSS kernels** (CuTeDSL). See `README.md` in this directory for the package inventory and [../../AGENTS.md
tests (`test/cpp`)
- Catch2 v3 binary, target `tests`, built by the default CMake build (`CUDNN_FRONTEND_BUILD_TESTS=ON`) into `build/bin/tests`.
- Run all: `./build/bin/tests`. List: `--list-tests`. One case: `./build/bin/tests "Validate
Agent: proposes Dataverse data models (read-only)
webapi-integration.md ← Agent: implements Web API integration in frontend code
table-permissions-architect.md ← Agent: proposes table permissions plan (read-only)
webapi-settings-architect.md ← Agent: proposes Web API site