lmtlssss.fun

🍿pROMPTcORN

scene scheduler

pull

scheduled terminal scenes

Scene definitions, timed playback, target session selection, and delivery proof on top of 👟CODEMAN.

The machine installs promptcorn. Operators reach it through /corn.

scene definitions timed playback codeman session targeting acknowledgement-aware delivery

Install Lane

The machine-side package path that works now.

npm install -g promptcorn
promptcorn init
promptcorn status

Scene Shape

The product in one deterministic preview.

scene: morning-openclaw-check
target_session: tmux:codeman-live:0:main
schedule: weekdays 09:00
steps:
  - switch_session
  - inject_text: "give me the overnight status report"
  - key: enter
ack:
  expect: answer
  timeout_seconds: 120

What this actually is

Scenes, timing, and delivery proof.

Scene-first

A prompt is just one kind of scene. A scene can switch sessions, open menus, inject text, confirm approvals, and wait for output.

Terminal-agnostic

If 👟CODEMAN can reach the session, 🍿pROMPTcORN can schedule it. OpenClaw is the first polished use case, not the whole product.

Ack-aware

Runs do not disappear into the dark. The point is a visible success, miss, retry, or operator-facing failure.

Delivery Chain

How a scheduled scene lands

  1. The operator uses /corn in the shared 👟CODEMAN Telegram bot.
  2. The machine-side promptcorn runtime resolves the target session, scene steps, and timing policy.
  3. At fire time, 🍿pROMPTcORN asks 👟CODEMAN to perform the scene on the live terminal.
  4. 👟CODEMAN returns structured output and acknowledgement rails back to the run ledger.

Hard Rails

Fresh-session resume spine

docs/codeman-contract.md The baseline mount and ownership contract with 👟CODEMAN.
ROADMAP.md Phase order for scenes, schedules, and acknowledgements.
STATE.md What is true right now, without previous chat context.
ACTIONS.md The granular action ledger for every product move.
HANDOFF.md The next exact thing a fresh agent should build.