`HyperResearch`: Open-source deep research harness for `Claude Code`

A Reddit post introduces HyperResearch, an open-source skill harness that turns Claude Code into a generalized deep-research agent. For indie developers, the main appeal is low marginal cost by using an existing Claude Code subscription, plus persistent research memory, fact-checking, and broader crawling via crawl4ai.

[ KEY POINTS ]

Targets agentic research workflows with a claimed 16-step pipeline for breadth, depth, fact-checking, and adversarial review.
Positioned as a single-command install open-source alternative to paid deep-research products from OpenAI and Gemini.
For indie developers, the value proposition is cost efficiency and reusable session knowledge for tasks like market research, stock analysis, and competitor analysis.
Risk to note: performance claims such as beating other offerings on `DeepResearch Bench` are presented in the post and are not independently verified here.

Originalwww.reddit.com/r/ClaudeAI/comments/1sz9ib0/converting_claude_code_into_the_most_intelligent/Read original →

// related

#0001
#0001Agents & tools Google AI Forum50 minutes ago
`Antigravity` extension install and skill/plugin management issues reported
50radar
AntigravityAgentic development IDE — skill and plugin based workflows
Clean installs can fail to import VS Code extensions, and old skills need directory reshaping. The bigger tax is context pollution: plugins cannot be toggled off yet.
- VS Code extension import can fail on a clean Windows install; renaming ~/.antigravity to antigravity-ide is the stated workaround.
- Old global skills are recognized but hidden from the global skill list because Antigravity does not recursively scan skill folders.
- Skills now sit in plugin chunks; matching .gemini/config/plugins/science structure makes them appear as plugin:science.
- Plugins cannot be enabled or disabled, so every skill collection keeps adding context. That is a real cost for small-agent setups.
Source: discuss.ai.google.dev/t/more-antigravity-issues/145875Read original →
FIG-0011:1
50radar
FIG-0011:1
#0002
#0002Agents & tools Google AI Forum2 hours ago
`Antigravity IDE` update migration can fail on existing `mcp_config.json` symlink
40radar
Antigravity IDECoding-agent IDE — built around Google's Gemini ecosystem
Auto-update may break project access when the migration hits an existing symlink. Check the config path before updating; the blast radius is narrow but painful.
- Failure happens during the move from ~/.gemini/antigravity to ~/.gemini/antigravity-ide; existing mcp_config.json symlink triggers EEXIST.
- Reported on macOS darwin-arm64 while updating to 2.0.1; the wizard aborts mid-migration and blocks existing project opens.
- Practical workaround: inspect or remove the destination symlink before update. The app needs overwrite/unlink handling in its copy step.
Source: discuss.ai.google.dev/t/antigravity-bug-report-ide-wizarRead original →
FIG-0021:1
40radar
FIG-0021:1
#0003
#0003Agents & tools Google AI Forum3 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-0031:1
50radar
FIG-0031:1

`HyperResearch`: Open-source deep research harness for `Claude Code`

// related

`Antigravity` extension install and skill/plugin management issues reported

`Antigravity IDE` update migration can fail on existing `mcp_config.json` symlink

`Antigravity 2.0` Drops Integrated IDE Workflow