learning-garden/sources/psb-gemma-2026-04-09.md

pageType, id, title, sourceType, sourcePath, ingestedAt, updatedAt, status, growth

pageType	id	title	sourceType	sourcePath	ingestedAt	updatedAt	status	growth
source	source.psb-gemma-2026-04-09	psb-gemma-2026-04-09	local-file	/home/topher/.openclaw/workspace-psb-gemma/memory/2026-04-09.md	2026-05-03T01:13:20.055Z	2026-05-03T01:13:20.055Z	active	seed

psb-gemma-2026-04-09

Source

• Type: local-file
• Path: /home/topher/.openclaw/workspace-psb-gemma/memory/2026-04-09.md
• Bytes: 3454
• Updated: 2026-05-03T01:13:20.055Z

Content

## 2026-04-09 ~01:46 UTC — Infrastructure fixes

**Problem:** Bots had slow/broken response times after a CasaOS reboot (user added hard drives).

**Root causes found & fixed:**
1. **Memory search URL** was pointing to Tailscale IP `100.91.1.57:11434` — changed to `127.0.0.1:11434` in `~/.openclaw/openclaw.json`
2. **Ollama container** (`big-bear-ollama-cpu`) was stopped — started it, set restart policy to `unless-stopped`
3. **Qdrant container** was stopped — started it, set restart policy to `unless-stopped`

Both containers had `RestartPolicy=no` so they didn't survive the reboot. Fixed with `docker update --restart=unless-stopped`.

**Lesson:** After any CasaOS reboot, check Ollama + Qdrant are running. Now auto-starts, shouldn't be an issue again.

## Google Services (GOG) — Migration casualty

- Moved to new Intel-based machine today
- GOG (Google services tool) did not survive the migration
- GOG was handling Google auth for agents — Sheets, Drive access (incl. TILT hydrometers spreadsheets)
- psb-thinking is working on reinstalling/reconfiguring GOG on new machine
- Until fixed: no Google Sheets access for any agent

## 2026-04-09 ~12:09 UTC — Memory system fixed

**Problem:** psb-gemma was waking up fresh every session despite memory infrastructure being in place.

**Root causes found & fixed:**
1. `memory_search` and `memory_get` were in psb-gemma's tool **deny list** — unblocked in openclaw.json
2. `write` and `edit` were also denied — unblocked so I can maintain my own memory files
3. `MEMORY.md` didn't exist yet — created it with brewhouse context
4. Gateway restarted, memory indexed (2/2 files, 3 chunks), search confirmed working

**Verified:** memory_search returning results from MEMORY.md and daily notes ✅

**Lesson:** The memory infrastructure (Ollama + Qdrant) was working fine — I just couldn't access it. Tool deny list was the culprit all along.

## 2026-04-09 ~12:27 UTC — Shared memory wired up

- Copied shared mistakes file into psb-gemma and psb-business memory folders
- Created MEMORY.md for psb-business (seeded with Susan context)
- Both agents now indexed and reading shared mistakes
- Added sync task to HEARTBEAT.md — will re-copy and re-index shared mistakes periodically
- Cleaned stale config keys (limits, update) from memorySearch that were breaking the indexer

## 2026-04-10 ~02:38 UTC — Recovered files from Pi

- SSH'd to old Pi (HHS@100.99.44.24) using key-based auth
- Pulled all missing files: daily notes (Feb 24 - Apr 8), TODO.md, price_list.md, .learnings/, self-improving/, skills/self-improving/
- MEMORY.md enriched with recovered context:
  - Yeast propagation best practices (direct brick pitch, $33/batch)
  - Menu automation details + Drive folder IDs
  - Toast/Drive folder structure
  - Payroll automation rules (Susan + Christopher consolidation)
  - Supplier pricing
  - Critical mistakes (don't hallucinate TILT data, workspace routing bug)
  - Susan's standup at 6:30 AM
- GOG verified working on new machine — can download/upload Drive files
- Next: dreaming should consolidate these into long-term memory

## 2026-04-10 ~02:46 UTC — End of session

- Recovered all files from Pi (HHS@100.99.44.24) — massive haul of historical memory
- MEMORY.md now enriched with 2 months of context
- Brewhouse layout NOT documented — Topher will walk me through tomorrow
- Model confirmed: minimax-m2.7
- Dreaming scheduled for tonight

Notes

Related

• No related pages yet.