Mike Swanson
100a491ac6
Two session logs: - session-logs/2026-04-16-session.md: cross-cutting (multi-user, audit, infrastructure) - guru-rmm session log appended: MSI installer, Len's Auto Brokerage, Uranus, migration drift Gap fixes: GrepAI initialized + MCP server added, Ollama models pulling, settings.json created (bypassPermissions), MCP_SERVERS.md written. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
43 lines
1.5 KiB
Plaintext
43 lines
1.5 KiB
Plaintext
AZ Computer Guru - ClaudeTools Setup
|
|
=====================================
|
|
|
|
This package sets up the Claude Code workspace on your machine.
|
|
|
|
WHAT'S INCLUDED:
|
|
setup.bat - Run this first. It installs everything.
|
|
keys.txt - Vault decryption key (if Mike included it)
|
|
README.txt - This file
|
|
|
|
WHAT IT DOES:
|
|
1. Checks for prerequisites (git, claude, python, sops)
|
|
- Auto-installs missing ones via winget
|
|
2. Clones the shared ClaudeTools repo from Gitea
|
|
3. Clones the encrypted credential vault
|
|
4. Sets up the decryption key for vault access
|
|
5. Creates a "ClaudeTools" shortcut on your desktop
|
|
|
|
HOW TO RUN:
|
|
1. Extract this zip to any drive (e.g., D:\)
|
|
2. Double-click setup.bat
|
|
3. Follow the prompts (you'll be asked for your Gitea
|
|
password on first clone - ask Mike)
|
|
4. After setup, double-click "ClaudeTools" on your desktop
|
|
5. Claude will introduce itself and walk you through everything
|
|
|
|
YOUR GITEA ACCOUNT:
|
|
URL: https://git.azcomputerguru.com
|
|
Username: howard
|
|
Password: Ask Mike (you'll change it on first login)
|
|
|
|
IF SOMETHING GOES WRONG:
|
|
- Close and re-run setup.bat (it's safe to run multiple times)
|
|
- If git clone fails: check network/VPN/Tailscale connection
|
|
- If vault fails: make sure keys.txt is at
|
|
%APPDATA%\sops\age\keys.txt
|
|
- Ask Mike or ask Claude (once it's running)
|
|
|
|
AFTER SETUP:
|
|
Your workspace lives at <drive>:\claudetools
|
|
Credentials vault at <drive>:\vault
|
|
Everything syncs to Gitea automatically via /sync command
|