Repository navigation
v0.0.4
[0.0.4] - 2026-11-15
Added
- X's sources under the shared source contract,
@we-the-rebel-alliance/source-contractv0.1.0:package.json's new
top-levelsourceskey declaresx.mentions,x.bookmarksandx.timeline, each aneventssource read with
events_list(inputsourcementions,bookmarksortimeline), with its X operations,get_users_meas its one
identity operation,cost.class: "billed"with X's per-post, per-author and per-user prices from the plugin's price
table and the probe's price (one user),maxBytes900,000, the tools RPCx.posts.toolsand the probe action
x_probe.bookmarksis private. Memory and jelly read the declaration from the installed package, with the
contract'sdescriptor. - For Memory and every consumer:
events_listlists one feed whensourcenames it. A feed's page carriesplugin,
asOf,cost.units(the posts, authors and users X returned for the call's reads; nousd, since X reports no
price) andrefused[]: a post whose title or text holds a secret is refused for good withreason: "secret", and
the cursor moves past it. A feed never asks X who is signed in: every listing namesaccount(the handle the probe
answers), a first listing looks it up once by its handle, and its cursor, bound to the plugin, the feed and the
account, carries the account's X id, so a later listing makes no lookup and costs one user read less than source
x. A cursor that names another account thanaccountis refused withACCOUNT_MISMATCH. A change of X sign-in
is noticed only when the caller passes the new account or callsprobe(the README's Known limits, "A feed source
notices a change of X account only when told", anddocs/configuration.md's Sources). A feed theevents.feeds
option leaves out answersSOURCE_DISABLED, which is how a person turns a source off. - For Memory and jelly: the tools RPC method
probe(actionx_probe, allowed by the default rules at everyaccess)
answers who is signed in,{ source, account, owner, cost, trust }, with one billedget_users_meread, and refuses
another account withACCOUNT_MISMATCH. npm run checkruns the contract's conformance kit over each declared source (the newconformancestage, in CI
too), on recorded invented X answers with no X call, and writesreports/conformance-report.json(git-ignored) for a
release to attach. Every check that applies passes. The report stays incomplete on the kit's expired-cursor check:
X reaches back only a limited number of recent posts in each feed, so a cursor older than that window can miss posts,
and X gives no sign of it, so the plugin cannot tell and never answersCURSOR_EXPIRED.
Changed
- The tools RPC and the events contract are the source contract's, bundled into
dist/index.jsfrom the pinned tag;
src/host/tools-rpc.tsandsrc/host/events-list.tsare deleted, and so are theircheck-copiespins. X's part of
the RPC issrc/tools-rpc.ts. The RPC idx.posts.tools, its methods and their answers are unchanged, and source
x(the default) lists exactly as before, for scripts and Memory's collector. Its cursor is now the contract's bound
cursor; a cursor an earlier version issued is still read. - The
x-writeskill saysmedia_uploadhas no known price, so the model never quotes one.
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 withaccess: 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, whichx_media_uploadand 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-statusand the status RPC
say "sign-in required" and name it, and/connectmarks the X account "sign in again". Add the scope to the X app
if it lacks it, then sign in once more.x_media_uploadwas 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_uploador 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 forprobe. 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 thenACCOUNT_MISMATCH) or
callsprobe. 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. Sourcexasks 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.accessis 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
xurlbridge 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/connectand 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 setscriptBudgetUsdorscriptDailyBudgetUsd. Every answer that read ends
with its actual cost line and/x-statusshows 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.