Quick Verdict
Anahata ASI Studio is a stateful Java agent running inside the Apache NetBeans JVM. It goes beyond completion and chat: a model can inspect IDE and project context, change Java ASTs, invoke NetBeans refactoring and Maven operations, and compile generated Java inside the IDE process through a custom classloader. It also exposes host shell, process, screen, audio, Chrome, and Firefox tools. Plugin Portal listed version 1.0.0 for NetBeans 30 and declared Apache Software License 2.0 by the July 21, 2026 cutoff.
This depth creates unusual capability and unusually high host risk. Generated code executes in the IDE JVM, shell tools launch local commands, browser tools act in sessions, and project tools can modify files and run builds. Prompt, Always, and Never permissions are useful controls but not a sandbox. Jeddict AI Assistant is a distinct, more conventional contextual assistant; Anahata is a high-privilege acting agent.
Best For
- Advanced NetBeans, Java, Maven, and plugin developers
- Researchers testing autonomous edit, compile, and validation loops in isolation
- NBM developers needing deep NetBeans API, AST, refactoring, and diagnostic access
- Security-aware teams able to review each tool call and restore the environment
- Not for production workstations, credential-rich hosts, beginners, or policies forbidding model-generated execution
Key Features
- In-JVM execution: compiles, loads, and runs generated Java in the active NetBeans JVM
- Java and refactoring tools: AST edits, imports, type indexes, Javadoc, native refactoring, and compiler alerts
- Maven and project control: dependency search, POM changes, goals, projects, actions, and output
- Shell and browser automation: host commands plus Chrome and Firefox navigation, forms, clicks, and scripts
- Stateful sessions: Kryo persistence, CwGC context management, Flight Recorder, and backups
- Multiple providers: OpenAI, Anthropic, Google, Hugging Face, MiniMax, and compatible endpoints
Use Cases
- Analyze a Java type graph, run native refactors, and respond to compiler diagnostics
- Prototype NetBeans APIs or Swing code by compiling temporary Java in the IDE process
- Fetch Maven dependency sources and Javadoc for architectural investigation
- Run builds, inspect output, and diagnose IDE or plugin failures
- Test shell or browser actions only on isolated, low-privilege systems without production accounts
Pricing
The precompiled Plugin Portal build is downloadable, and the project primarily requests donations and offers support rather than publishing a standard subscription. Licensing needs careful review. The repository LICENSE and Plugin Portal declare Apache License 2.0. The project also publishes ASL V108, saying open-source projects use Apache 2.0 while proprietary closed-source integration requires a commercial license obtained through a donation of any amount.
Those statements can create interpretive conflict around the standard Apache grant, especially for the precompiled plugin, internal commercial use, redistribution, and closed-source integration. An enterprise should obtain written clarification from the maintainer and legal review rather than infer rights from one page. Model providers, hosted endpoints, and support can add separate costs.
Pros
- Exceptionally deep NetBeans, Java AST, Maven, type-index, and refactoring integration
- A closed loop across perception, editing, compiler feedback, and execution
- Visible and editable tool calls with Prompt, Always, and Never controls
- Stateful sessions, context management, recordings, and backups aid traceability
- Apache-2.0 declarations are present in both the source repository and Plugin Portal
Cons
- Generated Java runs inside the IDE JVM and can damage the process or user environment
- Shell, process, browser, screen, and network access expand prompt-injection and credential risk
- Confirmation controls reduce accidental execution but provide no hard isolation
- ASL V108 commercial language coexists with Apache declarations, requiring clarification for binaries and commercial use
- Small adoption and validation footprint compared with mainstream coding assistants
Alternatives
| Tool | Best for | Main difference | Risk or tradeoff |
|---|---|---|---|
| Jeddict AI Assistant | NetBeans completion and contextual chat | Broader assistant-style provider workflow | Less autonomous and less deeply executable |
| GitHub Copilot | Teams prioritizing maturity and administration | Larger ecosystem and enterprise controls | Less NetBeans-native agent depth |
| Claude Code | Terminal-agent developers | Mature repository and command workflow | Still has shell risk, but does not reside in the IDE JVM |
| Cursor | Users adopting an AI-native editor | Complete multi-file and agent experience | Requires changing editors |
FAQ
Are Anahata ASI Studio and Jeddict the same product?
No. They are independent projects. Anahata focuses on a stateful agent, NetBeans APIs, JVM execution, and high-impact tools; Jeddict focuses more on completion, chat, providers, and conventional development assistance.
Does Anahata execute AI-generated code?
Yes. Its documented JIT tools compile and run generated Java inside the NetBeans JVM using project output, dependencies, and IDE APIs.
Do confirmation dialogs make it safe?
No. They reduce unintentional actions but do not isolate the process, filesystem, network, or credentials. Use a dedicated VM, low-privilege account, and snapshots.
Is Anahata Apache 2.0 licensed?
The repository license and Plugin Portal say Apache 2.0, while ASL V108 adds a commercial-license path for proprietary integration. Enterprise users should obtain written clarification.
Can a company use the precompiled plugin for free?
The public materials do not clearly reconcile internal commercial use, binary redistribution, and proprietary integration. Legal review should rely on written maintainer confirmation, not assumptions from the download page.
Should I install it on my main workstation?
Not initially. Evaluate it in a dedicated VM without production keys, customer code, or logged-in browser profiles.
Bottom Line
Anahata ASI Studio is differentiated by what it can do, not by another chat panel: invoke AST, refactoring, Maven, shell, and browser tools and execute Java inside the IDE JVM. Its blast radius therefore resembles a local developer account. Serious evaluation requires isolation, least privilege, per-action review, rollback, and written licensing clarification. Use the separate Jeddict page when a more conservative NetBeans assistant is sufficient.