What it is
The IDE plugin brings LoneAct conversations and Agent execution into the editor sidebar. You can open a project, start tasks, review tool results, and continue the last conversation without leaving your code.
VS Code family
Works with VS Code and compatible editors; sign in with your LoneAct account after installing.
JetBrains family
Works with IntelliJ IDEA, PyCharm, GoLand, WebStorm, and other JetBrains IDEs.
Editor context
Open a conversation from the current project so the Agent works around the code you are viewing.
Install and sign in
Install the plugin
Install the LoneAct plugin from your IDE's marketplace, or use an organization distribution package.
Open a project
Open a real project root first, then start the LoneAct panel. Do not use your home directory as a substitute when no project is open.
Sign in and confirm the local service
Complete sign-in and confirm that the current model and the local LoneAct service connection are healthy.
Start the first task
Open a conversation from the sidebar, choose a model, describe the goal, and approve tool calls step by step.
If the plugin panel does not appear, or capabilities look incomplete after an update, restart the IDE once and check the plugin status again.
Review results inside the editor
| Capability | Experience |
|---|---|
| File changes | Agent edits appear as diffs and are applied to the workspace after you confirm |
| Terminal commands | Commands that need approval appear in the conversation, and results return to the same session |
| Project team | The same Agent Team and memory as Local Web, not rebuilt because the entry point differs |
| Context | The editor supplies information about the current project and open files, reducing repeated explanations |
Boundaries and guidance
- The IDE plugin still relies on the LoneAct service on your computer to execute tools; the plugin panel is not a separate execution engine.
- Do not start an Agent without an open project; an empty workspace produces wrong paths or unavailable tools.
- Rules, skills, and Secrets shared by a team belong in project or organization configuration, not in personal IDE settings.
- When you need full split panes and project or team overview, use Local Web or the cloud Workbench.