GitHub Copilot in NetBeans: Current Support and Safe Alternatives
GitHub Copilot does not have an official NetBeans plugin. Here is how to check the current support status, which editors do have Copilot support, and how to keep your task record through a supported connected assistant.
Updated 4 min read
GitHub Copilot does not have an official plugin for Apache NetBeans. GitHub publishes plugins for VS Code, Visual Studio, JetBrains IDEs, Neovim, and Xcode, but NetBeans is not on that list. If you prefer NetBeans for Java or PHP work, you can still use Copilot by opening those projects in a supported editor, and a tool like fenbs lets you keep your task record available regardless of which editor or AI assistant you use.
This guide explains how to check the current support status, which options are available to NetBeans users, and how to keep project context through a supported connected assistant.
How to check current NetBeans support
The authoritative source for supported editors is GitHub's Copilot documentation. Check GitHub's Copilot documentation (opens in a new tab) under "Getting started" or "Supported IDEs" for the current list. This list can change: GitHub has added new editors over time, and the status for a given editor may differ by Copilot feature.
You can also check the Apache NetBeans Plugin Portal and the NetBeans community forums for community-maintained plugins. These are not supported by GitHub and their reliability varies. A community plugin may work for completions but not chat, or it may break when either NetBeans or Copilot updates.
What to do when your preferred editor is unsupported
The most straightforward path is to open the same project in a supported editor. VS Code handles Java and PHP projects, integrates well with Maven and Gradle, and has the GitHub Copilot extension available in one click. JetBrains IDEs (IntelliJ IDEA for Java, PhpStorm for PHP) are also fully supported and offer a more complete refactoring experience than VS Code for some Java workflows.
You do not need to switch editors permanently. Many developers keep NetBeans for specific tasks and open VS Code when they want Copilot assistance. The project files on disk are shared; the editor is just how you view and edit them.
For a comparison of Copilot with other coding assistants, see GitHub Copilot vs ChatGPT. For licensing requirements before setting up a second editor, see GitHub Copilot license.
Setting up VS Code alongside NetBeans for a Java project
Opening a Java project in VS Code for Copilot sessions is straightforward. Install the Extension Pack for Java, which bundles language support, Maven and Gradle integration, and a debugger. Then install the GitHub Copilot extension and sign in. Both extensions are available from the VS Code Extensions panel.
The project folder on disk is the same whether you open it in NetBeans or VS Code. Neither editor modifies files the other cannot read, and the build system (Maven or Gradle) is independent of both. You can commit from either IDE using Git, and the repository treats both as the same working directory.
A few NetBeans-specific files live in the nbproject/ folder. VS Code does not use them, but they do not interfere with VS Code either. Adding nbproject/ to .gitignore is common in projects that work across multiple editors. Check whether your project's .gitignore already excludes them before making a change.
For PHP work in NetBeans, the same principle applies: open the project in VS Code with the PHP Intelephense extension and GitHub Copilot. The PHP files are shared on disk; VS Code and NetBeans can both operate on the same project without conflict. If you use Composer for dependency management, VS Code reads the composer.json and vendor/ directory the same way NetBeans does, so Copilot has access to the same type information.
Keeping your task record independent of the editor
When you move a project between editors, the code is portable. What is less portable is the work context: what task is in progress, what the next step is, and what decisions have been made about the code. If that context lives only in a chat with one assistant in one editor, it does not survive the move.
Keeping the task record in a separate tool means you can open a project in any supported editor, connect an AI assistant, and ask it to read the current tasks and rules. The assistant starts from the same context regardless of which editor or which AI tool you used last.
Keep your project context through editor and assistant changes
Add the project's current tasks, decisions, and rules to fenbs. When you open the project in a supported editor with a connected assistant, ask it to read the project context first. The work record is independent of which editor you use, so switching from NetBeans to VS Code for Copilot does not mean re-explaining the project.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account and add a project for the Java or PHP work you are doing in NetBeans.
- Write the current tasks and their status. Note any decisions about the code structure, approved libraries, or conventions the team follows.
- Set up a supported editor such as VS Code or a JetBrains IDE when you need Copilot assistance.
- Connect your AI assistant over MCP from Integrations. Ask it to read the project context before starting work, so it knows the current tasks and rules.
- Continue recording progress in fenbs so the context stays current when you switch back to NetBeans or any other tool.
fenbs does not require you to use a specific editor. It works as the persistent task record that sits behind your development setup, accessible to any connected assistant. See GitHub Copilot memory for how Copilot's own memory features work when you do use a supported editor.