Skip to content

v0.0.8

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 15:17
· 7 commits to master since this release
ba0a997

[0.0.8] - 2026-11-20

Added

  • List snapshots x.bookmarks.list and x.posts (output: "list"), for an app and not for an agent. An app can bind them and render a list without knowing X: the tools RPC method events_list with list bookmarks or posts answers the contract's list output, through the same get_users_bookmarks and get_users_posts reads as the feeds, not a second client. Posts are listed newest first, once each, and a post whose text holds a secret is screened whole and left out before any of it is cut; the answer stays inside the source's 64 KB, dropping whole items from its end and marking shortened: true rather than cutting an item's bytes. The method declares both answers, so the host accepts the list; x_events_list, the model's tool, keeps its events-only input and output. x.bookmarks, x.mentions and x.timeline stay events sources and are not renamed. No write is declared, and this change sends none of v0.3.0's new fields.
  • x.bookmarks.list is off when bookmarks is: a list of a feed the events.feeds option leaves out answers
    SOURCE_DISABLED before any billed read, as the feed does. x.posts is not an events feed and has no plugin switch:
    only the consumer's consent turns it off.
  • A known gap: a list looks up the handle it is asked for (get_users_by_username) and does not read which account
    is signed in. The declaration is source-contract v0.1.0, which Jelly pins and whose schema cannot say a content read
    also reads the identity (readsIdentity is v0.2.0), so a list cannot detect a later change of X sign-in. X refuses
    another account's bookmarks itself; x.posts would list that handle's public posts, labelled as the grant's. The
    check returns, with readsIdentity, once Jelly reads source-contract v0.2.0 or later.
  • For jelly: sources gains x.bookmarks.list and x.posts, so Jelly asks for consent again; x.mentions, x.bookmarks and x.timeline are unchanged.

Changed

  • The source contract is @we-the-rebel-alliance/source-contract v0.3.0, pinned as github:we-the-rebel-alliance/source-contract#v0.3.0 (commit 2fd55cd) and bundled into dist/index.js, still with no runtime dependency. x.mentions, x.bookmarks, x.timeline, x.bookmarks.list and x.posts declare and send none of v0.3.0's new keys (facts, hints, routines, actor kind, sections/parts), which a consumer still on v0.2.0 refuses; their declarations and pages are unchanged, and a pin alone sends nothing. The conformance test states why each new check does not apply to a page here.

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.

  • X lists only each feed's most recent posts. X keeps a limited number of each feed's newest mentions, timeline posts
    and bookmarks (its 800 most recent bookmarks). A collector that falls behind, or a first listing from further back,
    could miss posts. A feed source answers the contract's gap once when that may have happened (configuration).
    Source x answers no gap.

  • A deleted post is not reported. A post X stops listing because its author deleted it, or a bookmark you removed,
    is simply not listed again; an event already listed stays with the consumer. It makes no gap: nothing was lost.

  • 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 that identity read is probe's until Memory and jelly accept a source that declares it
    (permission.readsIdentity, in the source contract they pin). 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. The answers under
    Cost lines carry their 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.