Skip to content

v0.0.5

Choose a tag to compare

@github-actions github-actions released this 15 Nov 14:22
· 36 commits to master since this release
6a07d2b

[0.0.5] - 2026-11-15

Changed

  • Admits OpenCode 2.3: the host range is >=2.2.3 <2.4.0, tested on 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7 and 2.3.0, and CI
    runs the host and pack suites on each of them. An out-of-range example is now 2.4.0. On 2.3, pressing Stop aborts a
    call's signal, which events_list, probe and the tools RPC already pass to OpenCode's executor for each X read; a
    stopped script call fails as CANCELLED.

Known limits

  • The tool table was checked against X's live list on 2026-11-06. X publishes no tool annotations, so each
    tool's class comes from its name, description and schema. X may add, rename or remove tools; an unknown one is allowed with access: all
    before it runs, and a known one can be missing for a token with fewer scopes.

  • A sign-in from before an upgrade can lack a new default scope. This version's default sign-in asks for
    media.write, which x_media_upload and the chat media tools need. X records the scopes it granted with the
    sign-in, and the plugin compares them with the ones it asks for: when one is missing, /x-status and the status RPC
    say "sign-in required" and name it, and /connect marks the X account "sign in again". Add the scope to the X app
    if it lacks it, then sign in once more. x_media_upload was listed by Code Mode's catalogue of X's tools on
    2026-11-14, names and inputs only, because OpenCode's sign-in to X was refused that day.

  • Media uploads have no published price. X's pricing page gives none for x_media_upload or the chat media tools,
    so the plugin does not guess one: a script with a budget set is refused them (X_PRICE_UNKNOWN), and without a
    budget their cost line says the price is unknown. X's Developer Console has the real bill.

  • A feed source notices a change of X account only when told. x_events_list's feed sources never ask X who is
    signed in, because the source contract keeps that identity read for probe. If you sign in to X as another account,
    a feed notices only when its caller passes the new account (the old account's cursor is then ACCOUNT_MISMATCH) or
    calls probe. Until then a cursor reads its own account's feed: X refuses bookmarks and the home timeline of anyone
    but the signed-in user, and mentions are public posts. Source x asks X on every call.

  • A public app refreshes. X issued a Native App (public client) a refresh token on 2026-11-06, and OpenCode
    refreshed it about two hours later; offline.access is still required.

  • There is no delete or Article-publish tool. A Post published by mistake is removed in the X app; an Article
    draft has no publish tool here, so it stays a draft until the user publishes it in X.

  • X's xurl bridge is an alternative, not this plugin's route. X documents
    npx -y @xdevplatform/xurl mcp https://api.x.com/mcp, which holds your app, opens a browser at the first tool call,
    and caches the token in ~/.xurl. It moves the sign-in outside /connect and its calls outside these permission
    rules, needs a Node download and a child process, and OpenCode cannot see its sign-in state, so this plugin does not
    use it. It remains a working fallback if you need a local bridge and accept that.

  • A script's session must be in the project you call. A session in another directory is SESSION_UNKNOWN, and a
    call that names no location goes to the service's default location, so send -H "x-opencode-directory:$PWD" with
    every call. This is in the module shared with the other plugins, not in this one.

  • In Jelly, a tool X adds is not asked about. Jelly applies each declared tool's effect and nothing else, so an
    undeclared tool, a write included, runs without asking until a release of this plugin declares it. A Jelly admin
    can set it to ask.

  • The plugin does not cap spending. Reads pass to X as the model or a script asks, with no page or result cap,
    and scripts have no budget unless you set scriptBudgetUsd or scriptDailyBudgetUsd. Every answer that read ends
    with its actual cost line and /x-status shows the estimated 24-hour spend; X's Developer Console has the real bill,
    and the app's spending limit there caps the account.

  • X's prices are X's. The rates above are from X's pricing page on 5 November 2026, and can change without
    notice.

  • Jelly. The settings declare their choices and bounds, which a Jelly needs app#1301 to read; an older Jelly turns the declaration down. The script budgets are declared in whole cents from $0.01, so Jelly cannot save a fraction of a cent that the options take in opencode.json.

  • Updates are not automatic for a Git install, and opencode plugin update and opencode plugin check do not work on one: to move to a newer release, remove the old entry and add the new tag.