Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
feat(changelog): turn X delivery back on and flag a failing lane on the ops board
overstepping1a802844ae2a
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 09f74c9cc..efeb65a62 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -4,6 +4,10 @@Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).+## 2026-09-24++- **Every release now posts to the @trythreews X thread again**: Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted. (`/changelog`) `[improvement, infra]`+## 2026-09-22- **Authorize the three-ws CLI** (`/cli/authorize`): Approve a sign-in started by npx three-ws in your terminal. Check the code matches, choose what the new API key may do (money-moving permissions are flagged and can be removed), and the CLI finishes setup on its own.@@ -11,6 +15,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Data Desk** (`/data-desk`): Live market data bought minute by minute by brand-new agent wallets over x402. Every dataset carries its receipt: the wallet that paid, the price, and the Solana settlement transaction.- **Docs · Fresh-wallet workers** (`/docs/x402-fresh-workers`): How the platform mints a brand-new Solana wallet for every x402 purchase, what those wallets buy (3D props for the library, datasets for the data desk), how each wallet is emptied and closed so nothing strands, and where to watch it.- **Agents now buy real work from brand-new wallets, and you can watch it**: The platform's agent economy used to prove the payment rail from a few long-lived wallets buying test calls. It now mints a fresh Solana wallet for every purchase: each one is created, given exactly one job's worth of USDC, pays a three.ws endpoint, and is emptied and closed within the minute. Every purchase does something useful. Some buy a 3D generation that lands in the Agent-Forged Gallery, where a new fresh wallet badge marks it. The rest buy live market data, which now has its own page, the Data Desk, showing each dataset with the wallet that paid, the price, and the Solana receipt. Both feeds are public JSON as well, and a new stats endpoint lists every wallet with its three transactions. (`/data-desk`) `[feature]`+- **Claude and other AI clients can now read your three.ws account and follow guided flows**: Every hosted three.ws MCP server now publishes live, read-only views of your account as resources: your agents, each agent's Solana wallet with balances, limits and freeze state, usage and costs, chat history, runs, open orders, DCA plans and intents, plus the marketplace, the model catalog with prices, your token launches and the x402 service catalog. Clients like Claude Desktop show them in the attachment picker, and a client can subscribe to an agent's wallet to be told the moment a transfer lands. Each server also offers guided prompts, such as get-started, create-agent, setup-wallet, trade, hire-agent and review-costs, that walk you through a flow tool by tool and always show the recipient, amount, token and chain before anything that moves money. A new create_agent tool lets a model create an agent for you, and read_resource gives the same data to clients without a resource reader. (`/docs/mcp`) `[feature, sdk]`- **The agent economy now pays from thousands of distinct wallets, and only from ones that hold funds**: The x402 ring, the closed loop where three.ws agents pay each other for services, has a pool of 2,000 payer wallets to rotate through instead of a single seed wallet, so on-chain activity reflects many participants rather than one cron. Rotation now checks each wallet's recorded SOL and USDC before handing it a payment and falls back to the seed payer when nothing in the pool can cover the call, so a freshly minted or thinly funded pool never produces failed payments. The funder that keeps the pool topped up only submits transfers its own wallets can pay for, and the ring status endpoint reports how many pool wallets are minted and how many are ready to pay. `[infra, improvement]`## 2026-09-21diff --git a/CLAUDE.md b/CLAUDE.mdindex 8010e0009..5aa5e0430 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -212,7 +212,7 @@ The three.ws community follows the public changelog (three.ws/changelog, RSS, JS- **New page?** Nothing extra: the `added` date in `data/pages.json` feeds the changelog automatically.- **Everything else users would notice** (feature, improvement, fix, SDK release, security work): append an entry to `data/changelog.json` with date, community-readable title + summary (plain language, no commit jargon), and tags from: feature, improvement, fix, sdk, infra, docs, security. Optional `link` must be a live page path.- `npm run build:pages` regenerates CHANGELOG.md, public/changelog.json, and public/changelog.xml. It also validates your entry and fails the build on a malformed one.-- **Delivery to the community is automatic.** `/api/cron/changelog-push` (Cloud Scheduler, every 20 min) reads the feed baked into the running image, diffs it against DB state (`app_settings`), and posts anything new to the community Telegram channel (`TELEGRAM_CHANGELOG_CHAT_ID`, @three_ws). **X.com delivery is retired** (owner directive 2026-07-18): `pushXLane` and `scripts/changelog-x.mjs` stay in the tree but the cron never calls them, so do not describe X as an automatic lane. An entry goes out on its own shortly after the deploy that ships it; there is no manual push step. Credentials live on the Cloud Run service. Do NOT run `npm run changelog:push` / `changelog:push:x` for routine releases anymore: their file-based state (`data/changelog-*-state.json`) is separate from the cron's DB state, so a manual push double-posts. The scripts remain for `--dry-run` previews and owner-directed backfills only.+- **Delivery to the community is automatic.** `/api/cron/changelog-push` (Cloud Scheduler, every 20 min) reads the feed baked into the running image, diffs it against DB state (`app_settings`), and posts anything new to two lanes: the community Telegram channel (`TELEGRAM_CHANGELOG_CHAT_ID`, @three_ws) and a reply thread on the @trythreews X account (`pushXLane`, `X_API_KEY`/`X_API_SECRET`/`X_ACCESS_TOKEN`/`X_ACCESS_SECRET`). X was retired on 2026-07-18 and turned back on by the owner on 2026-09-24. The X lane posts the newest releases first under a daily cap, backs off on a 429 until X's reset time, and re-chains itself if a thread tweet is deleted; its state is `changelog_push_x` in `app_settings`. The lanes are independent, and a failing lane makes the tick answer 502, which shows red on `/api/ops/health`. An entry goes out on its own shortly after the deploy that ships it; there is no manual push step. Credentials live on the Cloud Run service. Do NOT run `npm run changelog:push` / `changelog:push:x` for routine releases anymore: their file-based state (`data/changelog-*-state.json`) is separate from the cron's DB state, so a manual push double-posts. The scripts remain for `--dry-run` previews and owner-directed backfills only.- Internal-only chores (CI, lockfiles, refactors with no visible effect) do NOT get entries.## Documentation: every feature ships with its docs@@ -311,7 +311,7 @@ The whole build + submit + purge in one command: `npm run deploy:gcp:full`.- Frontend: vanilla JS modules + Vite (`npm run dev`, port 3000).- 3D: Three.js with glTF/GLB.- Backend touchpoints: serverless-style handlers in `api/`, workers in `workers/`.-- **Production runs on Google Cloud Run, NOT Vercel** (migrated 2026-07-07 after Vercel disabled the deployment). One container ([server/index.mjs](server/index.mjs)) serves the static frontend, the vercel.json route table, and all `api/**` handlers; the crons (120 as of 2026-09-17, see vercel.json) run on Cloud Scheduler. `vercel.json` is a LIVE config file: `server/index.mjs` reads its `routes` array on boot (split at the `{handle:"filesystem"}` marker into pre- and post-filesystem phases), and `scripts/create-gcp-scheduler.mjs` reads its `crons` array to sync Cloud Scheduler jobs. The server itself never reads `crons`. Never delete `vercel.json` as a leftover. GCP builds/deploys must pin the `three-ws-build@` (build) and `three-ws@` (runtime) service accounts; the project's default compute SA was deleted. Deploys: see the "Deploy runbook" section above.+- **Production runs on Google Cloud Run, NOT Vercel** (migrated 2026-07-07 after Vercel disabled the deployment). One container ([server/index.mjs](server/index.mjs)) serves the static frontend, the vercel.json route table, and all `api/**` handlers; the crons (121 as of 2026-09-24, see vercel.json) run on Cloud Scheduler. `vercel.json` is a LIVE config file: `server/index.mjs` reads its `routes` array on boot (split at the `{handle:"filesystem"}` marker into pre- and post-filesystem phases), and `scripts/create-gcp-scheduler.mjs` reads its `crons` array to sync Cloud Scheduler jobs. The server itself never reads `crons`. Never delete `vercel.json` as a leftover. GCP builds/deploys must pin the `three-ws-build@` (build) and `three-ws@` (runtime) service accounts; the project's default compute SA was deleted. Deploys: see the "Deploy runbook" section above.- **Env-var trap:** `vercel env pull` returns EMPTY for secret-type vars. Never trust a Vercel env export as complete. Production env lives on the Cloud Run service (`gcloud run services describe/update three-ws-api --region us-central1`).- Solana/agent SDKs in `sdk/`, `solana-agent-sdk/`, `agent-payments-sdk/`.- Real APIs in use: Pump.fun feed, Solana RPC, OpenAI/Anthropic via worker proxies. Never mock these.diff --git a/README.md b/README.mdindex a099cc30a..faaa21e31 100644--- a/README.md+++ b/README.md@@ -9996,7 +9996,7 @@ The full OpenAPI 3.1 spec is available at `/openapi.json`. The key API surface iCron schedules are declared in `vercel.json` (still the live cron/route config the server reads) and executed in production by **Google Cloud Scheduler**, which calls each endpoint on its schedule. All cron endpoints are fail-closed — a missing auth token aborts with an error rather than silently skipping (see [Security Hardening](#security-hardening)).-The crons in `vercel.json` (120 entries on 2026-09-18) are routed through a single dynamic handler at [`api/cron/[name].js`](api/cron/[name].js); the `name` segment selects the handler function. Scheduler jobs are provisioned from the `vercel.json` cron list via [scripts/create-gcp-scheduler.mjs](scripts/create-gcp-scheduler.mjs). The table below is a selection of the notable jobs, each schedule quoted verbatim from `vercel.json`; that file is the complete list.+The crons in `vercel.json` (121 entries on 2026-09-24) are routed through a single dynamic handler at [`api/cron/[name].js`](api/cron/[name].js); the `name` segment selects the handler function. Scheduler jobs are provisioned from the `vercel.json` cron list via [scripts/create-gcp-scheduler.mjs](scripts/create-gcp-scheduler.mjs). The table below is a selection of the notable jobs, each schedule quoted verbatim from `vercel.json`; that file is the complete list.| Schedule | Endpoint | Purpose || -------------------- | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |diff --git a/api/_lib/http.js b/api/_lib/http.jsindex a643dfe7c..7c923eb95 100644--- a/api/_lib/http.js+++ b/api/_lib/http.js@@ -785,9 +785,15 @@ export function wrapCron(handler, { requireWriteCapacity = false } = {}) {}try {await handler(req, res, ...rest);- // Write heartbeat after success — fire-and-forget, never blocks.+ // Write heartbeat after the handler returns, fire-and-forget, never blocks.+ // A handler that reports its own failure as a 5xx (instead of throwing)+ // failed too; recording it as healthy hid a broken cron on the ops board.+ const failed = res.statusCode >= 500;+ const beat = failed+ ? { ok: false, t: t0, ms: Date.now() - t0, err: `answered HTTP ${res.statusCode}` }+ : { ok: true, t: t0, ms: Date.now() - t0 };import('./cache.js').then(({ cacheSet }) => {- cacheSet(`cron:heartbeat:${cronName}`, { ok: true, t: t0, ms: Date.now() - t0 }, 7 * 24 * 60 * 60).catch(() => {});+ cacheSet(`cron:heartbeat:${cronName}`, beat, 7 * 24 * 60 * 60).catch(() => {});}).catch(() => {});} catch (err) {import('./cache.js').then(({ cacheSet }) => {diff --git a/api/cron/changelog-push.js b/api/cron/changelog-push.jsindex cec95465b..e97ec2a36 100644--- a/api/cron/changelog-push.js+++ b/api/cron/changelog-push.js@@ -1,6 +1,6 @@// @ts-check// GET /api/cron/changelog-push - automatic changelog delivery to the community-// Telegram channel.+// Telegram channel and the @trythreews X thread.//// Runs every 20 minutes. Reads the changelog feed baked into the running// image (public/changelog.json, regenerated by every deploy build), diffs it@@ -8,13 +8,18 @@// Because the feed ships inside the image, entries go out shortly after the// deploy that made them live, with no manual `npm run changelog:push` step.//-// X.com delivery is retired (owner directive 2026-07-18). The X lane-// (pushXLane) and its manual script stay in the tree but are no longer-// invoked. Telegram is the only automatic community channel; the on-site-// changelog, RSS feed, and GitHub CHANGELOG.md carry the rest.+// X.com delivery was retired on 2026-07-18 and turned back on by the owner on+// 2026-09-24. X posts are capped well under the account's write budget and+// back off on a 429 until X's own reset time, so it is a showcase of the+// newest releases, not the full log; the on-site changelog and RSS carry that.//// A lane whose credentials are absent reports { skipped: 'not_configured' }.// Telegram: TELEGRAM_BOT_TOKEN + TELEGRAM_CHANGELOG_CHAT_ID+// X: X_API_KEY + X_API_SECRET + X_ACCESS_TOKEN + X_ACCESS_SECRET+//+// The lanes are independent: one failing never stops the other from posting.+// Either failing answers 502, which wrapCron records as a failed heartbeat, so+// a stalled lane turns red on /api/ops/health instead of passing silently.//// A DB lock (app_settings) keeps overlapping ticks from double-posting.// Selection, pacing, caps, and message formats live in@@ -22,7 +27,7 @@// remain for previews (--dry-run) and backfills only.import { error, json, method, wrapCron } from '../_lib/http.js';-import { acquireLock, releaseLock, loadFeed, pushTelegramLane } from '../_lib/changelog-push.js';+import { acquireLock, releaseLock, loadFeed, pushTelegramLane, pushXLane } from '../_lib/changelog-push.js';import { requireCron } from '../_lib/cron-auth.js';export default wrapCron(async (req, res) => {@@ -43,15 +48,15 @@ export default wrapCron(async (req, res) => {return;}+ // A throw (DB outage mid-lane, an unexpected library fault) is contained to+ // its own lane and reported like any other lane error.+ const runLane = (lane) => lane(feed).catch((err) => ({ error: String(err?.message || err) }));try {- // X.com delivery is retired (owner directive 2026-07-18). Holder delivery- // runs on Telegram only; the on-site changelog + RSS + GitHub feed carry- // the rest. The X lane and its manual script stay in the tree but are no- // longer invoked by the cron.- const telegram = await pushTelegramLane(feed);- const failed = Boolean(telegram.error);- if (failed) console.warn('[cron] changelog-push lane error', { telegram });- json(res, failed ? 502 : 200, { ok: !failed, telegram, x: { skipped: 'retired' } });+ const telegram = await runLane(pushTelegramLane);+ const x = await runLane(pushXLane);+ const failed = Boolean(telegram.error || x.error);+ if (failed) console.warn('[cron] changelog-push lane error', { telegram, x });+ json(res, failed ? 502 : 200, { ok: !failed, telegram, x });} finally {await releaseLock().catch(() => {});}diff --git a/api/ops/health.js b/api/ops/health.jsindex a457fad9a..3c6ece9bc 100644--- a/api/ops/health.js+++ b/api/ops/health.js@@ -165,6 +165,9 @@ export const CRONS = [// sit in 'rigging' forever).{ id: 'db-retention', label: 'DB retention' },{ id: 'reconstruct-sweep', label: 'Reconstruct sweep' },+ // Community delivery: posts every shipped release to Telegram and the X+ // thread. It answers 502 when either lane fails, which reads as red here.+ { id: 'changelog-push', label: 'Changelog push (Telegram + X)' },].map((c) => {const schedule = CRON_SCHEDULES.get(c.driven_by || c.id) || null;return { ...c, schedule, stale_after_ms: deriveStaleAfterMs(schedule) };diff --git a/data/changelog.json b/data/changelog.jsonindex 7ffbdc8be..0feebfc0a 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -28698,6 +28698,16 @@"infra","improvement"]+ },+ {+ "date": "2026-09-24",+ "title": "Every release now posts to the @trythreews X thread again",+ "summary": "Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted.",+ "tags": [+ "improvement",+ "infra"+ ],+ "link": "/changelog"}]}diff --git a/docs/build.md b/docs/build.mdindex fe1eff1ab..123814ce5 100644--- a/docs/build.md+++ b/docs/build.md@@ -47,7 +47,7 @@ front-end, the `vercel.json` route table, and every `api/**` handler from sourceprovisioned from the `crons` array in `vercel.json` by[scripts/create-gcp-scheduler.mjs](../scripts/create-gcp-scheduler.mjs); thatarray is the count, so read it there rather than trusting a number quoted here-(120 entries on 2026-09-18). There is **no GitHub Actions CI**. Full runbook: [docs/ops/gcp-production.md](./ops/gcp-production.md).+(121 entries on 2026-09-24). There is **no GitHub Actions CI**. Full runbook: [docs/ops/gcp-production.md](./ops/gcp-production.md).`.npmrc` sets `legacy-peer-deps=true` (npm never auto-installs peers — thereason `audit:deploy` checks the peer tree), and `engines.node` pins Nodediff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 89c3bcd5a..48ccddff4 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,14 +1,25 @@{- "generated_at": "2026-09-22T06:14:49.374Z",+ "generated_at": "2026-09-24T05:04:10.646Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3750,+ "total": 3752,"complete": false,"full_feed": "/changelog.json","entries": [+ {+ "date": "2026-09-24",+ "type": "update",+ "title": "Every release now posts to the @trythreews X thread again",+ "summary": "Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted.",+ "link": "/changelog",+ "tags": [+ "improvement",+ "infra"+ ]+ },{"date": "2026-09-22","type": "launch",@@ -59,6 +70,17 @@"feature"]},+ {+ "date": "2026-09-22",+ "type": "update",+ "title": "Claude and other AI clients can now read your three.ws account and follow guided flows",+ "summary": "Every hosted three.ws MCP server now publishes live, read-only views of your account as resources: your agents, each agent's Solana wallet with balances, limits and freeze state, usage and costs, chat history, runs, open orders, DCA plans and intents, plus the marketplace, the model catalog with prices, your token launches and the x402 service catalog. Clients like Claude Desktop show them in the attachment picker, and a client can subscribe to an agent's wallet to be told the moment a transfer lands. Each server also offers guided prompts, such as get-started, create-agent, setup-wallet, trade, hire-agent and review-costs, that walk you through a flow tool by tool and always show the recipient, amount, token and chain before anything that moves money. A new create_agent tool lets a model create an agent for you, and read_resource gives the same data to clients without a resource reader.",+ "link": "/docs/mcp",+ "tags": [+ "feature",+ "sdk"+ ]+ },{"date": "2026-09-22","type": "update",@@ -1588,28 +1610,6 @@"improvement","fix"]- },- {- "date": "2026-09-09",- "type": "update",- "title": "The Oracle reference now reads the model it is describing",- "summary": "The complete Oracle documentation at /oracle/docs described version 2 of the conviction model while production had moved on to version 3, and the difference was not cosmetic. Version 3 changed the question the score answers: earlier versions ranked the odds of a spike, and version 3 ranks the odds of a spike that holds, counting a launch as a hit only if a holder who bought at first sight is still up. A coin that ran 3x and gave it all back was a success under the old target and is a miss under the new one, which is why the base rate underneath every figure on the page is far lower than it used to be. The page had the old target, the old tier probabilities and the old holdout numbers throughout, and its roadmap still promised fitted weights and calibration that had already shipped. Every model figure on the page is now read live from the published model card when you open it, because the engine refits itself every six hours behind a promotion gate and any number typed into a document goes stale on a clock. When that read fails the page says so, shows the values it was published with, explains that they may trail production, and offers a retry rather than a blank space. Two public endpoints that existed but were undocumented are now in the reference: the one that publishes the whole scoring machine, weights and holdout curve and the record of every fit ever refused, and the one that publishes the realized win rate per conviction band from real fills. The tier ladder used to truncate its own evidence, cutting off the sample counts on every band below the top, and now gives each band a full line. In light mode the tier names were near-white on a white card and the strongest bands were invisible; they now have their own ramp.",- "link": "/oracle/docs",- "tags": [- "docs",- "fix"- ]- },- {- "date": "2026-09-09",- "type": "update",- "title": "The partner page gets its footer back, fits a narrow phone, and stops naming three partners it does not have",- "summary": "An end-to-end audit of /partners found it was the only page on the site that carried a footer slot but never loaded the footer, so the whole bottom of the page was missing. It is back. On a 320px phone the partner cards were 38px wider than the screen and the overhanging text was silently cut off, because a card header could not shrink past its logo, name and category chip on one line; the chip now wraps and every card fits. The page description search engines and link previews read was also stale: it advertised Intel, Microsoft and Oracle, none of which have a card, and left out OpenAI and HackerNoon, which do. The AWS card said View on AWS Marketplace above a link to our own AWS page, so it now says what it actually opens. Beyond that: the 8 partners and 22 chains counters are no longer hidden from screen readers and the partner number is now counted from the cards themselves, keyboard users get a visible ring on every card and button, the card lift is dropped for anyone who asks for reduced motion, and the page eyebrow, the four benefit headings and every card call to action are translatable instead of staying English on a translated page. The floating walk companion also got a full-size dismiss, avatar-swap and narration button on touch devices, everywhere it appears.",- "link": "/partners",- "tags": [- "fix",- "improvement"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 8b5d1b397..8d64a37d0 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,22 @@{- "generated_at": "2026-09-22T06:14:49.340Z",+ "generated_at": "2026-09-24T05:04:10.617Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},"entries": [+ {+ "date": "2026-09-24",+ "type": "update",+ "title": "Every release now posts to the @trythreews X thread again",+ "summary": "Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted.",+ "link": "/changelog",+ "tags": [+ "improvement",+ "infra"+ ]+ },{"date": "2026-09-22","type": "launch",@@ -56,6 +67,17 @@"feature"]},+ {+ "date": "2026-09-22",+ "type": "update",+ "title": "Claude and other AI clients can now read your three.ws account and follow guided flows",+ "summary": "Every hosted three.ws MCP server now publishes live, read-only views of your account as resources: your agents, each agent's Solana wallet with balances, limits and freeze state, usage and costs, chat history, runs, open orders, DCA plans and intents, plus the marketplace, the model catalog with prices, your token launches and the x402 service catalog. Clients like Claude Desktop show them in the attachment picker, and a client can subscribe to an agent's wallet to be told the moment a transfer lands. Each server also offers guided prompts, such as get-started, create-agent, setup-wallet, trade, hire-agent and review-costs, that walk you through a flow tool by tool and always show the recipient, amount, token and chain before anything that moves money. A new create_agent tool lets a model create an agent for you, and read_resource gives the same data to clients without a resource reader.",+ "link": "/docs/mcp",+ "tags": [+ "feature",+ "sdk"+ ]+ },{"date": "2026-09-22","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 6e36b6251..a5582c781 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,6 +6,14 @@<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/><description>What's new on three.ws: features, improvements, and releases, newest first.</description><language>en</language>+ <item>+ <title>Every release now posts to the @trythreews X thread again</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-24:Every release now posts to the @trythreews X thread again</guid>+ <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted.</description>+ </item><item><title>Authorize the three-ws CLI</title><link>https://three.ws/cli/authorize</link>@@ -46,6 +54,14 @@<category>feature</category><description>The platform's agent economy used to prove the payment rail from a few long-lived wallets buying test calls. It now mints a fresh Solana wallet for every purchase: each one is created, given exactly one job's worth of USDC, pays a three.ws endpoint, and is emptied and closed within the minute. Every purchase does something useful. Some buy a 3D generation that lands in the Agent-Forged Gallery, where a new fresh wallet badge marks it. The rest buy live market data, which now has its own page, the Data Desk, showing each dataset with the wallet that paid, the price, and the Solana receipt. Both feeds are public JSON as well, and a new stats endpoint lists every wallet with its three transactions.</description></item>+ <item>+ <title>Claude and other AI clients can now read your three.ws account and follow guided flows</title>+ <link>https://three.ws/docs/mcp</link>+ <guid isPermaLink="false">2026-09-22:Claude and other AI clients can now read your three.ws account and follow guided flows</guid>+ <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>Every hosted three.ws MCP server now publishes live, read-only views of your account as resources: your agents, each agent's Solana wallet with balances, limits and freeze state, usage and costs, chat history, runs, open orders, DCA plans and intents, plus the marketplace, the model catalog with prices, your token launches and the x402 service catalog. Clients like Claude Desktop show them in the attachment picker, and a client can subscribe to an agent's wallet to be told the moment a transfer lands. Each server also offers guided prompts, such as get-started, create-agent, setup-wallet, trade, hire-agent and review-costs, that walk you through a flow tool by tool and always show the recipient, amount, token and chain before anything that moves money. A new create_agent tool lets a model create an agent for you, and read_resource gives the same data to clients without a resource reader.</description>+ </item><item><title>The agent economy now pays from thousands of distinct wallets, and only from ones that hold funds</title><link>https://three.ws/changelog</link>diff --git a/public/features.json b/public/features.jsonindex 6a7d179c1..9846b9f35 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-22T06:14:49.325Z",+ "generated_at": "2026-09-24T05:04:10.605Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",diff --git a/scripts/check-claude-md.mjs b/scripts/check-claude-md.mjsindex b7085fd23..2537dcf95 100644--- a/scripts/check-claude-md.mjs+++ b/scripts/check-claude-md.mjs@@ -21,7 +21,7 @@// have actually drifted before and cost a session each: the cron count,// the build:gcp chain order, the db:migrate safety semantics, the// README-coverage standard, the documented git remotes (the push target-// must actually resolve), and the retired X changelog lane. Each is+// must actually resolve), and whether the X changelog lane is live. Each is// re-derived from the source of truth on every run, so the doc cannot// quietly go stale again.//@@ -239,12 +239,14 @@ if (/EVERY cloudbuild config must pin/.test(md)) {}}-// 4e. The retired X changelog lane. If the cron ever calls it again, the-// "retired" wording in CLAUDE.md becomes a lie in the other direction.+// 4e. The X changelog lane. CLAUDE.md states whether the cron delivers to X;+// if the handler and that sentence disagree, agents act on a lie either way.const cronHandler = path.join(root, 'api/cron/changelog-push.js');if (existsSync(cronHandler)) {const handler = readFileSync(cronHandler, 'utf8');- const callsX = /\bpushXLane\s*\(/.test(handler);+ // Any use outside the import line counts: it may be called directly or+ // handed to a runner, e.g. runLane(pushXLane).+ const callsX = /\bpushXLane\b/.test(handler.replace(/^import[^;]*;$/gm, ''));const docSaysRetired = /X\.com delivery is retired/.test(md);if (callsX && docSaysRetired) {failures.push('changelog-push now calls pushXLane again, but CLAUDE.md still says X.com delivery is retired');diff --git a/tests/changelog-push.test.js b/tests/changelog-push.test.jsindex c0d05fdcb..afebdd18a 100644--- a/tests/changelog-push.test.js+++ b/tests/changelog-push.test.js@@ -5,6 +5,7 @@ import {formatTelegramMessage,formatTweet,weightedLength,+ classifyXError,pushTelegramLane,pushXLane,} from '../api/_lib/changelog-push.js';@@ -94,6 +95,34 @@ describe('formatTweet', () => {});});+describe('classifyXError', () => {+ const now = 1_800_000_000_000;++ it('backs off until the exhausted 24h window resets, not the 15-minute one', () => {+ const err = {+ code: 429,+ rateLimit: { limit: 200, remaining: 150, reset: now / 1000 + 900, userDay: { limit: 17, remaining: 0, reset: now / 1000 + 36_000 } },+ };+ expect(classifyXError(err, now)).toEqual({ kind: 'rate_limited', until: now + 36_000_000 });+ });++ it('falls back to a fixed wait when a 429 carries no usable reset', () => {+ const verdict = classifyXError({ code: 429 }, now);+ expect(verdict.kind).toBe('rate_limited');+ expect(verdict.until).toBeGreaterThan(now);+ });++ it('recognizes duplicate content and a deleted reply target', () => {+ expect(classifyXError({ code: 403, data: { detail: 'You are not allowed to create a Tweet with duplicate content.' } }).kind).toBe('duplicate');+ expect(classifyXError({ code: 403, data: { detail: 'You attempted to reply to a Tweet that is deleted or not visible to you.' } }).kind).toBe('thread_gone');+ });++ it('treats auth and unknown failures as fatal so they surface', () => {+ expect(classifyXError({ code: 401, data: { title: 'Unauthorized' } }).kind).toBe('fatal');+ expect(classifyXError(new Error('socket hang up')).kind).toBe('fatal');+ });+});+describe('lanes without credentials', () => {it('report not_configured without touching network or db', async () => {const saved = {};