Funday Wiki

Amy Session Continuity (CLI ⇄ Discord)

Properties2
descriptionResume any Amy Discord-thread conversation from the omp CLI — thread ID → session dir mapping, the cwd-vs-session-store mental model, and the one command that continues it.
tagsagents, discord, amy, omp, session, continuity, cli

3 min read

🔗🧵 Amy Session Continuity — resume a Discord thread from the CLI

TL;DR 🚀 Every Amy Discord thread is an on-disk omp session. Grab the thread ID → point omp at that thread’s --session-dir → add -c. You’re back in the exact same conversation, now in your terminal. Daemon and CLI share one session file transparently.

⚡ Do it in one command

A Discord thread URL ends in the thread ID:

https://discord.com/channels/<guild>/<THREAD_ID>
                                      └── this ──┘

Resume that thread interactively in your terminal:

THREAD=1514275906170912769   # 👈 paste your thread ID
omp --allow-home --cwd /home/usr \
    --session-dir ~/.omp/amy-sessions/$THREAD -c

One-shot / headless (exactly what the daemon does):

omp --allow-home --cwd /home/usr \
    --session-dir ~/.omp/amy-sessions/$THREAD -c "your next prompt"
  • -c ▶️ continues the latest session in that dir.
  • -r 019eb1f2 🎯 resumes a specific session by ID prefix (when a dir holds more than one).
  • Omit -c/-r to start a fresh session that still lives in that thread’s dir.

🧠 The #1 confusion: cwd ≠ session store

Two unrelated directories. Conflating them is the classic trip-up.

flowchart LR
  A["🖥️ omp run"] --> B["📂 cwd — where files get edited"]
  A --> C["💾 session store — where the transcript saves"]
  B --> B1["/home/usr · AMY_WORKDIR (default HOME)"]
  C --> C1["default: ~/.omp/agent/sessions/ + cwd-bucket"]
  C --> C2["Amy override: ~/.omp/amy-sessions/ + threadId"]
📂 cwd (--cwd)💾 session store (--session-dir)
WhatWhere the agent reads/edits filesWhere the transcript (*.jsonl) is saved
🏠 Amy’s value/home/usr (AMY_WORKDIR, default $HOME)~/.omp/amy-sessions/<threadId>/
🤖 Your normal CLIwherever you launched~/.omp/agent/sessions/<cwd-bucket>/ (auto)

💡 “I thought all sessions were in /home/usr!” — Half-true. /home/usr is the cwd, and omp buckets the default store by cwd. Your home cwd shows up as the - bucket: ~/.omp/agent/sessions/-/. So your interactive sessions are keyed by /home/usr, not stored loose in it.

🗺️ Where every session actually lives

WhoStore pathKeyed byContinue with
🧑‍💻 You (plain omp from home)~/.omp/agent/sessions/-/cwd (/home/usr → -)omp -c (same cwd)
🧵 Amy thread~/.omp/amy-sessions/<threadId>/Discord thread IDomp --session-dir … -c

The daemon deliberately splits each Discord thread out of the cwd bucket via --session-dir (amyd.mjs, or wrapper ompcordd.mjs), so every thread is its own independently-resumable session — no collisions with your interactive work. Default remains ~/.omp/amy-sessions; OMPCORD_SESSION_ROOT/existing ~/.omp/ompcord-sessions are supported without stranding legacy threads.

🛡️ Safety — never double-write a live session

CLI and daemon share one .jsonl. Both writing at once corrupts continuity.

pgrep -f 'node (amyd|ompcordd)\.mjs'        # 🔍 is the daemon running?
  • ✅ Daemon idle → continue from CLI freely; it picks up your turns next time.
  • ⛔ Daemon mid-turn in that thread → wait until its run finishes (the dir’s .jsonl stops growing). Or /amy cancel in Discord first.

🔁 Direction matters

DirectionWorks?Why
Discord thread → CLI✅point --session-dir at ~/.omp/amy-sessions/<threadId>
CLI (--session-dir …) → Discord✅daemon reads the same dir; its -c sees your turns
Plain CLI session → Discord❌it’s in the - cwd bucket, not a thread dir — Amy never looks there

🧩 Why each flag

FlagReason
--session-dir ~/.omp/amy-sessions/<threadId>🎯 the thread’s transcript store — the whole point
-c▶️ continue the latest session there
--allow-home --cwd /home/usr🏠 replicate Amy’s env; without --allow-home, omp auto-relocates out of ~
--model <m>🧠 match AMY_MODEL if the daemon set one (else omit)

The daemon also injects --append-system-prompt ASK_PROTOCOL so its headless agent can ask via Discord components. From the interactive CLI you don’t need it — the native ask picker works directly.

✅ Verify you grabbed the right session

THREAD=1514275906170912769
ls -t ~/.omp/amy-sessions/$THREAD/*.jsonl | head -1   # 👀 the file -c will reopen

The newest *.jsonl there is exactly what -c resumes — match it against the last messages in the Discord thread.

See also: Ompcord — Always-on Discord Bridge (the bridge) · Amy SSOT Embed Dashboard (/amy status shows the live cwd/session).

Graph View

Backlinks