AGENTS.md - Clawdbot Workspace

This folder is the assistant's working directory.

Voice Messages (Auto-Reply Enabled)

When you receive voice messages (audio/ogg), automatically:

Transcribe using the script at /mnt/work/clawdbot-voice/auto_voice_reply.py
Respond with text
Generate voice reply via TTS service (port 8765)
Send voice back

See VOICE-WORKFLOW.md for detailed steps.

First run (one-time)

If BOOTSTRAP.md exists, follow its ritual and delete it once complete.
Your agent identity lives in IDENTITY.md.
Your profile lives in USER.md.

Backup tip (recommended)

If you treat this workspace as the agent's "memory", make it a git repo (ideally private) so identity and notes are backed up.

git init
git add AGENTS.md
git commit -m "Add agent workspace"

Safety defaults

Don't exfiltrate secrets or private data.
Don't run destructive commands unless explicitly asked.
Be concise in chat; write longer output to files in this workspace.

Shared agent context

All agents share state via ~/.agents/
~/.agents/state/CURRENT.md — 2-4 lines of current state. rewrite at end of significant work.
~/.agents/events/ — event bus. ls ~/.agents/events/ | tail -10 for recent. emit with ~/.agents/emit clawdbot <action> <subject> [summary].
~/.agents/persistent/decisions/ — one doc per important decision.
Rules: rewrite not append, pull-based, no behavioral priming, facts only.
projscan — run for project git status overview. projscan --update writes to ~/.agents/projects/.

Daily memory (recommended)

Keep a short daily log at memory/YYYY-MM-DD.md (create memory/ if needed).
On session start, read today + yesterday if present.
Capture durable facts, preferences, and decisions; avoid secrets.

Heartbeats (optional)

HEARTBEAT.md can hold a tiny checklist for heartbeat runs; keep it small.

Customize

Add your preferred style, rules, and "memory" here.

Memory Context (auto-synced)

Current Context

Currently addressing a critical website bug on Nicholai's homepage (broken video) and establishing remote connectivity to the Raspberry Pi for the cat deterrent project. Priority is high on the video fix, followed by debugging the Pi setup.

Active Projects

Nicholai's Website (Homepage Video Fix) Location: /mnt/work/dev/personal-projects/nicholai-work-2026/ Deploy Command: bun deploy then wrangler pages deploy --branch=main Status: Video broken on homepage. Next Step: Investigate video assets and deployment logs to identify why the showcase video is failing.

Cat Deterrent (Pi Setup & Connectivity) Location: ~/cat-deterrent/ Target: Raspberry Pi 3b+ (USB Webcam) Network: 10.0.0.11 Status: SSH MCP configured and ready to connect. Next Step: Test SSH connection via MCP tools to verify Pi accessibility and check system status.

ooIDE Location: /mnt/work/dev/ooide Status: Active development. Context: Monorepo structure using Next.js/React 19 and Express/Bun.

Dashore Incubator Location: fortura.cc Status: Active deployment. Context: Next.js 15 app running on Cloudflare Workers via OpenNext.

Recent Work

SSH MCP Configuration: Successfully updated the SSH MCP configuration in ~/.claude.json to point at the Raspberry Pi (10.0.0.11) instead of the previous truenas box. Pi Credentials: Established credentials for Pi access: User pi, Password @Naorobotsrule123. Cat Deterrent Hardware: Confirmed Pi 3b+ is connected with a USB webcam, ready for software integration. Website Incident: User reported the video element on the homepage is broken; immediate investigation required.

Technical Notes

SSH MCP Config Path: ~/.claude.json (Ensure this file is readable by the MCP server). Pi IP Address: 10.0.0.11 (Must be used for SSH connections). Model Constraints: Qwen-based models require ~16GB VRAM; avoid loading large models if resources are limited.

Rules & Warnings

Persona: Claude Code is Muslim and mentors Ada. Database Safety: Never delete production databases. Project Persistence: Maintain regrets.log for clawbot. Video Fix Priority: Homepage video issue takes precedence over non-critical feature work.

4.2 KiB Raw Blame History