dependency and a `dsh.profile.bundles` entry — `pnpm
add` writes only the first.
**Version**: 0.4.7 · **Tests**: 116 · **Runtime deps**: none · **Build step**: none
---
## What it is
Seven role tools (`ccg_analyze
docs-only changes exempt); squash-merge after green CI (`.github/workflows/ci.yml`:
verify:version + typecheck + typecheck:tests + lint + build + test:run on Node 22 and 24,
plus a separate `test:mutation
issue per run) and
`next-qa` (implementation — builds one per run) grow the automated test
suite on the **`auto-qa`** branch (queue = Issues labeled `qa`, memory =
`docs/qa-log.md`). `auto-qa` branches
Register it in `ThinkAgent.getTools()`
4. Update the relevant prompt or skill
5. Add focused tests
**Add API Endpoint:**
1. Define types in `src/api-types.ts`
2. Add to `src/lib/api-client.ts`
3. Create service
task/PR/caller, no multi-paragraph. If removing wouldn't confuse, don't write.
- **Non-tautological tests** — every test must assert behavior that breaks if prod code deleted.
## Layer model and import
pipeline
```
## Key Commands
```bash
make dev # Start FastAPI (port 8000) + Next.js (port 3000)
make test # Run pytest
make lint # ruff check + mypy
make check # everything CI checks: lint, unit tests
Sanity)
- **Generate Types**: `npm run schema:generate` (generate GraphQL types from Sanity schema)
- **No test command configured** - check with user if tests are needed
## Code Style
- **Formatter**: Biome with
Rust code
cargo fmt --check # Check formatting, matching CI
cargo clippy # Run lints
cargo test # Run all tests
cargo test provider_switch # Run tests whose names contain provider_switch
cargo
risky, architectural, or ambiguous changes.
- Use subagents only for bounded sidecar work: exploration, review, test triage, or documentation lookup.
- Prefer separate worktrees for parallel implementation sessions.
- When a task touches
usage, sound packs, remote dev, mobile notifications), see [README.md](README.md).
## Commands
```bash
# Run all tests (requires bats-core: brew install bats-core)
bats tests/
# Run a single test file
bats
site uses Tailwind CSS v4 with the Vite plugin configuration
- No linting or testing framework is currently configured
- All components are in `.astro` format (not React/Vue/etc)
- The project uses
detected) | ModelOpt source, used as workdir |
| `/hf-local` | HuggingFace model cache |
### Examples
```bash
# Run PTQ test
bash tools/debugger/client.sh run "bash hf_ptq/scripts/huggingface_example.sh"
# Run pytest
bash tools/debugger/client.sh run "python -m pytest tests/gpu
atoms
- `src/renderer/features/agents/main/active-chat.tsx` - Main chat component
- `src/main/lib/trpc/routers/claude.ts` - Claude SDK integration
## Debugging First Install Issues
When testing auth flows or behavior for new users, you need to simulate a fresh install:
```bash
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.