`hollow-agentOS`: an agent runtime that writes and registers its own tools

Instead of freezing an agent to a preset tool list, this runtime lets it generate missing scripts and API wrappers, test them, then keep them as permanent skills. Interesting if you want longer-running coding agents, but the real question is whether the self-tooling loop stays stable under messy real work.

[ KEY POINTS ]

A built-in Tool Factory lets the agent create missing utilities on demand, then register them so future runs inherit those capabilities.
Memory is split through a vector layer to fight context decay, so long sessions surface only task-relevant state instead of dragging full history.
A Reviewer and Coder pair must agree before larger changes land, adding a lightweight safety check to autonomous edits.
The repo is open source and explicitly asks for stress-testing around self-tooling, so it is closer to an experimental runtime than a polished product.

Originalwww.reddit.com/r/ClaudeAI/comments/1t29fq6/i_left_my_agent_os_running_overnight_and_it_built/Read original →

// related

#0001
#0001Agents & tools Google AI Forum2 hours ago
`Antigravity 2.0` Drops Integrated IDE Workflow
50radar
AntigravityAI coding tool — IDE-style workflow discussed on Google AI forum
The main app lost editor, terminal, and source control flow. Update only after checking whether your daily coding loop survives the split.
- Reports mention the editor workflow missing after Antigravity 2.0; that turns a coding agent into a slower app handoff.
- The IDE opens the wrong app, so project context switching becomes a real friction point during edits.
- No terminal or source control in the main app means core dev loops are split across tools.
Source: discuss.ai.google.dev/t/antigravity-2-0-removed-the-inteRead original →
FIG-0011:1
50radar
FIG-0011:1
#0002
#0002Agents & tools GeekNews2 hours ago
GitHub Internal Repos Accessed After Employee Device Compromise
40radar
A poisoned VS Code extension became the entry point. Treat editor extensions as supply-chain risk, not convenienceware.
- Attack path: a compromised employee endpoint via malicious VS Code extension, followed by access to internal repositories.
- GitHub removed the malicious extension version and isolated the endpoint. Extension version pinning and review matter for dev machines.
- No concrete customer-impact detail is available in the provided text. Actionable takeaway stays limited to workstation hardening.
Source: news.hada.io/topic?id=29703Read original →
FIG-0021:1
40radar
FIG-0021:1
#0003
#0003Agents & tools Google AI Forum2 hours ago
`Antigravity 2.0` Install/Update Bug Workaround: Roll Back to `1.23.2`
40radar
AntigravityAI coding agent IDE — integrated with Google tooling
Rollback first, then disable background updates. Until the installer stabilizes, manual updates are the practical path.
- Download 1.23.2 from previous releases instead of installing 2.0; this is a rollback workaround, not a permanent fix.
- After opening Antigravity, go to Editor Settings > Application > Update and disable Windows Background Updates.
- Switch update mode to Manual Mode and restart. This avoids being pushed back into the broken update path.
Source: discuss.ai.google.dev/t/solution-for-antigravity-2-0-insRead original →
FIG-0031:1
40radar
FIG-0031:1

`hollow-agentOS`: an agent runtime that writes and registers its own tools

// related

`Antigravity 2.0` Drops Integrated IDE Workflow

GitHub Internal Repos Accessed After Employee Device Compromise

`Antigravity 2.0` Install/Update Bug Workaround: Roll Back to `1.23.2`