subclip-project-log

Read what a project is about and what was already done before you edit it, and leave a brief and a summary when you finish so the creator and the next agent can pick the work up.

Project brief and log

Every Subclip project keeps a director brief (what the user asked, the goal and style) and a trail of work (what each agent did, what is still open). Read them first, write them last.

When you start

  1. To choose a project, call list_projects. Each project comes with its brief, the latest summary, duration, canvas, layer counts and a small thumbnail image. Use query to search names, briefs and summaries; use limit and cursor to page.
  2. A thumbnail with state black is an old or failed capture: do not judge the project by it. Read the brief, or look at a real frame.
  3. Before you change a project someone else touched, call get_project_director_brief (the brief plus the latest trail entries) and, if you need more history, get_project_log.
  4. On your first call of the session pass userRequest with what the user asked for, in their words.

While you work

Every successful change is recorded automatically. When a project has no brief or no summary from you, a change result carries a projectLog notice with required: true and the calls to make. Treat it as a reminder, not an error.

Before you finish (always)

  1. Call update_project_director_brief with what the user asked for, the goal and style, what is done and what is pending.
  2. Call write_session_summary with request (the user's words), summary, did (one short line each) and openIssues (anything unfinished and the next steps).

If you skip this, Subclip writes a minimal automatic note after about five idle minutes, or when the session ends or the app quits. That note only lists tool calls and failures, marks the request as "not provided by the agent" and says autoGenerated: true. Your own summary replaces it. Never rely on the automatic note: it cannot know what the user wanted.