Usage

Once mounted, no interaction is needed — every session in the profile gets a log.txt in its workspace, starting with a write-probe section. Ask the agent anything about earlier work ("what exact command failed back then?") and the prompt section steers it to grep the log.

Check plugin health at any time:

/prolong status

prolong-memory status
log file: log.txt (per-session workspace)
window: full

session 9f3c…
  path: /work/demo/log.txt
  writable=yes sections=128 lastSeq=341

denied tool calls referencing the log: 0

Configuration (cordis.yml / patch overlay)

field	default	meaning
`logFile`	`log.txt`	log file name inside the workspace (path traversal rejected; misconfiguration fails loud)
`logWindow`	`0`	`0` = keep everything; `N>0` = keep last N sections; `-1` = disable entirely (no-log ablation)
`promptOrder`	`150`	system-prompt section ordering
`registerPrompt` / `registerCommand`	`true`	toggle the prompt section / the status command independently
`denyKeep`	`20`	denied-call records kept for the status report

Temporary debugging without touching the profile: dsh --profile web --patch ./overlay.yml.

dsh-prolong-memory

安裝

說明文件

Usage

Configuration (cordis.yml / patch overlay)