149 lines
5.1 KiB
Markdown
149 lines
5.1 KiB
Markdown
# 2026-02-12
|
|
|
|
## Daily News Briefing Cron - FIXED
|
|
|
|
**Issue:** Morning briefing wasn't posting to Discord despite cron firing.
|
|
|
|
**Root Cause:** The AI generated text but never called the `message` tool to actually send it.
|
|
|
|
**Solution:** Updated prompt to explicitly instruct using `web_search` and then `message` tool.
|
|
|
|
**Working Prompt:**
|
|
```
|
|
Generate a morning news briefing covering: 1) Formula 1 updates, 2) LLM/AI industry news,
|
|
3) Self-hosting/homelab news. Use web_search to find current news, then use the `message`
|
|
tool to send the finished briefing to Discord channel 1471156195233628394 with action=send.
|
|
IMPORTANT: Include direct URLs/links to each article/source mentioned. Format with markdown
|
|
links like [title](url).
|
|
```
|
|
|
|
**Job Details:**
|
|
- **ID:** `008d21d9-05ee-4aca-97af-646d150e2c6b`
|
|
- **Schedule:** Daily at 8:00 AM (America/Chicago)
|
|
- **Target:** #news-brief channel (1471156195233628394)
|
|
- **Format:** Markdown with clickable links for every article
|
|
|
|
**Example Format:**
|
|
```
|
|
# 📰 Morning News Briefing — Feb 12, 2026
|
|
|
|
## 🏎️ Formula 1
|
|
- [Article Title](https://url) — Description
|
|
|
|
## 🤖 AI/LLM Industry
|
|
- [Article Title](https://url) — Description
|
|
|
|
## 🏠 Self-Hosting
|
|
- [Article Title](https://url) — Description
|
|
```
|
|
|
|
**Key Requirements:**
|
|
- Must include `web_search` in the task (so it actually searches)
|
|
- Must explicitly say "use the `message` tool" (or delivery won't happen)
|
|
- Must specify channel ID and action=send
|
|
- Links must be in markdown format
|
|
|
|
---
|
|
|
|
## Status Update
|
|
|
|
**Services Running:**
|
|
- ✅ Frigate NVR - 4 cameras streaming (Kitchen, Livingroom, Front_DUO2, Back)
|
|
- ✅ Nextcloud - accessible via http://aiagents:8081
|
|
- ✅ Dashboard - at http://aiagents/dashboard/
|
|
- ✅ Supermemory backup cron - runs daily at 2 AM
|
|
|
|
**Thermal Management:**
|
|
- Nextcloud removed from startup (CPU spike causes GPU thermal issues)
|
|
- Frigate running solo keeps temps stable
|
|
- Both services work fine when started manually, just not together at boot
|
|
|
|
---
|
|
|
|
## Files Created
|
|
|
|
- `dashboard/index.html` - Daily briefing web UI
|
|
- `dashboard/assets/style.css` - Brutalist dark theme
|
|
- `dashboard/assets/app.js` - Live detections, weather widget
|
|
- `dashboard/api/detections.php` - CORS proxy for Frigate API
|
|
- Copied to: `C:\web\htdocs\dashboard\`
|
|
|
|
---
|
|
|
|
## Access URLs
|
|
|
|
| Service | URL |
|
|
|---------|-----|
|
|
| Dashboard | http://aiagents/dashboard |
|
|
| Frigate | http://aiagents:5000 |
|
|
| Nextcloud | http://aiagents:8081 |
|
|
| Home Assistant | http://aiagents:8123 |
|
|
|
|
---
|
|
|
|
## Discord #home-assistant Channel Issue
|
|
|
|
**Problem:** Model returning empty responses (`"content": []`) in #home-assistant only — #projects and #general worked fine.
|
|
|
|
**Initial Diagnosis:** Session had accumulated 197K tokens, thought it was a context limit issue.
|
|
|
|
**Attempted Fix:** Ran `/compact` — reduced context to 0K, but empty responses persisted.
|
|
|
|
**Root Cause:** Session corruption — model calls were succeeding but returning no content. Same model works in other channels.
|
|
|
|
**Attempted Resolution:** Suggested `/terminate` in the channel to force fresh session creation.
|
|
|
|
**Session Details:**
|
|
- Session: `agent:main:discord:channel:1466074219829006599`
|
|
- Session ID: `c9046c92-269c-4626-bc95-d341231bda5d`
|
|
- Model: `kimi-k2.5:cloud` (same as working channels)
|
|
|
|
---
|
|
|
|
## Notes
|
|
|
|
- Dashboard uses `aiagents` hostname for all internal links (Tailscale-friendly)
|
|
- Frigate detections update every 10s via PHP proxy
|
|
- News briefing fires at 8 AM daily
|
|
- Supermemory backup runs at 2 AM daily
|
|
|
|
---
|
|
|
|
## Afternoon Session (#home-assistant)
|
|
|
|
### Session Corruption - RESOLVED
|
|
**What happened:** Model started returning empty responses (`[]`) in #home-assistant channel.
|
|
**Fix:** Deleted corrupted session, switched back to `kimi-k2.5:cloud` (was temporarily on `qwen3-coder-next:cloud`).
|
|
**Result:** Session now clean at ~63K tokens.
|
|
|
|
### Workspace Context Architecture - CREATED
|
|
**New file:** `workspace-context.md` — daily session state that persists between channels.
|
|
|
|
**Structure:**
|
|
- **Current Conversation** — active project right now
|
|
- **In Progress** — unfinished projects
|
|
- **Planning** — ideas discussed but not started
|
|
- **Finished Today** — done projects waiting for MEMORY.md migration
|
|
- **Channel History** — timestamp log for continuity
|
|
|
|
**Key insight:** This survives session crashes, provides continuity when switching channels, and gets cleared daily with an EOD ritual.
|
|
|
|
**Updated:** `AGENTS.md` now loads `workspace-context.md` on every session, plus EOD consolidation ritual.
|
|
|
|
### Workspace Cleanup - DONE
|
|
**Problem:** Root directory was cluttered with temp files and one-off scripts.
|
|
**Actions:**
|
|
- Created `scripts/` folder — moved 8 helper scripts
|
|
- Created `temp/` folder — archived transcript files (~600KB)
|
|
- Deleted ~3MB of temp JSON dumps and session files
|
|
- Updated `TOOLS.md` with organization scheme
|
|
|
|
**Result:** Root down from ~3.5MB to ~45KB of actual documents.
|
|
|
|
---
|
|
|
|
## Decisions Made
|
|
1. `workspace-context.md` is temporary state — gets cleared daily, survives session crashes
|
|
2. End-of-day ritual: migrate "Finished" → MEMORY.md, clear file for tomorrow
|
|
3. Folder structure: `scripts/` for helpers, `temp/` for downloads/transcripts
|