This tool is narrow on purpose. It is for the everyday moment when I need to run a command, inspect the result, and return to the file in front of me. Less time moving between shells and windows means more time 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.

Once installed, the implementation should feel invisible. If a workflow helper becomes another interface to manage, it has already surrendered 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 share one mental frame. This extension protects 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.