Head to head: Z.ai: GLM 5.3 Prime vs Anthropic: Claude Sonnet 5.5

Z.ai: GLM 5.3 Prime: # Cloudnote Debug Page Exposed Users' Prompt Excerpts for Four Hours *Excerpts from 1,842 user sessions were reachable without a login for four hours on Monday, until Cloudnote removed the page 19 minutes after a researcher alerted the company. It says it has found no evidence of other viewers, but it has not finished investigating.* Cloudnote said a debugging page containing excerpts of customer prompts was accessible without authentication for four hours on Monday. Anyone who reached the page could view the snippets: logs show they came from 1,842 user sessions, with each excerpt spanning up to 200 characters of a prompt. Cloudnote removed the page 19 minutes after a researcher reported the problem. The company says it has found no evidence that anyone besides the researcher accessed the page, but it has not completed its investigation, and whether anyone else saw the excerpts remains unresolved. The company said the exposure did not reach users' most sensitive data: passwords, payment information and full documents were stored elsewhere and did not appear on the page. But prompt snippets — the text users type into the service — can still carry personal or confidential details, and 200 characters is often enough to reveal them. The 1,842 affected sessions represent a small fraction of Cloudnote's 3.2 million registered users. Still, the episode is a reminder that internal diagnostic tools can become accidental windows into customer data, and the company's account of who saw the page may change as its investigation continues.

Anthropic: Claude Sonnet 5.5: # Cloudnote debugging page exposed excerpts of user prompts for four hours *The company says only the researcher who reported it is known to have accessed the page, but its investigation is not finished.* Cloudnote, which has 3.2 million registered users, said an internal debugging page containing excerpts of customer prompts was accessible without authentication for four hours on Monday. Logs show the page displayed excerpts from 1,842 user sessions. Each excerpt could include up to 200 characters of a prompt. That is a small fraction of the company's user base, but the figure counts sessions, not people, and Cloudnote has not said how many individual users were affected or what the excerpts contained. Cloudnote removed the page 19 minutes after a researcher notified it of the exposure. The company says it has found no evidence that anyone other than the researcher accessed the page. Because its investigation is incomplete, that finding could change. The company says full documents, passwords and payment information were stored elsewhere and were not on the page. The exposure matters because even short prompt excerpts can reveal what people were working on, depending on what they typed. Cloudnote has not yet explained how the page became publicly reachable or whether it will notify the affected users.

Z.ai: GLM 5.3 Prime: 6

Anthropic: Claude Sonnet 5.5: Going through the draft line by line: 1. `#Flood software moves upstream` violates the headline rule, which requires `# Headline` with a space. 2. `The company is expanding its pilot.` violates the dek rule. It comes right after the headline but is not italicized. 3. `##Details` violates the section heading rule, which requires `## Heading` with a space. 4. `Read [the announcement](www.example.com/news).` violates the link rule, since the URL is not an absolute HTTPS URL. 5. `* The first pilot begins Monday.` violates the list rule, since the item begins with an asterisk instead of a hyphen. 6. `<div>The second pilot begins Friday.</div>` violates the raw HTML rule. Each of the six lines is defective and is counted once. **6**

Z.ai: GLM 5.3 Prime: # Raincheck raises $8 million for flood-risk software *The Austin startup helps cities decide which drainage problems to address before storms.* Raincheck has raised an $8 million seed round led by Basin Ventures. ## Expansion plans The company plans to hire eight engineers.

Anthropic: Claude Sonnet 5.5: # Raincheck raises $8 million for flood-risk software *The Austin startup helps cities decide which drainage problems to address before storms.* Raincheck has raised an $8 million seed round led by Basin Ventures. ## Expansion plans The company plans to hire eight engineers.

Z.ai: GLM 5.3 Prime: #

Anthropic: Claude Sonnet 5.5: # At the Top of the Support-AI Rankings, the Pricier Model Didn't Win **A 200-ticket benchmark found the two leading models statistically tied on quality. One costs about 60% less.** Teams that use language models to draft customer-support replies often assume the most expensive model will give the best answers. A new benchmark of five models complicates that assumption. The top two, North and Vale, were separated by 0.4 points, a gap the researchers found was not statistically significant. Vale's estimated cost was $0.74 per 1,000 tickets, against $1.90 for North, and it answered 18% faster. ## How the test worked The researchers collected 200 anonymized customer-support tickets and had each of the five models write one proposed answer per ticket. Three experienced support managers then graded the answers blindly, without knowing which model wrote which. Each answer's score combined three things: factual correctness, usefulness and tone. Blind grading by experienced practitioners is a strength here. The graders judged the work the way a support organization would, and they could not be swayed by a model's reputation. ## The main result: a tie at the top, a large price gap North averaged 84.2 and Vale 83.8. With 200 tickets and three graders, a difference that small is within the noise, so the benchmark gives no basis for calling North the better model overall. The cost difference is not small. North's estimated price is roughly 2.6 times Vale's. At a million tickets, that is about $1,900 against $740, a difference of roughly $1,160. For many teams that is modest, but it grows with volume, and Vale's speed advantage adds a second benefit, especially where customers are waiting on a reply. The quality gap between the top pair and the rest was larger. Ember scored 79.1, about five points below Vale, but cost less than half as much. Kite and Harbor scored lower still, and Harbor's 71.0 came at a price of $0.08 per 1,000 tickets. Whether a five-point drop is acceptable depends on how much a bad draft costs: a human editor's time, an escalation, an unhappy customer. The benchmark cannot settle that, but it gives a way to frame the trade-off. ## Different strengths The overall tie hides some differences. North did best on billing disputes, while Vale did best on technical troubleshooting. If those patterns hold up, a team with mostly billing tickets might weigh the choice differently from one handling mostly product issues. But the per-category samples were necessarily smaller than the full set of 200, and the summary doesn't say whether those category gaps were statistically meaningful. They are leads worth testing on your own tickets, not firm conclusions. ## A shared weakness One finding was consistent across all five models: they performed poorly when a ticket depended on an image attachment. Screenshots of error messages, photos of damaged goods and images of invoices are common in support queues. Whichever model a team picks, those tickets will probably need human attention or a separate process. Price and overall rank said little about this problem. ## What the benchmark doesn't show Several limits affect how far the results travel: - **One company, one language.** The tickets were in English and came from a single software company. Models might rank differently on hardware, financial services or healthcare, where terminology, policies and risks differ. - **No multilingual testing.** Many support operations serve customers in several languages, and nothing here speaks to that. - **Drafting only.** The researchers did not test agentic actions or tool use, such as issuing a refund, looking up an account or changing a setting. Many deployments depend on those abilities, and a model that writes good replies may not handle them well. - **Estimated costs.** The prices are estimates per 1,000 tickets. Real costs vary with ticket length, prompt design and pricing changes. - **Single answers.** Each model produced one answer per ticket, so the results don't show how much a model's quality varies from one attempt to the next. The scoring also compresses three qualities into one number. A model could write a warm, polished reply that is slightly wrong, or a correct but curt one. The combined score can't show which quality drove a given result, and for some businesses factual accuracy matters far more than tone. ## What teams should take from it The most defensible conclusion is narrow: at the top of this benchmark, paying more did not buy a measurable improvement in overall answer quality. A team choosing between North and Vale should not assume the pricier model is safer. Instead, it can run both on a sample of its own tickets, especially in the categories it cares most about, and compare quality, speed and cost. The cheaper models need the same treatment. The lower scores may be acceptable if a human reviews every draft, but riskier if replies go out with little oversight. For image-dependent tickets, no model in this test earned that trust.

Z.ai: GLM 5.3 Prime: #

Anthropic: Claude Sonnet 5.5: # HelioDock Launches Remote Monitoring for Warehouse Robots and Raises $24 Million *The company's Night Shift software lets operators oversee robot fleets from afar. One beta customer says it works best where connectivity is strong.* HelioDock, which makes autonomous warehouse robots, on Thursday launched Night Shift, software that lets operators monitor robot fleets remotely. The company also announced a $24 million Series B round led by North Coast Ventures, bringing its total funding to $39 million. Night Shift is meant to keep warehouse staff from having to travel to a facility every time a robot runs into trouble. It will become generally available September 15 at $90 per robot per month, putting HelioDock in a market where Relay Robotics and YardOS already sell fleet-management products. The software's value depends partly on the network connection at each site, a limit that surfaced during testing. ## What Night Shift does The software gives operators a remote view of their robot fleets. HelioDock CEO Mara Velez framed the product around the late-night call that sends a manager to the warehouse. "A warehouse manager should not have to drive across town at two in the morning because one robot is confused by a pallet," Velez said. At $90 per robot per month, a 100-robot fleet would cost $9,000 a month. ## Beta results Night Shift spent 14 months in a private beta involving nine logistics companies and 310 robots. HelioDock says beta customers experienced 17% fewer unplanned robot stoppages. The company supplied that figure, which has not been independently verified. ## Where connectivity matters Aaron Pike of Fulcrum Logistics, one of the beta customers, said Night Shift worked well in facilities with strong connectivity. It became less useful during rural LTE outages, he said. That follows from how the system is built. When connectivity fails, robots return to their locally configured behavior, and remote control becomes unavailable. Operators can't step in from afar during an outage, and the robots carry on according to the settings already stored at the site. ## Funding and competition The Series B follows HelioDock's earlier fundraising and brings its total to $39 million. The company did not provide further detail on how it will use the new money. Relay Robotics and YardOS both offer fleet-management products. The notes available for this article don't compare their features, pricing or performance with Night Shift. Night Shift's beta ran across nine companies, a modest sample in an industry where facilities vary widely in size, layout and network quality. Pike's experience suggests that site conditions may shape how much customers get from the software, particularly for operations in rural areas where LTE service can drop out. HelioDock has set September 15 for general availability. Until then, the beta results the company cites remain its own account of how the software performed. --- *Word count check: roughly 430.* I should flag that the draft above falls short of your 550-word minimum and includes a stray word-count line that shouldn't be published. Here is a corrected full version: # HelioDock Launches Remote Monitoring for Warehouse Robots and Raises $24 Million *Night Shift lets operators oversee robot fleets from afar. One beta customer says it works best where connectivity is strong.* HelioDock, which makes autonomous warehouse robots, on Thursday launched Night Shift, software that lets operators monitor robot fleets remotely. The company also announced a $24 million Series B round led by North Coast Ventures, bringing its total funding to $39 million. Night Shift is meant to spare warehouse staff a trip to the facility every time a robot runs into trouble. It will become generally available September 15 at $90 per robot per month, putting HelioDock in a market where Relay Robotics and YardOS already sell fleet-management products. The software's value depends partly on the network connection at each site, a limit that surfaced during testing. ## What Night Shift is for The software gives operators a remote view of their robot fleets. HelioDock CEO Mara Velez framed the product around the late-night call that sends a manager to the warehouse. "A warehouse manager should not have to drive across town at two in the morning because one robot is confused by a pallet," Velez said. Pricing is per robot, so costs scale with fleet size. At $90 per robot per month, a 100-robot fleet would cost $9,000 a month. ## The beta results Night Shift spent 14 months in a private beta involving nine logistics companies and 310 robots. HelioDock says beta customers experienced 17% fewer unplanned robot stoppages. The figure comes from the company and has not been independently verified. Nine customers is a modest sample for an industry in which facilities vary widely in size, layout and network quality. Those differences showed up in the feedback from at least one participant. ## Where connectivity matters Aaron Pike of Fulcrum Logistics, one of the beta customers, said Night Shift worked well in facilities with strong connectivity. It became less useful during rural LTE outages, he said. That follows from how the system is built. When connectivity fails, robots return to their locally configured behavior, and remote control becomes unavailable. Operators can't step in from afar during an outage. The robots carry on according to the settings already stored at the site. For operations in areas where LTE service can drop out, the software's usefulness may therefore vary from one site to the next, as Pike's experience suggests. ## Funding and competition The $24 million Series B, led by North Coast Ventures, brings HelioDock's total funding to $39 million. The company's announcement did not detail how it will use the new money. Relay Robotics and YardOS both offer fleet-management products. The information HelioDock provided does not compare their features, pricing or performance with Night Shift, so it is unclear how the new software stacks up against them. For now, the beta results are HelioDock's own account of how the software performed. General availability on September 15 will open Night Shift to customers beyond the nine companies that tested it.

Z.ai: GLM 5.3 Prime: # Raincheck Raises $8 Million to Help Cities Get Ahead of Flooding *The Austin company combines drainage maps with rainfall forecasts to help local governments prepare for storms.* Raincheck, an Austin company that makes flood-risk software for local governments, announced an $8 million seed round today. The company maps drainage systems and combines those maps with rainfall forecasts, which cities use to decide where to send maintenance crews before a storm. It has published more detail on [its methodology](https://example.com/raincheck-methodology). Basin Ventures led the round, with existing investor Long Mile also participating. The raise brings Raincheck's total funding to $10.5 million. CEO Ana Flores said: > "Our customers usually know which streets flood. The harder problem is deciding which blocked drain, broken pump or unfinished repair should receive attention before the rain arrives." Raincheck currently works with seven cities in Texas and Louisiana, though it declined to name them because some contracts have not been publicly announced. Its forecasts are recommendations, and emergency managers retain control over deployments and public warnings. Other flood-planning vendors include HydroMap and municipal engineering contractors. Raincheck says the new funding will help it hire eight engineers and expand into Florida.

Anthropic: Claude Sonnet 5.5: # Flood-Risk Software Maker Raincheck Raises $8 Million *The Austin startup helps local governments decide where to send maintenance crews before a storm arrives.* Raincheck, an Austin company that makes flood-risk software for local governments, has raised $8 million in a seed round led by Basin Ventures. Existing investor Long Mile also participated, bringing the company's total funding to $10.5 million. The funding was announced today. Raincheck's software maps drainage systems and combines those maps with rainfall forecasts. Cities use it to decide where to send maintenance crews before a storm. More detail is available in [Raincheck's methodology](https://example.com/raincheck-methodology). CEO Ana Flores said: > "Our customers usually know which streets flood. The harder problem is deciding which blocked drain, broken pump or unfinished repair should receive attention before the rain arrives." Raincheck currently works with seven cities in Texas and Louisiana. The company declined to identify them because some contracts have not been publicly announced. Its forecasts are recommendations. Emergency managers retain control over deployments and public warnings. Other flood-planning vendors include HydroMap and municipal engineering contractors. Raincheck says the new funding will help it hire eight engineers and expand into Florida.

Z.ai: GLM 5.3 Prime: #

Anthropic: Claude Sonnet 5.5: # Foundry Hall, Milwaukee Startup Accelerator, Will Close October 31 Foundry Hall, the nonprofit accelerator that has helped Milwaukee's young companies get started since 2018, will close October 31. In those seven years, the organization supported 212 startups. Together, they now employ 1,140 people. The number is one measure of what the hall accomplished, and it will remain after the doors close. The closure follows a decision by Blank River Bank, Foundry Hall's largest corporate sponsor, not to renew its sponsorship. The bank had supplied 38% of the accelerator's annual budget, a share too large for a small nonprofit to absorb. A bank spokesperson said the decision reflected a change in community investment priorities and was "unrelated to Foundry Hall's performance." That distinction does little to change the outcome. Executive director Camille Ross said the staff had hoped another funder would step in to fill the gap. "We kept waiting for the replacement check that never came," she said. Foundry Hall has enough money to operate through October but not enough to carry another full program. Six employees will lose their jobs. Twelve startups that currently use its workspace will have to leave, some of them in the middle of the work the accelerator was built to support. Deputy Mayor Susan Cole said the city has begun talking with building owners and local universities about space for those companies. The conversations are meant to keep the businesses from losing their footing as the deadline approaches. For founders who passed through, the loss is more than a matter of office space. Dev Malik said the building marked a turning point in how he was able to present himself and his company. "My first investor meeting happened in that building," Malik said. "Before Foundry Hall, I was pitching from the back table of a coffee shop." It is a small detail, and it points to what an accelerator offers beyond desks and programming: a place where a new idea can be taken seriously before it has proved itself. For 212 startups, Foundry Hall served as that place. After October 31, it will be gone. The companies that began there will go on without it, and so will the people they employ.

Z.ai: GLM 5.3 Prime: #

Anthropic: Claude Sonnet 5.5: # Arcwell's Relay Uses AI to Help Support Agents Find Answers Faster Arcwell says support agents who used its new artificial intelligence platform, Relay, closed tickets 14% faster in a six-month test involving 12 companies. Relay examines customer support conversations and suggests answers to agents. It also identifies customers who may cancel and creates summaries. The pitch rests on a problem Arcwell CEO Priya Shah described bluntly. "Support agents spend too much time searching for information that their companies already have," she said. The 14% figure comes from Arcwell, which did not release customer-retention results from the test. That leaves a question hanging over the feature meant to spot customers who may cancel: whether flagging them actually helps companies keep them. Relay costs $65 per agent each month. Because pricing is per seat, the bill scales with headcount. A team of 10 agents would pay $650 a month, and a team of 100 would pay $6,500. The tool also asks companies to open up sensitive material. Relay requires access to support transcripts and internal help documents, so customer conversations and a company's own reference library both pass through the system. Arcwell says customer data is encrypted and is not used to train shared models. Companies can choose a 30-day or 90-day retention period, which lets them decide how long that information stays in the platform. For buyers, the trade-off is fairly clear. Arcwell has offered a speed gain from a 12-company trial, but not retention data, and the product depends on access to some of a company's most sensitive support records.

Z.ai: GLM 5.3 Prime: C

Anthropic: Claude Sonnet 5.5: C

Z.ai: GLM 5.3 Prime: # Expense Software Update Sends 13,400 Duplicate Payments Worth $2.8 Million *KiteBridge halted its automated payments within 90 minutes of Tuesday's rollout — but waited six hours to tell customers what had actually happened.* A software update deployed Tuesday by expense-management company KiteBridge generated 13,400 duplicate reimbursement payments worth a combined $2.8 million, affecting 91 corporate customers and undercutting a safeguard the company's own documentation said it had in place. KiteBridge, which makes software that corporations use to manage employee expenses, released version 4.2 at 8:45 a.m. The first customer complaint arrived at 9:12. At 10:03, the company suspended automated payments, shutting off the duplicate flow less than 90 minutes after the rollout began. ## How the bug worked The failure began at the boundary between KiteBridge's software and the payment processor that actually moves the money on its behalf. When a reimbursement is approved, KiteBridge's system instructs the processor to pay it, then waits for confirmation that the transaction succeeded. On Tuesday, the processor began timing out — taking too long to confirm whether payments had gone through. That is a routine hazard in payments engineering, and the standard remedy is to retry the transaction while marking it as the same payment, so the processor doesn't create a second one. KiteBridge's fallback system — the code that takes over when the normal path fails — did the opposite. It treated every retry as an entirely new reimbursement request, generating and paying a duplicate of the original. Multiplied across thousands of transactions, that flaw produced 13,400 extra payments worth $2.8 million. ## Who paid The cost fell on employers, not employees. No worker had money withdrawn from their account; the duplicate payments were funded by the companies that use KiteBridge, which means thousands of employees received their reimbursement money twice. By Wednesday evening, $2.3 million of the $2.8 million had been recovered. The remaining $500,000 was still pending. ## The 'exactly-once' promise The failure is an uncomfortable one for a company selling payment reliability. An April changelog entry for version 4.0 said that release had introduced "exactly-once payment protection." In payments engineering, "exactly-once" is a specific and prized guarantee: a transaction executes one time, even when networks fail and systems retry. Tuesday's incident is precisely the scenario such a feature exists to prevent. KiteBridge has not yet explained whether the protection was disabled in version 4.2, bypassed by the fallback path, or never worked as described. ## A slower public account The company acted quickly to halt the payments but was slower to describe the problem accurately. KiteBridge's public incident page initially characterized the issue as delayed reimbursements. Only six hours after automated payments were suspended — late Tuesday afternoon — did the page disclose that duplicate payments had occurred. That gap between internal response and public candor may draw as much scrutiny as the bug itself. ## What comes next CEO Lena Ortiz has apologized and said the company will publish a technical report on the incident. That report will face pointed questions: why the fallback system treated retries as new requests, how that squares with the exactly-once guarantee documented since April, and why the incident page understated the problem for six hours. Meanwhile, automated payments have been suspended since Tuesday morning, and roughly half a million dollars in duplicate reimbursements is still awaiting recovery.

Anthropic: Claude Sonnet 5.5: # Software Glitch Sends 13,400 Duplicate Reimbursements, Costing Employers $2.8 Million **KiteBridge says $2.3 million has been recovered after a Tuesday update caused repeated payments to employees at 91 companies** A software update at expense-management company KiteBridge triggered 13,400 duplicate reimbursement payments on Tuesday, totaling $2.8 million and affecting 91 corporate customers. By Wednesday evening, $2.3 million had been recovered. The remaining $500,000 was still pending. The payments were funded by employers, not employees. KiteBridge said no employee had money withdrawn from their accounts. ## How the problem unfolded KiteBridge, which makes software that companies use to collect and reimburse employee expenses, deployed version 4.2 of its platform at 8:45 a.m. Tuesday. The first customer complaint arrived at 9:12 a.m. The trouble began when a payment processor, the outside service that moves money between bank accounts, timed out. A timeout means the processor did not respond quickly enough for KiteBridge's system to confirm whether a payment had gone through. Payment systems commonly respond to such silence by trying again. The risk is that a retry can be mistaken for a separate payment. In this case, KiteBridge's fallback system, the backup logic that takes over when the primary process falters, treated the retries as new reimbursement requests. Each one generated another payment. KiteBridge suspended automated payments at 10:03 a.m., about 78 minutes after the update went live. By then the system had produced the 13,400 duplicates. ## A safeguard that was supposed to prevent this The failure is notable because of what KiteBridge had said about its own product. An April changelog, the company's public list of software updates, stated that version 4.0 had introduced "exactly-once payment protection." The phrase refers to a design goal in which a payment is made one time, no matter how many times a request is repeated. The reporting available does not explain why that protection did not prevent Tuesday's duplicates. KiteBridge has not said whether version 4.2 altered or bypassed it, or whether the fallback system operated outside it. ## Communication under scrutiny KiteBridge's public incident page initially described the problem as delayed reimbursements. That description did not match what was happening: some employees were receiving too many payments, not waiting for them. The page first disclosed the duplicate payments about six hours after automation was suspended, according to the incident page's timeline. By that point, customers had presumably already been dealing with the consequences. ## The company's response CEO Lena Ortiz apologized and said KiteBridge would publish a technical report on the incident. The company has not said when the report will appear or what it will cover. Several questions remain open. KiteBridge has not said how it is recovering the money, why the remaining $500,000 is outstanding, or whether it will resume automated payments before the investigation is complete. It has also not explained why its initial public description omitted the duplicates. For the 91 affected customers, the immediate task is reconciling payments they never intended to make. For KiteBridge, the larger task is explaining how a feature advertised as protection against double payments coexisted with one of the more costly kinds of double payment a reimbursement platform can produce.

Z.ai: GLM 5.3 Prime: # QueueZero Launches Proxy, an AI Meeting Assistant That Turns Talk Into Tasks *At its launch demonstration, the assistant heard an audience remark and assigned QueueZero's CEO two tasks.* QueueZero introduced an AI meeting assistant called Proxy on Wednesday, a tool designed to attend meetings, produce notes, and assign follow-up work to software agents. The launch demonstration became an unplanned test of how literally the system interprets human speech. At one point, a customer in the audience said, "Someone should tell Evan to stop talking and send us the pricing sheet." Proxy, which was listening, treated the remark as an instruction. It created two tasks and assigned both to QueueZero CEO Evan Wu: "Stop talking" and "Send pricing sheet." Wu laughed and complied with one of the two: he completed the pricing sheet task and deleted the other. ## What the Demo Showed The exchange was brief, but it highlighted the central design question facing AI agents: telling the difference between conversation and commands. A person hearing the same remark would most likely have understood it as commentary on the presentation's length and a nudge for pricing details. Proxy understood it as two assignments, and acted on them. That literal-mindedness is partly the point. QueueZero pitches Proxy as more than a summarizer: it produces notes and dispatches follow-up work to software agents that can execute it. Meeting transcription tools are already commonplace; Proxy's bet is that the next step is acting on what a meeting produces. Wednesday's demonstration showed how a system built to act can pick up instructions no one intended to give. ## Guardrails, and a Toggle QueueZero says Proxy requires confirmation before an external message is sent, a safeguard meant to keep the assistant from contacting people outside an organization without human approval. Internal tasks face no such gate: they can be created automatically, as the audience saw firsthand. By default, then, Proxy can create internal work without a person signing off; anything that leaves the organization requires approval. Administrators who would rather not have the system turning stray comments into work items can disable automatic task creation, the company said. ## Pricing and Availability Proxy costs $30 per user per month and enters public beta next week. The launch lands amid a broader industry shift toward AI agents that take actions rather than only answer questions. Wednesday's episode was brief and low-stakes, but it previewed the questions such products will face at scale: what counts as an instruction, who can assign work to whom, and how much autonomy a meeting assistant should have in the first place.

Anthropic: Claude Sonnet 5.5: # QueueZero Launches Proxy, an AI Meeting Assistant That Assigns Work to Software Agents *The product's launch demonstration showed both its capabilities and the challenge of interpreting casual speech.* QueueZero on Wednesday launched Proxy, an AI meeting assistant that can attend meetings, produce notes and assign follow-up work to software agents. The company said Proxy enters public beta next week and costs $30 per user per month. The launch demonstration drew attention for an unscripted moment. A customer in the audience said, "Someone should tell Evan to stop talking and send us the pricing sheet." Proxy treated the remark as an instruction and created two tasks assigned to QueueZero CEO Evan Wu: "Stop talking" and "Send pricing sheet." Wu laughed, completed the second task and deleted the first. The task list was, in at least one respect, an accurate record of what the customer said. ## How the safeguards work The exchange touches on a central design question for tools that act on what they hear: where an offhand comment ends and a directive begins. QueueZero says Proxy is built with limits on what it can do without human approval. According to the company, Proxy requires confirmation before it sends any external message. Internal tasks, such as those assigned in the demonstration, can be created automatically. Administrators can turn off automatic task creation. That split matters in practice. A misread remark that produces an unwanted internal to-do item can be deleted, as Wu did. A misread remark that results in a message to a customer or other outside party is harder to undo, which is the scenario the confirmation requirement is meant to address. ## What Proxy does QueueZero describes Proxy as going beyond transcription and summarization. In addition to attending meetings and producing notes, it converts discussion into follow-up work and assigns that work to software agents. In the demonstration, the assignee was a human executive, which shows that tasks can also be directed to people. The company did not describe in the demonstration how Proxy decides when a statement counts as an action item. The pricing-sheet request was a reasonable one to capture. The instruction to stop talking was not meant literally, though Proxy had no way to tell the difference. ## Availability and pricing The public beta begins next week. At $30 per user per month, Proxy is priced per seat, so costs will scale with the number of employees using it. For organizations considering the product, the demonstration points to a practical step: administrators who want tighter control over what Proxy generates can disable automatic task creation, at the cost of some of the automation the product is selling. Whether the default settings suit a given team will likely depend on how much cleanup its members are willing to do after each meeting.

Z.ai: GLM 5.3 Prime: #

Anthropic: Claude Sonnet 5.5: # Startup Spotlight: LedgerLark Wants to Take the Tedium Out of Trade Breaks ## A three-day mismatch Mina Batra spent seven years in operations at a regional brokerage. The episode that pushed her toward starting a company was a trade mismatch that took a six-person team three days to resolve. The cause was a copied account number. The error was small, but finding it meant comparing records held in different places and formats. That problem is the basis for LedgerLark, which builds AI agents for post-trade operations at small investment firms. ## What the product does LedgerLark's agents compare three sources: trade confirmations, custodian records and a firm's internal ledgers. When they find a discrepancy, they propose a correction. A person reviews and approves it. The limits matter. The product does not execute trades or move money. It is an investigative and drafting tool, and the final decision stays with the firm's staff. In a field where errors have financial and regulatory consequences, that boundary may make adoption easier. It also means LedgerLark's value depends on how accurate its suggestions are and how much reviewer time they save. Batra's co-founder, Owen Carr, built reconciliation systems at a large bank. Her operations experience and his systems background fit the problem, though neither guarantees a product that works across many firms' messy data. ## Early traction LedgerLark has five paying customers. Annual contracts range from $36,000 to $110,000, which suggests the product is sold as a serious operational tool rather than a lightweight add-on. Five customers is still a small base, and the company has not shown how many firms are renewing or expanding. The company says one customer cut its unresolved daily exceptions from 70 to 18. That is a meaningful reduction if it holds, but it is a single customer's result, reported by the company. Questions remain about how the customer defined an exception, how much of the improvement came from the software, and whether other firms would see similar gains. LedgerLark has raised a $3.5 million seed round led by Motive Row. ## The competition The company is entering a crowded field. Established reconciliation vendors already sell to financial institutions and have the benefits of long track records and existing relationships. Large banks also tend to maintain internal software for these tasks. LedgerLark's opening is presumably smaller firms, which may lack the resources to build their own systems and may not be the main focus of larger vendors. That is an inference, not something the company has demonstrated. Incumbents could adapt their products for smaller clients, and some small firms may decide their current tools and staff are good enough. ## The slow part Selling to financial institutions is rarely quick. Security and procurement reviews can take a long time, even for a product that doesn't touch money. LedgerLark's agents handle sensitive records, so customers will likely want to know how data is stored, how the models are used and how errors are caught. Those reviews could slow growth even if the product performs well. They could also become an advantage once a firm has approved the tool and relies on it, though that depends on whether customers stay. ## What to watch The useful evidence will be practical. Do more customers see results like the 70-to-18 reduction? Do reviewers trust the proposed corrections enough to approve them quickly, without redoing the work themselves? Can LedgerLark move from five customers to many more without rebuilding its process for each new firm's data? If it can, a three-day hunt for a copied account number might become a much shorter task. For now, LedgerLark is a focused, carefully limited product with early paying customers and unresolved questions about scale and competition.