GitHub Copilot for Sublime Text: Options and Limits
GitHub Copilot does not have an official Sublime Text plugin. Here is what options exist, which editors offer full official support, and how to keep your project context available through a supported client.
Updated 4 min read
GitHub Copilot does not publish an official plugin for Sublime Text. GitHub's published integrations cover VS Code, Visual Studio, JetBrains IDEs, Neovim, and Xcode. Some community projects exist for Sublime Text, but they are not maintained by GitHub and their feature coverage is incomplete. Tools like fenbs let you keep the project brief and current decisions available to a connected assistant regardless of which editor or tool you use.
This guide covers what to check, what community options exist, which alternatives offer full official support, and how to keep your project context portable.
Is there an official Copilot plugin for Sublime Text?
No, not as of the date this was written. Check GitHub's Copilot documentation (opens in a new tab) under the supported editors section to see whether that has changed. GitHub has expanded its editor support over time, and a future update may add Sublime Text.
Package Control, Sublime Text's package manager, does list some AI-related packages. Search there and read the package's documentation carefully to understand what it does and does not support. A package that provides completions may not support Copilot chat, and a package that worked last year may not be maintained against current Copilot API changes.
Community plugin options and what to check
Before installing a community plugin, check four things: when it was last updated, whether it has open issues reporting broken functionality, whether it requires a personal access token rather than the standard OAuth sign-in, and whether it stores credentials on disk in a way you are comfortable with.
A plugin that requires you to paste a token into a config file carries a different risk profile than one that uses GitHub's standard sign-in flow. Read the plugin's README and the setup instructions in full before installing. Community plugins can be useful, but the security and reliability standards are not the same as a first-party plugin.
Editor alternatives with full official support
If you want Copilot completions and chat without worrying about plugin maintenance, VS Code is the most common choice. It is free, runs on Windows, macOS, and Linux, handles the same project types as Sublime Text, and has the GitHub Copilot extension in one click. Many Sublime Text users keep both editors installed and open VS Code when they want Copilot assistance.
Neovim is another officially supported option for users who prefer a keyboard-driven editor. The GitHub Copilot plugin for Neovim provides completions. For a more feature-complete AI coding experience, VS Code remains the most directly comparable to Sublime Text in terms of workflow.
For a comparison of Copilot with other assistants, see GitHub Copilot vs ChatGPT. For licensing, see GitHub Copilot license.
AI assistants that work without an editor plugin
Some AI assistance does not require an editor plugin at all. The GitHub Copilot CLI, for example, runs in the terminal and explains commands or generates shell scripts. Claude Code and similar tools run as terminal processes that read and write files in your project directory regardless of which editor is open. These approaches let you get AI help on a Sublime Text project without switching editors for each task.
The trade-off is that terminal-based assistants do not see the cursor position or the specific code you are looking at the way an inline editor extension does. They work from the files on disk, which means you describe what you want in a message rather than accepting an inline completion. For some tasks, particularly longer code generation, refactoring, or explanation, this works just as well. For quick line-by-line completion while typing, an editor extension is more fluid.
Keeping the project brief through a supported client
When you switch from Sublime Text to VS Code for Copilot work, you move between tools but the project does not change. The risk is that work context gathered in one environment does not reach the next one: a decision made in a Copilot chat session stays in that chat.
Keeping the project brief, current decisions, and active tasks in an external record means any connected assistant can read the same context whether you are using VS Code, Neovim, or any other supported tool. The record travels with the work, not with the editor.
Keep your project brief available through any supported client
Add the project's goals, decisions, and current tasks to fenbs. When you open a supported editor with Copilot or another connected assistant, ask it to read the project context first. The rules and next steps are available regardless of which editor you use, and decisions made in one session do not get lost when you switch tools.
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 work you are doing in Sublime Text.
- Write the project's current goals, conventions, and active tasks as context notes and Decisions and rules.
- Open a supported editor such as VS Code when you need Copilot assistance for this project.
- Connect your AI assistant over MCP from Integrations and ask it to read the project context before starting.
- After each session, update the project's tasks and Where we left off so the record stays current.
fenbs does not require you to give up Sublime Text for editing. Use Sublime Text for the work it does well and a supported editor for Copilot sessions. Keep the task record in fenbs so nothing depends on which window is open. See GitHub Copilot memory for more on what Copilot itself retains between sessions.