Claude brings full software functionality into chat windows: The same document can be edited collaboratively by humans and AI.

Yield vault protocol Hyperwave announced in a statement that, due to rising operational costs and regulatory uncertainty, the project has decided to gradually cease operations. The protocol will officially shut down on December 16, and users are advised to withdraw funds before that date to facilitate faster withdrawals. After shutdown, any remaining net asset value (NAV) will be returned to wallets holding vault tokens. All vaults, including GWAVE, have now been set to withdrawal-only mode, allowing users to unstake at any time. Vaults will continue generating yields while converting funds into underlying assets to prepare for user withdrawals. Additionally, 100% of all revenue generated before the protocol’s shutdown will be used to repurchase and burn HWAVE. The project team reminds users to stay vigilant against phishing links that may emerge during the shutdown period. For questions about the shutdown arrangements, users can contact the official support team via Discord or in-app channels.

Citi raises Coreweave (CRWV.O) price target from $128 to $149.

According to EmberCN's monitoring, as ZEC's price plummeted today and dropped below $1,000, two addresses of asset management and hedge fund Abraxas Capital holding ZEC short positions on Hyperliquid have generated an unrealized profit of $34.98 million from their ZEC positions alone. Currently, the total unrealized profit from all open positions of these two addresses stands at $118 million.

Aethir announced that its previously proposed tokenomics update has officially taken effect, with the highly anticipated ATH burn dashboard and first batch of daily burns launching simultaneously. According to the official, under the new mechanism, ATH burn funding comes entirely from network fees paid by customers when reserving computing power; fixed platform fees have been scrapped, replaced by variable network fees that adjust with market conditions. The exact amount of each burn is automatically calculated via a public formula that combines the network revenue of the past 730 hours and the 30-day time-weighted average price of ATH, ensuring the burn scale aligns closely with actual network activity. The mechanism has already generated preliminary data: cumulative burns total 4,364,413 ATH, with 629,516 burned in the past 24 hours, and weekly burns offset 18.48% of total token issuance. To ensure full transparency, all burns are executed on the Arbitrum network and sent to a public burn address; anyone can verify every transaction record via the dashboard or a blockchain explorer. Additionally, the new mechanism sets a hard cap to ensure variable network fees never exceed the value of cloud host rewards. This means that while protecting cloud host operators’ revenue, ATH’s maximum supply will always remain at 42 billion tokens. As more computing power nodes go online in the future, all relevant revenue will be included in this public, daily-auditable burn mechanism.

According to Bitget's market data, WTI crude oil rose more than 1% intraday, now at $87.35 per barrel. Brent crude oil gained 1.6% on the day, currently quoted at $93.52 per barrel.

Beating AI News Flash: Cursor is upgrading its Projects feature, launched this September, to a multi-user collaborative version called Team Projects. Previously, a single user could manage multiple coding agents via a lead agent to develop features and fix bugs simultaneously. Now, team members can join the same Project: each retains their own lead agent and execution agent, but all share a single task board and project repository. The task board displays who is responsible for what, which tasks agents are handling, and their corresponding GitHub PRs. The repository stores requirement documents, design drafts, technical solutions, and project decisions. A solution agreed upon in a chat by one member is accessible to other members’ agents, eliminating repeated context explanations. Lead agents of different members can also communicate directly. For example, if one member’s agent is modifying database fields and another’s is preparing to develop a feature dependent on those fields, both can exchange plans in advance to agree on modification order, reducing code merging conflicts. Cursor also shared an internal shift handover case: after an engineer’s shift change, the incoming agent already has access to unfinished tasks, pending bugs, and follow-up messages, and ongoing work can be directly handed over to the new agent. In October, a developer complained on the Cursor forum that they could only view their personal agent’s task board and had to ask colleagues individually to check their agents’ work. The new Team Projects version has added these sharing and coordination features. Currently, the multi-user collaboration feature is rolling out gradually, requiring a Cursor team account, a Cloud Agents-supported plan, and version 3.26.13 or later. Each member’s agent usage remains billed separately.