IDE

NextOS can work alongside an editor instead of replacing it. The goal is to let the agent understand the code you are looking at while you keep normal editor habits.

What IDE context adds

• Active file and selection context.
• Faster file references through @ search.
• Better prompts for focused changes.
• A bridge between manual editing and agent-driven edits.

Suggested workflow

1. Open a file or select a relevant range.
2. Ask a narrow question: “Explain this reducer” or “Make this component handle empty state.”
3. Review the diff in your editor.
4. Ask NextOS to run the smallest relevant test.

Keep prompts grounded

Instead of asking “fix the app,” point at the part of the app you are inspecting.

Use the selected component as context. Add the loading state without changing the surrounding layout.

For larger tasks, keep the desktop workspace open for task progress and permissions while using the IDE for diff review.