Skip to content

v0.0.6

Choose a tag to compare

@github-actions github-actions released this 17 Nov 19:50
· 25 commits to master since this release
d874f4a

[0.0.6] - 2026-11-17

Fixed

  • A feed source no longer loses posts silently when X stops listing them (released in 0.0.4 and 0.0.5). X lists only
    a limited number of each feed's most recent posts, and it moves an older since_id forward without saying so. A
    collector that had fallen behind, or a first listing from further back, missed posts with no sign. mentions,
    timeline and bookmarks now answer the contract's gap once per read, on the page where they find it, and the
    next page carries none:

    • mentions and timeline: every call first checks, with one small read (up to five posts), that X still lists a
      post with an id up to the cursor's, the newest one it listed. When X lists none, the page answers gap: { reason: "expired", since } from that post's time, with the posts X still lists. A first listing checks for a post from
      before its start, and answers gap: { reason: "window-truncated", since } from the start when X lists none.
    • bookmarks: a walk that meets none of the bookmarks the cursor knows, after reading 700 or more (X lists only its 800
      most recent, and may count posts it no longer returns, hence a margin of 100), answers gap: { reason: "expired", since } from when they were confirmed. A shorter walk means they were removed: no gap. A false gap needs all five
      known bookmarks removed and more than 700 added.

    A deleted post or a removed bookmark is not lost history and makes no gap. X can move past a read between any two of
    its calls (a busy account passes 800 mentions in minutes), so every call checks, by id as the cursor is, and a cut
    inside one second is seen too. The check costs up to five posts a call that the reader has just been answered,
    which X charges once in 24 hours, so next to nothing; it is not counted against events.maxCalls, so it never takes
    a read from the listing. A cursor from an earlier version is checked on its first read; the gap's time comes from its
    post's id. Source x (contract 1) is unchanged and answers no gap. gap is contract 1's, so Memory and jelly on
    v0.1.x read it.

Changed

  • The source contract is @we-the-rebel-alliance/source-contract v0.2.0 (tag v0.2.0, commit 88bdc1e), bundled into
    dist/index.js as before, with no runtime dependency. The declaration, the event shape, the error codes and the probe
    are unchanged. X sends none of v0.2.0's new keys, which Memory and jelly on v0.1.x refuse.
  • The conformance report is complete and ok. npm run conformance (new; npm run check runs it too) runs the kit over
    each source and writes reports/conformance-report.json, which names the contract it ran, v0.2.0. Every check that
    applies runs. That includes gap-and-cursor-expired and gap-once-per-read, on a cursor from further back than X
    still lists and on a first listing from further back than X lists. One check does not apply, and the report says why:
    failed-holds-cursor (atomicPages: X answers each feed read in one call, so no single post can fail on its own).
    noExpiry is not declared: X can lose history a reader has not seen.
  • Releases use the family's release kit r4.1 (1f452e5). A release runs npm run conformance on its parent in a job of
    its own and attaches the report as the Release asset conformance-report.json, listed in SHA256SUMS. It also checks
    that the staged tarball is the one it packed. docs/jelly.md carries jelly's shared rules for the family, word for
    word, and the declaration kit test/support/jelly-kit.ts knows jelly's cost and admin lines. The host range is
    unchanged, >=2.2.3 <2.4.0, tested on OpenCode 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7 and 2.3.0.

What Memory and jelly should change

  • Treat a feed source's gap as the contract says: one resync per gap.
  • Nothing else now. Once both are on source-contract v0.2.0, X will declare a price's conditions and min for the
    Owned Read rate ($0.001 a post for mentions and bookmarks when you own the X app). It may also declare
    permission.readsIdentity, so a feed can ask X who is signed in and notice a change of account itself.

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. 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.