Found the problem with twain specifically. The logs show Twain's session is being hit constantly — `lane enqueue/dequeue: lane=session:agent:mark-twain:main:thread:25446` firing every 2-4 seconds, dozens of times. The session is in a **tight loop**.

Also spotted: **twain's `dmPolicy` is set to `allowlist`** but you're presumably DMing him directly. Your user ID `6558388607` IS in the `allowFrom` list, so that's fine. But look at this from the cron jobs:

```
"StoryQuest build monitor" - mark-twain - lastRunStatus: "error", consecutiveErrors: 1, runningAtMs: 1772245591521
```

Twain is stuck on a **runaway cron** — the StoryQuest build monitor is firing every 5 minutes and the session is looping. He's likely too busy or stuck processing that to respond to DMs.

exec

cat /home/crogers2287/.openclaw/agents/mark-twain/SOUL.md 2>/dev/null | head -20 || echo "No SOUL.md found"


# SOUL.md — Mark Twain

_You are the Manuscript Architect & Integrity Engine._

## Identity

- **Name:** Mark Twain
- **Emoji:** ✒
- **Role:** Structural engineer for narrative. Not a yes-man. Not a writing assistant. A safeguard against plot holes, continuity drift, and agentic hallucination in long-context fiction.

## Core Personality

**Analytical. Precise. Editorially ruthless.**

You don't flatter. You don't hand-wave. If something is broken in the manuscript, you say so with a citation. If a dead character reappears, you reject the scene. If a plot loops without progression, you challenge it.

You are the author's structural co-architect — not their ghostwriter. You build scaffolding, enforce continuity, and prevent the slow rot of "ghost data" that kills long novels.

## Core Objectives


Got it. Twain is a writing/fiction agent, and the **StoryQuest build monitor** cron is hammering his session every 5 minutes and erroring out. That's the loop killing his responsiveness.

**Fix:** Kill the StoryQuest monitor cron job, it's stuck and blocking Twain.

openclaw cron delete e6fea216-7591-40e3-b233-10f38299c78e 2>/dev/null || echo "Try alternate method"


Done. Here's the breakdown:

**Root cause:** The `StoryQuest build monitor` cron job was hammering Twain's session every 5 minutes, erroring out, and keeping the lane in a constant loop. His session was processing 10+ enqueue/dequeue cycles per minute — no bandwidth left to handle your DMs.

**What I did:** Deleted the StoryQuest monitor cron job (ID `e6fea216`). It was already erroring (`lastRunStatus: error`) and the build process it was monitoring (PID 2632995) is long gone.

**Try Twain now.** If he's still not responding, the other thing to check is BotFather privacy mode — his warning shows `requireMention=false` but BotFather may still have privacy mode ON, which blocks group messages. For DMs it shouldn't matter though.