Opening a whole detailed panel for every quick choice makes work heavy. Fitting every input and explanation inside a small menu makes it hard to read. Northstar assigns different jobs to its popup and detailed view while connecting both to the same project context.
Opening the popup does not execute the work
Icons and the puzzle are capability-selection entry points. An item's menu leads to Python/notebook execution, usage and management choices. Registration, pinning and menu opening do not automatically start business effects. The runner is reached after an execution action is selected.
Quick execution reads the current tab and saved defaults. Where required account, target or content is invalid, a branch opens detailed input for preparation. Convenience does not mean every capability must execute unconditionally in one click. Keep frequent choices short and route input review to the depth it needs.
Do not make instructions compete with quick actions
Usage opens the existing right-side input view with showUsage enabled. That detailed view explains what the capability does, how to use it and its procedure. Recreating all instructions in the popup would split their canonical definition.
Changed capabilities need updated explanation and input contracts together. The popup remains an entry point; management handles enablement, pinning and registration, while the run form handles current inputs. Calling every surface settings would make it harder to find where a decision belongs. Interface depth should correspond to the role of the decision.
A child above native web views still needs a contract
The extension popup is a separate trusted child positioned above actual WebContentsViews. It uses dedicated preload, a restricted action schema and checks for sender, main frame and URL. External pages do not inherit its menu authority merely because it appears above them.
Dimensions are constrained to the display work area, and navigation and new windows are denied. That is not certification against every security problem. The useful architectural choice avoids assuming one large CSS z-index solves native view ordering and authority. Inspect where a menu is rendered and who can request its operations in the actual app structure.
Recheck context after the popup has opened
Bootstrap captures profile, workspace and tab at opening and checks after refresh and before actions. Changed selection produces STALE_PLUGIN_POPUP rather than redirecting the old menu to a similar new tab. Menu-open time and action time can differ.
Escape/dismissal has a route back to puzzle focus, while blur closes the popup. A late dismissal checks context so it does not steal the person's new focus. Small surfaces do not make this trivial. Quick actions intensify the expectation that work applies to the currently understood target; an old menu should not acquire authority over a new destination.
Retain the actual evidence level for shortcuts too
Existing documents separate popup, detail, management, focus, keyboard and disablement checks. They also distinguish an error-free OS open-path return from visually reading an Explorer window. Report the boundary whose result was observed rather than just that a link was clicked. A configured parent-folder shortcut also differs from the output folder of a particular successful run. The button label and its evidence should identify which material it actually opens.
I reviewed code without executing the original popup. The shared status-copy module uses synthetic data only. The interface principle is a small menu leading naturally to necessary inputs, evidence and management, rather than containing every explanation itself. Separate depths should preserve one coherent target and execution meaning for both person and agent.