Changelog
Stay up to date with the latest changes to elizaOS Cloud.
April 2026
Apr 6, 2026
Auth API consistency — API keys, sessions, and clearer errors
- Programmatic access — Many dashboard and org APIs (apps/domains, ElevenLabs voices, API key CRUD except Explorer, profile, crypto payment list/status
GET, org members and invites management) now accept the same API keys you use for chat, so CI and backends do not need a browser cookie. Why: One credential model for automation; avoids “request reached the server but auth failed” confusion when only cookies worked before. - Session-only endpoints — Some flows stay browser session only (e.g. accepting an invite, redeeming a signup code, Stripe checkout, CLI web completion after login). If you send
X-API-KeyorBearer eliza_…there, the edge returns401with codesession_auth_required. Why: Clear signal that the URL expects a logged-in user in the product, not a script key; reduces abuse on one-time or redirect flows. - CLI login paths — Creating a CLI session and polling status stay easy for the terminal; completing login in the browser follows normal API auth rules. Why: Completion issues API key material and must align with cookie session semantics.
Docs: API authentication (mechanics), Auth consistency — WHY. Engineering: CHANGELOG.md.
March 2026
Mar 30, 2026
Referral invite links — API, dashboard UI, docs
GET /api/v1/referrals— Returns the signed-in user’s referral row as flat JSON (code,total_referrals,is_active); creates a code viagetOrCreateCodeon first success. Why: One round trip for “my link,” no separate create endpoint; idempotent and safe for duplicate calls from header + Affiliates page.- HTTP semantics —
401for auth failures (includingAuthentication requiredand API key errors),403forForbiddenError(e.g. no org),500for unexpected errors. Why: Callers can tell “not logged in” from “logged in but not allowed” instead of masking 403 as 500. - Dashboard — Header Invite (lazy fetch, clipboard, toast; hidden for anonymous users and during
authGraceActive). Affiliates page Invite friends card above the affiliate link (distinct styling); inactive codes show a warning and block copy in header. Why: Discoverability without a new nav item; avoids conflating?ref=with?affiliate=; grace-period gating avoids broken clicks mid-session sync. - Docs — docs/referrals.md (flows, APIs, WHYs), docs/affiliate-referral-comparison.md; README subsection updated; ROADMAP.md entry. Shared type
ReferralMeResponse+parseReferralMeResponseinpackages/lib/types/referral-me.ts. Why: README previously linked to missing referral docs; flat JSON and parser reduce client bugs.
Mar 28, 2026
Per-agent Anthropic extended thinking (MCP / A2A)
user_characters.settings.anthropicThinkingBudgetTokens: integer token budget for Anthropic “extended thinking” onPOST /api/agents/{id}/mcp(chat) andPOST /api/agents/{id}/a2a(chat).0disables thinking for that agent even ifANTHROPIC_COT_BUDGETis set; omitted or invalid values fall back to env default. Why: Agent owners set inference policy in stored character data without redeploying; request bodies must not carry budgets so third-party MCP/A2A callers cannot inflate token spend.ANTHROPIC_COT_BUDGET: clarified as default when the character does not set the key (and for routes that have no resolved character).ANTHROPIC_COT_BUDGET_MAX: optional ceiling on any effective budget. Why: Operators keep a baseline and a worst-case cap while still allowing per-agent overrides.
Docs: Anthropic CoT / thinking, CHANGELOG.md.
Mar 27, 2026
Anthropic extended thinking (deploy policy)
- Optional
ANTHROPIC_COT_BUDGET: positive integer enables Anthropic extended thinking for eligible Claude models viaproviderOptions.anthropic.thinking; unset or0leaves behavior unchanged. Why: Thinking uses extra tokens—keeping control in environment config avoids arbitrary client-controlled budgets and keeps billing/support predictable. - Provider-option merge helpers preserve existing
gateway/googlekeys when adding Anthropic fragments. Why: Routes already set gateway order or image modalities; overwriting the wholeproviderOptionsobject would drop those settings.
Milady unit tests and pricing mocks
mockMiladyPricingMinimumDepositForRouteTests: route tests that tweak minimum deposit now spread the realMILADY_PRICINGobject instead of replacing it with{ MINIMUM_DEPOSIT }only. Why:mock.modulereplaces the entire module for the process; partial objects removed hourly rates and warning thresholds and broke Milady billing cron tests when the full unit suite ran.- Billing cron test file renamed to
z-milady-billing-route.test.tswith stable queue-backed DB mocks re-registered inbeforeEach. Why: Reduces order-dependent failures when other tests also mock@/db/client.
Engineering details: CHANGELOG.md, docs/unit-testing-milady-mocks.md, docs/anthropic-cot-budget.md.
Mar 8, 2026
Anthropic Messages API compatibility
- Added
POST /api/v1/messages, an Anthropic Messages API-compatible endpoint for Claude Code and Anthropic SDK clients. - Streaming now emits Anthropic-style SSE events for both text and tool use blocks.
- Added docs for the new Messages endpoint and exposed it as a public API-key route in the proxy.
Eliza App connection enforcement
- Telegram, Discord, and iMessage Eliza App channels now require one connected data source before the agent processes messages.
- Added an in-character connection nudge flow plus a post-OAuth success page that returns users to their messaging channel.
- OAuth callback handling now invalidates the connection-enforcement cache immediately after a successful connection.
Mar 4, 2026
Wallet API — SIWE, wallet header auth, topup, docs
- SIWE (EIP-4361):
GET /api/auth/siwe/nonceandPOST /api/auth/siwe/verifyfor programmatic wallet sign-in. Returns API key; new wallets get account and initial free credits. Why: Agents and headless clients need to sign in and obtain an API key without a browser; nonce prevents replay, domain binding prevents phishing. - Wallet header signature: Per-request auth via
X-Wallet-Address,X-Timestamp,X-Wallet-Signature. First valid request for an unknown wallet creates the account (same path as SIWE). Why: Clients that prefer not to store an API key can prove ownership on each request; method+path in the signed message prevents replay on other endpoints. - x402 topup: Can credit the signer when wallet sig headers are present, or use
body.walletAddress. All wallet signup (SIWE, wallet-header, topup) uses sharedfindOrCreateUserByWalletAddress(slugwallet-${address}, optional initial credits, race handling). Why: One consistent signup path; topup with wallet sig ties payer to credited account. - Proxy & CORS: Requests with
X-Wallet-Signaturepass through without Privy session; wallet headers added toAccess-Control-Allow-Headers;/api/v1/topupadded to public paths. Why: Otherwise wallet-header auth would get 401 at the proxy before the API runs. - Docs: docs/wallet-api.md (WHYs, lifecycle, file list), Wallet API and Authentication updated, README subsection, changelog. llms.txt regenerated.
Referrals & Affiliates — docs, safety, and cleanup
- Documentation: Added docs/referrals.md with full referral and affiliate flow, WHYs, and API. Referral revenue is 50/40/10 (ElizaCloud / app owner / creator); affiliate revenue is markup on top-up and MCP, passed to the customer. No double-apply on the same transaction.
- Revenue math: Single source of truth for referral splits (
REFERRAL_REVENUE_SPLITSinlib/services/referrals.ts) with startup assertions (50+40+10=100%, 8+2=10%).calculateRevenueSplitsnow asserts total allocated equals purchase amount so changes to constants cannot silently over- or under-pay. - Dead code removed: Removed unused
processReferralCommissionandCOMMISSION_RATEfrom referrals service and unusedreferralSignupsRepositoryimport from Stripe webhook to avoid accidental re-use (which would have double-paid referral on top of 50/40/10). - Comparison doc: docs/affiliate-referral-comparison.md compares this repo with the other cloud repo (commission tiers vs 50/40/10, affiliate markup usage) and includes a revenue math audit.
- README: Referrals & Affiliates subsection under Credit System & Billing with links to the new docs.
Signup codes — env config, Discord/Telegram wiring, docs
- Config: Signup codes now load from
SIGNUP_CODES_JSONenv var (JSON object); if unset, default to{}. Why: Env allows per-environment codes without a config file in the repo; default keeps the app runnable when the var is not set. - Eliza App: Optional
signup_codein Discord and Telegram auth request bodies; for new users only, we apply the bonus increateUserWithOrganization(invalid or already-used code logs a warning and does not block account creation). Why: New users can get base credits + signup bonus in one step; existing users and bad codes do not break signup. - Docs: docs/signup-codes.md expanded with WHYs (why env var, why one per org, why session-only redeem, why CRITICAL rate limit, why no-cache, two-layer one-per-org). README Signup codes subsection and changelog entry added.
January 2026
Jan 8, 2026
Documentation Redesign
- Completely redesigned documentation with AAA pro quality styling
- New sidebar organization matching dashboard structure
- Comprehensive API reference with real endpoint documentation
- Added protocol documentation (A2A, MCP, x402)
Features
- Agent monetization and earnings system
- x402 crypto payment integration
- Improved API Explorer
December 2025
Dec 28, 2025
MCP Integration
- Full MCP protocol support
- MCP registry with curated servers
- Custom MCP server hosting
- Tool invocation in agents
Dec 15, 2025
Video Generation
- MiniMax Video-01 integration
- Runway Gen-3 support
- Image-to-video generation
- Gallery management for videos
Dec 5, 2025
Knowledge Base Improvements
- Increased document size limits
- Better chunking algorithms
- Improved retrieval accuracy
- Document metadata support
November 2025
Nov 25, 2025
Voice Cloning
- ElevenLabs integration
- Voice cloning from samples
- Multi-language TTS
- Speech-to-text support
Nov 15, 2025
Container Deployment
- Custom Docker container support
- Auto-scaling
- Health monitoring
- Log streaming
Nov 5, 2025
Apps & API Keys
- App creation and management
- Scoped API keys
- Usage analytics per app
- Webhook support
October 2025
Oct 20, 2025
A2A Protocol
- Agent-to-Agent communication
- Agent discovery
- Task delegation
- Streaming tasks
Oct 10, 2025
Image Generation
- Fal.ai integration
- FLUX model support
- Multiple aspect ratios
- Batch generation
Oct 1, 2025
Initial Release
- Chat completions API
- OpenAI compatibility
- Multi-model gateway
- Agent creator
- Basic dashboard
Subscribe to Updates
Get notified about new features and changes:
- Discord: Join discord.gg/elizaos
- Twitter: Follow @elizaOS
- GitHub: Watch elizaOS/eliza