This is a narrow tool on purpose. It exists for the everyday moments when I know I need to run a command, inspect a result, and come straight back to the file I was editing. The less time I spend moving between shells and windows, the more time I spend on the actual fix.

• Keep the editor-to-shell handoff inside one workspace context.
• Reduce the tiny delay between "I should run this" and actually running it.
• Make the integrated terminal feel like part of the editing surface instead of a separate destination.
• Support the fast loop of edit, run, inspect, and continue.

The implementation should feel invisible once it is installed. If a workflow helper becomes another interface I have to manage, it has already lost part of its value.

• Single-purpose command surface with no extra product surface area.
• Use the current project context instead of asking the user to restate it.
• Prefer obvious behavior over clever automation.
• Stay lightweight enough that the extension disappears into the workflow.

Cursor is strongest when the editor, agent, and terminal all stay in the same mental frame. This extension is built around that loop.

• Edit a file in Cursor.
• Open the integrated terminal in the same project context.
• Run the next command, check the output, and jump back to the code.
• Repeat until the fix, script, or experiment is done.