`1Password` adds OpenAI Codex integration for runtime-only secrets

// related

• #0001

  #0001Agents & toolsGoogle AI Forum3 hours ago

  `Antigravity` Paid Plan Gemini Quota Reset, Ongoing Cap Up **3x**

  70radar

  AntigravityAI coding-agent IDE — Gemini-powered development workflow

  Paid users get a weekly reset plus a larger running cap. Useful for heavier agent runs, though tier details are still thin.

  • —Paid Antigravity plans received a Gemini quota reset for the week, removing short-term blocked usage immediately.
  • —The ongoing quota is now 3x higher, which makes multi-step coding-agent sessions less likely to stall mid-task.
  • —No tier-by-tier quota numbers or billing changes are included. Treat this as a practical capacity bump, not a pricing model change.

  Source: discuss.ai.google.dev/t/big-thanx-reset-and-increased-3xRead original →
• #0002

  #0002Agents & toolsGoogle AI Forum6 hours ago

  `Antigravity` `2.0.2` patch still unreleased after broken 2.0 rollout

  60radar

  AntigravityAI coding IDE — split agent manager and IDE architecture

  The emergency fix is not out yet. 2.0/2.0.1 split the IDE and agent manager, breaking launch paths, storage, WSL, and remote workflows. Hold upgrades unless you can absorb migration work.

  • —2.0/2.0.1 changed Antigravity from one AI IDE into a standalone agent manager plus separate IDE, creating a messy migration surface.
  • —Installer behavior hijacked the IDE executable for some users, so launching the editor opens the agent app instead. Upgrade rollback risk is real.
  • —Old conversations and workspaces are not migrated by default because the new IDE uses a different storage path. Manual data copy is the current workaround.
  • —WSL and Remote SSH are broken in the main app, with Windows filesystem fallback causing dev environment drift and token waste during setup.

  Source: discuss.ai.google.dev/t/antigravity-2-0-2-changelog/1468Read original →
• #0003

  #0003Agents & toolsGeekNews10 hours ago

  GitHub confirms 3,800 repositories compromised via malicious `VS Code` extension

  60radar

  A single developer workstation became the entry point. VS Code extension trust is now part of supply-chain security, so extension audits are worth doing now.

  • —About 3,800 internal repositories were affected after one employee installed a trojanized VS Code extension.
  • —GitHub’s current assessment limits exposure to internal repositories, but compromised developer endpoints can still leak secrets and code context.
  • —The extension was removed from VS Code Marketplace, infected endpoints were isolated, and incident response started immediately.
  • —Practical takeaway: review installed IDE extensions, publisher names, permissions, and disable unused tools before they become build-chain risk.

  Source: news.hada.io/topic?id=29731Read original →