Skip to content

v0.3.0 — editing lands on the agent surface

Latest
Latest

Choose a tag to compare

View all tags
@yong-opus yong-opus released this 03 Sep 17:08
· 1 commit to main since this release
v0.3.0
943634f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What changed on the hosted MCP surface (https://mcp.opus.pro/mcp) and the opusclip CLI since v0.2.0. Nothing to install — the endpoint is hosted, and the npm / PyPI launchers are unchanged.

Editing is on the agent surface now

  • edit_clip is served on the connector for everyone, and the raw editing-script pair (get_editing_script / apply_editing_script) is retired — the old pair signposts to it instead of accepting a script.
  • Timeline ops on edit_clip: cut and keep sections, delete a phrase, dub the clip into another language, fix captions, add a title card, add emoji — each runnable as a dry run first.
  • Deleting a phrase matches non-Latin scripts.
  • edit_clip returns a deep link into the web editor, so a person can pick up where the agent left off.
  • On MCP Apps clients an edit comes back as an in-chat receipt card — ops applied, words cut, timeline delta.
  • CLI: clip edit ops runs the same timeline ops, and delete_phrase / set_style run from the CLI too.

Publishing asks before it posts

  • Publish, schedule and share tools on the Claude connector hand off to a signed approval link for consent instead of posting straight away, and the consent mode follows the surface.
  • Publish-tool titles state what the surface actually does.

Connecting

  • Generation stays off the listed Claude connector: generative tools are not served there, and edit_clip arrives without its dub op — narrowed out of the ops it advertises, and refused if you call it anyway. mcp.opus.pro serves the full set.
  • GET / DELETE on the endpoint answer 405 instead of 403 — the 403 was making VS Code discard its client registration and re-authenticate.
  • The dedicated MCP host advertises its endpoint URI, and the RFC 9728 suffix-form protected-resource metadata is served.
  • JWKS is served at /.well-known/jwks.json.
  • Compliance-ready MCP instructions, plus the OpenAI domain challenge.

Also

  • list_scheduled_posts returns the project post URL and the failure reason.
  • The no-clip submit mode is discoverable in the submit schema.
  • duplicate_clip keeps the original title, and clip listings report their stage.
  • A render override that would change the aspect ratio is rejected.
  • arc_curate is removed from the surface.

Hosted endpoint unchanged: https://mcp.opus.pro/mcp (Streamable HTTP + OAuth, no API keys).
Docs: https://help.opus.pro/api-reference/agent-setup

Assets 2
Loading