Calliope changelog — 24 August 2026

[benjiyaya]

Calliope changelog — 24 August 2026

Agent + Assets Management update. Ships in Windows zip 1.2.1.

Posted in both places:

• Release v1.2.1 — zip download
• Discussion #20 — comments

Video / H3 / Generate-all: 2026-08-23.

---

Agents

Agents chat is a plugin harness with an event-sourced session log. UI rows and LLM history are derived from that log — they are not written on their own.

Modes

• Project-linked — tools stay on that film (story, scenes, assets, jobs).
• Sandbox — no project. @workflow / generate queues on hidden Playground scratch. The agent does not create_project just to make an image. create_project / link_project only when the user wants a film; the session then re-scopes.

Tools the agent may use

• Workspace: create_project, link_project, list_projects.
• Story / script: draft and edit beats, characters, locations, misc. items, scenes.
• Assets / render: enqueue_asset_jobs, enqueue_video_jobs, run_workflow, wait_for_jobs, attach_asset.
• attach_asset files a finished generate (job_id or path) onto a film as a character sheet, environment, or misc. item. Refuses Playground scratch.

Comfy MCP comfy_* generate tools are not loaded. Agents use Calliope HTTP tools only.

Human-in-the-loop (1.2.1)

• Render tools (run_workflow, enqueue_asset_jobs, enqueue_video_jobs) stay hidden until the user’s latest message asks to generate or confirms an offer.
• Tagging @workflow alone is not permission. Creating a misc. item (or any text edit) is not permission.
• Intent is read from user prose only. The machine [Calliope context] appendix is stripped first (kind=image in the appendix cannot unlock renders).
• More than three video clips needs an explicit “all scenes / every clip” — a bare “yes” after a 2-clip offer must not enqueue the whole timeline.
• Destructive replace=true regeneration on a non-empty project still needs an explicit confirm (“yes, replace” / “from scratch”).

Helpers live in harness/policy.py.

Operator controls

• Settings → Agent: hardening rules appended last on the system prompt (blank disables). Same text on swarm sub-agents.
• Step budget: agent_max_steps.
• Composer: @ mentions (workflows), file attachments. Welcome chips stay on a newly created empty session.

---

Assets management

Three entity types on Project → Assets. All three are LLM-extracted in Draft Storyline, editable in Story, and generated as reference images here.

Type	Stored as	Video refs
Characters	characters	Yes — sheets / portraits
Environments	locations	Yes — location / env
Misc. Items	items	Picker can use the image; items are not auto-attached to scenes

Items match locations in the form (name, description, consistency_prompt, reference_image_path). Image prompt on the card maps to (Input:prompt) by role, not node id.

Generate (Assets tab)

• Per-entity Image prompt + workflow inputs (width/height/seed…). Shared top-form Text Prompt stays empty — use the entity prompt.
• Worker writes the output path onto the entity. Items now persist reference_image_path (they used to finish in the queue and stay Pending on the card). Queue label: Name · item.
• Characters / locations were already attached this way.

Playground → project

• Add to project can add as Character sheet, Background / location, or Misc. item.
• Misc. item creates a new row. It does not replace an existing item on the project list. Name field (prefilled from the file); existing items stay unchanged.
• Character / location still pick an existing row.

Agent path

• Sandbox generate → Playground job → attach_asset onto a real film (sheet / env / item).
• Or enqueue from a linked project after the user asks to generate.