Check Python dependencies and exposed credentials

  • Two Microsoft agent-framework releases steal credentials at Python startup — Developers using the affected package should remove those versions and rotate credentials accessible to the environment.
    • Socket’s November 17 investigation identifies compromised PyPI releases agent-framework 1.26.1 and 1.26.2. PyPI is Python’s package registry.
    • Both releases install .pth startup hooks, files Python processes when starting normally. The credential collector can therefore run before an application explicitly imports the framework.
    • The reported payloads read secret-bearing environment variables, credential files and other processes’ environments. They also request fresh Azure identity tokens; version 1.26.2 adds GitHub Actions identity-token requests.
    • Socket lists the malicious files and their SHA-256 fingerprints, identifiers for checking exact file contents. Removing the package alone leaves previously stolen credentials usable.
    • Separately, the ONNX Runtime repository, its public GitHub API record and Microsoft’s Agent Framework repository returned HTTP 404 during this morning’s checks.
    • The ONNX Runtime website remains accessible. The repository outage alone supplies no evidence that installed ONNX Runtime packages contain these payloads.
    • Caveat: The package findings are Socket’s technical analysis, and a common cause linking the unavailable repositories remains unverified. (HN 350 points · 74 comments · linked Socket disclosure · direct repository checks)

Office applications move inside Copilot

  • Microsoft brings editable Office files into Copilot — Organizations get broader document creation and delegated work, with availability and claimed savings requiring separate checks.
    • Ars Technica reports that Word, Excel and PowerPoint are generally available inside Copilot. Generated files remain editable in their respective applications.
    • An agent is a model running a multi-step task with tools. Microsoft’s Autopilot lets users delegate ongoing responsibilities, with administrator permissions, activity records and approval requests for some actions.
    • Microsoft’s November 17 Cowork update makes app building and its managed runtime generally available. Automatic effort adjustment and parallel assistants remain in Frontier, its early-access program.
    • Agent 365 Business Analytics begins rolling out through Frontier. Launch access for Microsoft-service analytics requires at least 50 Microsoft 365 Copilot licenses; broader access is planned by mid-December.
    • Its assisted-hours and dollar-value figures combine typical task duration with AI’s estimated contribution. Spending and estimated productivity are different measures.
    • Caveat: The dashboard’s estimated assisted hours are not a direct measurement of employee time saved. (Techmeme · Ars Technica · Microsoft release and analytics documentation)

Measure the full cost of shorter conversations

  • Removing old conversation details can make coding assistants cost more paper notes → — Count reused input, fresh input and generated output separately before assuming a smaller prompt means a smaller bill.

    • Huawei researchers study more than 20,000 runs across seven downloadable models and several coding tests. Tokens are the pieces into which models divide text.
    • Prefix caching reuses the unchanged beginning of a prompt. Removing earlier material can invalidate that reuse and make the following material expensive to process again.
    • On 201 fresh tasks, keeping only the latest ten command outputs increased calculated cost by 116% for Qwen3.6-27B and 87% for Qwen3-Coder.
    • Those estimates price reused input at one-tenth of fresh input and output at four times fresh input. Without the reuse discount, the same runs cost 19% and 25% less.
    • Supplying retrieved code reduced reading and searching by 18–34% in the main experiments, but raised cost by 33–42% without an established improvement in fixes.
    • Concurrent test conditions can reuse each other’s cached prompts, distorting comparisons. Quality scores can omit staged changes, although token-cost measurements are independent of patch scoring.
    • Caveat: These are repriced experimental runs, not measured provider bills, and results vary with the model, surrounding software and pricing. (arXiv 2611.22238 · submitted November 17)
  • Stopping coding assistants after passing tests saves money with risks paper notes → — Evaluate intermediate patches against independent checks before turning an early-stopping rule into policy.

    • The same team examines about 6,000 runs across eight locally served models and two software setups. Tests use bounded budgets and disable extended reasoning where supported.
    • Hidden tests grade intermediate patches without showing those answers to the assistant. On 386 new Qwen3.6-27B runs, stopping after two passing tests on an unchanged patch saved 22.8% in calculated cost.
    • The fixed-task success rate fell one percentage point. That comparison failed its statistical requirement to rule out a loss exceeding two percentage points.
    • Training the model to imitate the stopping rule saved about 30% across six training seeds, while preserving quality remained uncertain.
    • An audit found that omitted staged changes had distorted earlier scores. Matching final reconstructed patches still leaves intermediate-state accuracy to check.
    • Caveat: Passing an assistant’s own tests does not establish that its patch meets the task’s independent correctness checks. (arXiv 2611.22901 · submitted November 17)

Keep reusable instructions current

  • Outdated saved instructions can make assistants worse than starting fresh paper notes → — Check saved paths, field names and procedures against the current environment, even when tasks still finish successfully.
    • The USC and AWS study tests Opus 4.7 and Haiku 4.5 across four settings. Skills are reusable packages of instructions, code and reference material.
    • After controlled changes, saved instructions sometimes lowered scores by more than ten percentage points. In one simulation, Opus needed 38.9% more steps than without saved instructions.
    • The proposed maintenance method replays checks from successful executions without model calls. Detected conflicts can trigger model-assisted repair, validation or a complete rebuild.
    • Haiku’s tax-form field accuracy rose from 30.5% with stale instructions to 97.5% after maintenance. On a simulated science task, maintenance reduced steps by up to 37%.
    • Tax-form token savings repay maintenance after roughly 21–42 uses compared with abandoning the skill. This excludes environment-computing costs and assumes no further maintenance during that period.
    • Caveat: The study tests two related models and controlled changes, rather than repeated maintenance through a changing production system. (arXiv 2611.22525 · submitted November 17)

Faster checks for repositories receiving more generated code

  • StarSling launches runners that propose improvements to automated checks — Teams can inspect its public optimization skills before paying for hosted infrastructure or granting repository access.
    • StarSling’s November 17 HN launch pairs GitHub Actions runners with assistants that analyze workflows, execution records and machine measurements. Proposed improvements arrive as pull requests for review.
    • Its MIT-licensed skills separate elapsed waiting time from total runner-minutes. The latter measures billed computing across jobs running concurrently.
    • The repository’s configuration checker runs offline. Its speed analysis reads GitHub run history, while the audit skills leave proposed fixes in the working tree for review.
    • A Better Auth example removes repeated cleanup of already-deleted rows. Its reported test-job speedups range from 1.2 to 5.4 times; that patch merged September 3.
    • The current service documentation says optimization pull requests are available on paid plans and disabled by default for new accounts.
    • Caveat: The speedups are project-specific vendor measurements, and the historical example is evidence for the method rather than a newly merged fix. (HN 82 points · 39 comments · launch discussion · source repository and reviewed example)

Full execution records still need independent scrutiny

  • Auditors miss planted research sabotage even with full execution records paper notes → — Saving every action helps investigation, but a complete record alone offers weak assurance that an experiment’s conclusion is sound.
    • Redwood Research’s team used one human researcher to produce ten honest and twelve sabotaged research records across ten questions. Twenty-five auditors completed 104 reviews.
    • Human auditors had 90 active minutes per review, AI assistance and permission to rerun experiments. They fully identified 17.4% of planted mechanisms on average, weighting each mechanism equally.
    • Their ability to rank sabotaged records above honest ones scored 0.59, where 0.5 means chance. The 95% uncertainty interval spans 0.37–0.77.
    • Fable 5.1 fully identified 31.8% of mechanisms without running experiments. Its apparent advantage over humans remained statistically uncertain.
    • The saboteur knew the honest results before constructing attacks. The paper’s research-material access route is a request form, rather than a directly downloadable public archive.
    • Caveat: This measures detection of human-planted sabotage under one protocol, not how often deployed AI systems attempt sabotage. (arXiv 2611.21832 · submitted November 16)
All gathered items - what was cut and why (12)