ap media

Use ap media when you want hosted assets that can be reused in one-off posts or referenced from calendar.json.

Usage

ap media <subcommand>

Subcommands

`ap media upload <file>`

Upload an image or video file.

`ap media list`

List uploaded media files.

ap media list
ap media list --limit 10
ap media list --json

`ap media generate <prompt...>`

Generate one AI image and store it in your Agenda Panda media library.

ap media generate "moody wine bar interior, editorial, no people"
ap media generate "restaurant table, candlelight, premium food photography" --aspect 4:5
ap media generate "cocktail hero shot" --no-context --out ./assets/cocktail.png
ap media generate "launch poster" --project <workspace-id> --json

`ap media edit <media> <prompt...>`

Edit an existing media item into a new stored image.

ap media edit abc12345 "make it warmer and moodier"
ap media edit original-room.png "remove people, make it feel editorial" --aspect 4:5
ap media edit --latest "same shot, darker background, more candlelight"
ap media edit abc12345 "crop tighter for LinkedIn" --out ./assets/linkedin-hero.png

`ap media delete <id>`

Delete an existing hosted media item.

ap media delete <id>
ap media delete <id> --json

Common options

Option	Description
`--aspect <ratio>`	Set image aspect ratio such as `1:1`, `4:5`, `9:16`, or `16:9`
`--size <size>`	Set output resolution such as `1K`, `2K`, or `4K`
`--format <format>`	Choose `png`, `jpeg`, or `webp`
`--out <file>`	Save a local copy in addition to storing it in Agenda Panda
`--project <id>`	Pull `art.md` context from a specific workspace
`--no-context`	Ignore `art.md` for a single generate or edit command
`--json`	Return structured output

Art Context

ap media generate and ap media edit use the active workspace art.md by default when one is available.

art.md is the only visual-context file Agenda Panda expects from the customer.
--no-context disables art.md for a single command.
--project <workspace-id> lets you use art context from a specific workspace.

In practice, this means the media workflow stays simple:

ap projects update --art-file art.md
ap media generate "candlelit dinner table with wine glasses"
ap media edit --latest "same shot, fewer people in the background"
ap post "Tonight's reservation drop" --media-id abc12345

For calendar-based workflows, use the hosted HTTPS URL returned by ap media generate or ap media edit in calendar.json.

Current Prompting Decision

We ran local renderer experiments across real projects and benchmark prompts before changing the media pipeline.

Current decision:

Keep art.md as the only customer-authored visual input.
Keep the current renderer as the default for now.
Do not introduce a separate media brief or extra customer-maintained prompt file.
Treat renderer changes as benchmarked product changes, not copy tweaks.

Why:

Results were brand-dependent.
The current renderer performed well for brands like Agenda Panda.
Smarter local compilers sometimes helped editorial brands, but not consistently enough to justify a global rollout.

How To Evaluate Future Changes

Before changing the media renderer or switching image models, rerun local benchmarks against the same art.md rather than changing the customer workflow.

Good benchmark coverage includes:

mascot / character scenes
workstation / hero shots
crowd or composition-heavy scenes
editorial still life
hospitality / dinner-table scenes
image cases where text or label hallucination is risky

The standard for shipping a change is simple:

the new prompt strategy must beat or clearly match the current renderer in human review
on real customer-style projects, not just synthetic brand fixtures

Product Manager Ready Summary

Customer workflow stays unchanged: one art.md, no extra files.
Current renderer remains the default.
Future media-prompt improvements should be tested locally first with benchmark pages and side-by-side human review.
No renderer change should ship just because it sounds more structured; it should ship only if it wins on output quality.