azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(claude): clean up redundant post-migration content

Browse Source 
Removed/simplified sections now handled by identity.json:
- Removed Ollama endpoint table (now in identity.json)
- Condensed verbose Ollama description
- Updated GrepAI CLI path to use $CLAUDETOOLS_ROOT
- Added migrate-identity.sh step to onboarding

All machine-specific config (Ollama, Python, paths) now centralized
in identity.json — CLAUDE.md references it, doesn't duplicate it.
This commit is contained in:
Mike Swanson
2026-05-26 20:13:40 -07:00
parent 2c12bd2d04
commit 0e2629ad0e
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
.claude/CLAUDE.md
View File

@@ -24,6 +24,7 @@ This repo is shared across multiple team members. **At every session start, BEFO
- Set local git config: `git config user.name "<full_name>"` and `git config user.email "<email>"`
- Set git remote (read `gitea_username` from users.json): `git remote set-url origin https://<gitea_username>@git.azcomputerguru.com/azcomputerguru/claudetools.git`
- Add hostname to user's `known_machines` in users.json and commit.
- Run `.claude/scripts/migrate-identity.sh` to populate machine-specific config (ollama, python, platform, architecture).
- **Show the user `.claude/ONBOARDING.md`** — present section by section, explain the WHY, answer questions.
3. **If hostname doesn't match any known machine** for the identified user, update their `known_machines` in users.json.
@@ -288,13 +289,11 @@ Vault structure: `infrastructure/`, `clients/`, `services/`, `projects/`, `msp-t
Tier 0 — **Ollama is the documentation and classification engine.** Route prose, summaries, and classification through it; Claude reviews before writing or posting.
| Machine | Endpoint |
|---------|----------|
| Local Ollama present (GURU-5070, Howard-Home, etc.) | `http://localhost:11434` |
| GURU-BEAST-ROG | `http://localhost:11434` (always-on RTX 4090; common fallback target) |
| No local Ollama (e.g. GURU-KALI) | endpoint+fallback = Beast `http://100.101.122.4:11434` |
**Models:** `qwen3.6:latest` (structured: JSON, classification), `qwen3:8b` / `qwen3:14b` (prose), `codestral:22b` (code suggestions).
Models: `qwen3.6:latest` (strict-format: JSON, classification, structured rules, redaction, word-limited summaries), `qwen3:8b` (prose on DESKTOP-0O8A1RL — 86 tok/s, full 12 GB VRAM fit), `qwen3:14b` (prose everywhere else — ~66 tok/s), `codestral:22b` (code suggestions — always review). Per-machine config (endpoint, fallback, prose_model, python, platform, architecture) lives in `.claude/identity.json` `ollama`/`python` — populated by `.claude/scripts/migrate-identity.sh` (Phase 2, 2026-05-26). Scripts read `.ollama.endpoint` (no curl probe). GURU-BEAST-ROG (`100.101.122.4:11434`, always on, RTX 4090) is the usual fallback. Full reference + per-machine routing: `.claude/OLLAMA.md`
**Configuration:** All machine-specific config (endpoint, fallback, prose_model, python command, platform, architecture) lives in `.claude/identity.json`, populated by `.claude/scripts/migrate-identity.sh`. Scripts read `.ollama.endpoint` directly — no curl probing.
**Reference:** `.claude/OLLAMA.md` for full model usage + routing patterns.
### GrepAI (Semantic Code Search)
@@ -303,7 +302,7 @@ Models: `qwen3.6:latest` (strict-format: JSON, classification, structured rules,
- **When to use:** "what did we do with X", "how does Y work", "find where Z is configured", context recovery, exploring unfamiliar code
- **MCP tools:** `grepai_search` (primary), `grepai_trace_callers`, `grepai_trace_callees`
- **Agent:** `deep-explore` (for multi-hop exploration)
- **CLI:** `D:/claudetools/grepai.exe search "query" --json -c -n 5`
- **CLI:** `$CLAUDETOOLS_ROOT/grepai search "query" --json -c -n 5`
- **Watcher:** runs as scheduled task "GrepAI Watcher - claudetools" (auto-starts on login, keeps index current)
---