[stevepridemore]

Requested by Steve · project thread

What

This follows #45 and has two parts.

1. A cost summary after every dream run

• Nightly, completed: a summary with the subject Graph dream — <date>: N sessions, E entities, D edges (~$cost). The body has the counts update_manifest recorded, what discovery found, and the model's closing message.
• Nightly, nothing pending: a one-line nothing new (~$0.00).
• Weekly: the cost appears in the subject and at the top of the report.
• Every email, alerts included, opens with Cost: ~$X (N turns, model) and API spend this month: ~$Y over K runs. The month figure is summed from logs/dream-runner/runs.jsonl.

2. task.js: a general API task runner

It runs one scheduled prompt (a Claude Code SKILL.md, say) on the API key, with only the capabilities its JSON task file grants. There is no shell.

• Files: list_dir and read_file work anywhere under workdir. write_file and edit_file work only under write_paths. Symlinks out of the folder are refused.
• Commands: each command is its own tool. The executable and leading args are fixed. The model supplies one argument, which must match a regex pattern, plus flags from a fixed list. Commands run with no shell and with a timeout.
• HTTP: http_request reaches only the listed prefix and method pairs. The runner injects bearer tokens and {{VAR}} values read from files, so the model never sees them. Redirects aren't followed, and URLs with userinfo are refused.
• MCP servers: stdio MCP servers, limited to an allowlist of their tools.
• Email: send_email goes through a gws-mcp notify profile, which fixes the sender and recipient. Sends are capped per run.
• Logging: runs log to the dream's runs.jsonl, so the month-to-date spend covers them. A run that doesn't complete emails an alert.
• Scheduling: scripts/register-api-task.ps1 sets up a Task Scheduler job. Tasks run on the host so they can use local tools like python or an MCP server's .exe.

Task files and their prompts live on the host, outside this repo.

The branch also carries -s ours merges of its pre-squash #45 history, so it could be reused without a force push. Those merges change no files.

Testing

• tsc is clean.
• src/dream-runner: 27/27 tests pass.
  • Mail: the nightly summary, the quiet-night message, the weekly cost header, and the month-to-date sum (last month excluded).
  • Task runner: read/write confinement, including a symlink escape; the command pattern and flag allowlist; URL prefix and method checks; frontmatter stripping; a full loop that runs a command, writes a file, refuses a read-only write and sends an HTML email; and the failure alert.

🤖 Generated with Claude Code

https://claude.com/claude-code