Repository navigation
wdx v0.5.0-dev.141
Pre-release
Pre-release
·
104 commits
to main
since this release
Unreleased
Features
- give wdx its mark, wdˣ, and put it on the site
- site: give tide its mark, a terminal window, on the site
- tide: render Markdown docs and files, m for their source
- read how much of its account's limits a Claude Code agent's ACA tells
- serve usage as GET /v1/usage and wdx usage
- tide: show the usage of each AI coding agent's account in a stats tab
- add the hub's API spec and its generated internal/hubapi
- add the hub's settings table and home in internal/hub/hubconfig
- add the hub's database in internal/hub/hubdb
- add the hub's certificate authority in internal/hub/ca
- serve the hub's API on its three endpoints in internal/hub/server
- add wdx-hub's commands in cmd/wdx-hub and internal/hub/hubcli
- build and ship wdx-hub, and run it from deploy/hub
- add the hub's accounts store, the audit chain and sealing
- add the hub's admin commands for accounts and the audit chain
- serve the hub's sign-in pages on the web endpoint
- store a usage row limited when the ACA says so, whatever its percentage
- read Antigravity's usage from the quota of its status line
- read Codex's usage from its session file
- read Cursor's usage from its dashboard API
- show the usage of Codex, Antigravity and Cursor accounts
- make machines nodes of the hub's accounts, on the hub's side
- add hublink, the node's side of the hub
- add wdx hub login, logout, status and node, served by the daemon
- keep the docs nodes push on the hub, sealed at rest
- queue a synced project's doc changes for the hub in an outbox
- push synced projects' docs to the hub with wdx project sync
- relay streams between two nodes of one user through the hub
- set up the host's authenticator code and keep the node's audit chain
- open sessions between two nodes of one account with the host's code
- serve a node's API through a session to another node
- run a command on another node with --node
- attach to a terminal or an agent on another node with --node
- open TIDE on another node with wdx tide --node
- show in the host's TIDE that a remote session is open
- wdx-hub update installs and rolls back the installed hub
- install wdx-hub as a system service with install-hub.sh
- deploy wdx-hub on Fly.io with make hub-fly-deploy
- read the draft's text from every ACA's input box
- submit a typed message once its paste shows, and confirm it went
- close a removed node's sessions on the account's other nodes
- close the sessions into this node from TIDE's Sessions dialog
- complete wdx-hub on Tab, and run help and completion on any settings
- log in to the central hub when wdx hub login has no --url
- say which usage buckets an agent's model draws on
- mark an agent limited while a bucket its model draws on is
- show in tide that an agent is limited
Fixes
- label a holder's log lines holder, and log each key once
- say a message queued when its shell or agent ends is kept, not lost
- write TIDE in capitals in wdx's own text, as the site does
- name web.tls_cert before web.tls_key when serve finds both missing
- site: import Since on the stats page
- log why the hub link lost control before saying so
- tell the hub a renewed certificate is saved before using it
- read the sync status in one transaction and log a push before the outbox changes
- bind a session's code to the step it arrived in, and log every hub request before it stops
- reset the hub's failed service before an update starts it
- show the host's reason when a remote TIDE's session closes
- list a bucket's usage windows together
- let the hub's user read the releases in test-hub-install
- release the update lock while a forked child holds its file
- let a remote client open a stream beside one in use
- start a terminal or agent created with --node in the project's checkout
- close a node's sessions on their hosts when it logs out
- nest a plan of plans' plans under it in TIDE's Plans section
- print Cursor's footer from the status line wdx pins
- read Cursor's tell box at 40 columns, recorded under wdx's status line
- put the hub's first Fly machine in the region asked for
- refuse --node naming this machine before asking for a code
- say what to do for a worktree in a repository with no commit
- log one debug_id on each line of the host's session streams
- log where each of the hub's requests came from
- name a Unix socket path too long before listening on it
- pass the host's last answer on before a session stream closes
- hand the hub's control goroutines a copy of the node