Repository navigation
Releases
Releases · sumelabs/opensume-cli
v0.4.4
Fixed
schema <model>lists that model's inputs, not the whole endpoint's. It narrows the vendored router schema with the model's row in the live catalog, the one the API checks requests against. Fields the model does not take are dropped (seedance-1.5-prono longer offersvideo_url,audio_url,captions,end_image_urlor the reference lists), and its own choices and limits replace the router's widest (resolution480p|720p|1080p,duration4–12 instead of 2–600, its aspect ratios, qualities, formats and image count). A field the catalog says nothing about is kept. Offline, it lists the whole endpoint as before and says so.--jsonaddsnarrowed_to_model. Found in the production QA of the Open API (sume #13628).
v0.4.3
Fixed
- The request schemas shipped in the CLI are synced with Open production (
open-v0.3.5). They now know the 12 models added since 0.4.1: kling-image-3, seedream-5-pro, kling-2.6, kling-3-turbo, kling-3-omni, hailuo-2.3, hailuo-2.3-fast, happy-horse-1.0, happy-horse-1.1, wan-3.0-prime, seedance-1.5-pro and higgsfield-cinema-studio-4. Soschemalists their inputs offline, their fields work as flags, and--setvalues are typed for them.
v0.4.2
Hardening, from reading how genmedia (fal's CLI, v0.7.0) fails and checking each case in opensume against a mock that drops connections, serves proxy error pages and fills disks.
Fixed
- Nothing is paid for that cannot be saved.
runchecks that-o(or the current folder) can be written before it submits; a file in the way or a read-only folder is refused, exit 2, with nothing submitted. Before, the job ran and was charged, then the save failed (EACCESafter three retries, or a crash onEEXIST). - Partial saves are reported, and resumable. One file that cannot be downloaded no longer stops the others. The command exits 1, names the missing files (in
--json,path: nullwith anerrorper artifact) and printsopensume jobs wait <id>. That command now keeps files already saved under the job's default name, which are complete because files get their name only when finished, and fetches only the rest instead of saving-2copies. - Downloads are checked before they get a name. An empty body, or a web page served in place of an image (a captive portal, a proxy), is refused and retried. The job's declared
size_bytesandchecksum_sha256are checked when present. Disk errors (read-only, full, permission) are reported at once with the path, not retried. - A connection that drops mid-answer is a network error that is retried, not "Unexpected error". When retries run out, errors say how many tries there were.
- A proxy's HTML error page is reported by its status (
api.open.sume.com answered 502 Bad Gateway (tried 4 times).), with a pointer to https://status.sume.com, instead of 200 characters of HTML. - Uploads retry. The PUT to storage is retried on a dropped connection or a busy store; it is signed for the exact size, so this is safe. Creating the upload target is retried too.
uploadchecks every local file before the first upload, and reports which uploads failed instead of losing the URLs of the ones that worked.upload <url>says why a fetch failed. - Empty values are refused.
--image "$UNSET"used to drop the image and run a different, paid request. Every flag and argument now refuses an empty value and says the variable is probably not set. - The API's own limits are checked first. These are refused locally with the rule spelled out:
--limitoutside 1–100 onjobs listandjobs events,--max-usdbelow 0,-nor-dbelow 1, an--idempotency-keythat is not 1–255 printable ASCII characters (it used to surface as a fake network error), a--webhookthat is not https, and a media value likehttps://that is not a URL. A missing local file is reported before pricing. - A missing key fails at once, before any network call.
- Mid-wait outages are visible. After three failed status reads in a row, the CLI says it lost contact and keeps trying; it says when contact is back. A
--timeoutreached during an outage says the job's state is unknown, rather than "still running". - SIGTERM and SIGHUP stop the wait like Ctrl-C: exit 130, with an error that names the job (
job_idand ajobs waithint in--json). A harness that kills a slow run can collect the job instead of resubmitting it and paying twice. - Clear errors instead of crashes for a config file that cannot be read or written, an
agent --writeorinittarget that is a folder or read-only,--input(which now says: no such file, a folder, or where the JSON breaks),updatelosing its connection, and a status read withoutsume_status.
v0.4.1
Security
- The standalone binaries no longer load a project's
.envorbunfig.toml. Bun's compiled executables load every variable in the current directory's.envat start, unless they are built without it. A cloned repo's.envcould setSUME_API_BASE_URLand receive the key the CLI was using. This affected every binary release since 0.1.0; the npm package never did it. The CLI still readsSUME_API_KEY, and only that, from./.env. CI and the release now check that a.envcannot pick the host.
v0.4.0
Fewer steps for a coding agent than genmedia (fal's CLI), from a fresh machine to a saved file.
Added
opensume initwrites the agent page where coding agents read instructions: a marked block in AGENTS.md,.claude/skills/opensume/SKILL.md, and.cursor/rules/opensume.mdcwhen the project has a.cursorfolder. Running it again refreshes them. It touches nothing else and makes no network calls.--targetspicks which files to write.opensume models --brief: one line per model with its price per image or second, its inputs and its limits, cheapest first in each kind. With--jsonit is about 12 KB, against 85 KB for the full catalog.opensume agentends with that list, from the public catalog with no key needed, so one command gives an agent the setup and the choices. Its JSON hasmodels.- The key is also read from
SUME_API_KEYin./.envin the current directory, so there is no setup command. Precedence: flag, then the environment, then./.env, then the saved key. The API host is never read from.env. OPENSUME_MAX_USDcaps every run when--max-usdis not given. The refusal names which cap it hit.install.shlinksopensumeinto~/.local/binwhen that folder is already on PATH, so the command works in the same shell. Otherwise it prints the full path to use until the shell is reloaded. The release workflow checks this on macOS and Linux.
Changed
- The agent page is one source for
opensume agent, the AGENTS.md block, the Claude skill, the Cursor rule and this repo'sskills/opensume/SKILL.md. It is shorter and leads with the three commands. Tests keep the generated files equal to it. - The install scripts and the no-key error say a person makes the key, and that
./.envworks.
v0.3.0
From reading genmedia (fal's CLI) side by side, and from Open's console moving to production.
Added
opensume agent(alsoquickstart): one page to hand a coding agent. It has the install line for each platform, the API host and the one to avoid (api.sume.com), how to pass the key, the five commands that do the work,--max-usdand the exit codes. It prints Markdown by default and fields with--json.--write <file>keeps the page in a marked block of an AGENTS.md; run it again to refresh the block. It makes no network calls.- Every request field is a flag:
--rendering_speed fast,--captions.style glass,--model_params '{"seed":7}', and--no-<field>for false. Values are typed by the schema like--set, and a near miss gets the closest flag or field.schemaandrun <model> --helpshow each field's flag. OPENSUME_OUTPUT=jsonmakes every command print JSON without--json;autodoes so only when stdout is not a terminal. Completion scripts are never JSON.--help --jsonlists the install lines, the wrong host andOPENSUME_OUTPUT. The root help tells someone with no key where to make one, and points agents atopensume agent.doctorfails when the API host isapi.sume.com, sume.com's own API.
Changed
- open.sume.com is now Open's production console, so its keys work on the default host with no setup. The development host the CLI names is now Open's own,
https://open-api-development.up.railway.app(keys from open.dev.sume.com).api.dev.sume.comis sume.com's development API. - The 0.2.4 hint that sent unknown models to the development API is gone, because Open's development API lists the same models as production.
- Type errors name the field without
--set, for examplenum_images takes a whole number. - AGENTS.md now starts with the page
opensume agentprints, and a test keeps the two equal.
v0.2.4
Fixed
- An unknown model names the host that was asked (
No model "veo-3.1" on api.open.sume.com.). When the API's routers take the model but this host's catalog does not list it, the hint points at the development API, where models in preview run.
v0.2.3
Synced with the Open API as it is now: Open has its own production stack.
Changed
- The default API host is Open production,
https://api.open.sume.com(it was Sume's development API,https://api.dev.sume.com). The development API still works with--base-url,SUME_API_BASE_URLoropensume auth login --base-url; it has models in preview and its own keys. While open.sume.com is in preview, its keys are development keys. README → API hosts lists both. npm run sync-schemareads the default host's OpenAPI. The vendored request schemas already matched both hosts.
Added
- A refused key names the other host to try, in run errors,
auth status(alsoerror.hintin--json) anddoctor: a key works only on the stack it was made for. doctorshows the API's release next to its build, such asbuild 5fadc7571 (open-v0.2.0).
Fixed
- The README's prices:
gpt-image-2at low quality costs $0.012 now.
v0.2.2
Fixed
- A failed job's hint points at
opensume jobs get <id>, which shows the reason, and says it is refunded.jobs eventsprints the job's error under ajob.failedevent, since the API's event does not carry it.
v0.2.1
Found by using 0.2.0 against api.dev.
Fixed
- After a definite refusal (any 4xx), errors no longer suggest rerunning with the idempotency key: nothing was created. The key is named only when the outcome is uncertain (network errors, 5xx, interrupts).
- A submit that matched an earlier one by idempotency key says its price was paid by the first submit, and
--jsonmarks itidempotency_hit: true. --timeoutnames the job to resume once, not twice.- Canceling a job whose generation already started explains that it will finish or fail on its own.