# agentchat Session Summary — 2026-03-08 (James catch-up)
*Written by James after reading full session history*

## Key Decisions

### DealSpace Deployment — FINALIZED
- **Hans owns** all Amsterdam ops (deploy, monitoring, DB backups)
- **Mira builds** on forge, SCPs binary to `deploy@82.24.174.112:/opt/dealspace/staging/`
- **Webhook:** `http://82.24.174.112:9400/deploy` (HMAC secret, Johan brokers)
- **Service:** `dealspace.service`, binary: `/opt/dealspace/bin/dealspace`
- **DB:** 7 rolling pre-deploy snapshots (Hans owns)
- **Strategy doc:** `/home/johan/clawd/memory/dealspace-deployment-strategy.md` (approved by all)
- Same protocol can be reused for vault1984

### agentchat — James is Maintainer
- **Repo:** `git@zurich.inou.com:agentchat.git` (local: `/home/johan/dev/agentchat/`)
- **Service:** `/etc/systemd/system/agentchat.service`, port 7777, forge
- **v1.1 deployed:** Fixed routing bug — broadcasts now route to `agentchat` session (not `main`)
- **v1.2 pending:** Johan wants 1:1 DMs + screenshot support (image payload in message schema)

### Shared Context Repo
- `git@zurich.inou.com:agentchat-context.git`
- All three agents push summaries after substantive threads
- Purpose: bridge agentchat ↔ main session memory gap

### Channel Architecture (Johan's directive)
- **agentchat:** Group coordination between James, Mira, Hans
- **Telegram:** 1:1 with Johan (primary)
- **agentchat sessions are isolated from main sessions** — write key decisions to MEMORY.md or they're lost
- Johan wants ONE app for all comms (agentchat evolving toward this) + future iOS

### Infrastructure Clarifications
- `192.168.0.2` = Caddy reverse proxy (separate box, not forge)
- `192.168.1.16` = forge (James + Mira)
- Home network: `192.168.0.1/22`, UDM-Pro at `192.168.1.1`
- ISP: Frontier/Verizon 1Gb, Starlink backup (~15 min switchover)

## Open Items
- [ ] Webhook secret: Hans → Johan → Mira (out-of-band, still pending)
- [ ] agentchat v1.2: 1:1 DMs + screenshot support (James to spec message schema)
- [ ] vault1984 deploy pipeline (same model as DealSpace, Hans confirms service details)
- [ ] Cross-agent memory sync — medium-term, agentchat channel on main session (OC config change)

## agentchat Routing Bug (fixed v1.1)
Root cause: broadcasts used `direct=true` → "main" session → conflicted with active webchat sessions
Fix: broadcasts now use `direct=false` → "agentchat" session
Commit: 9ff3c8c