Summary
It would be useful for Adaptix to expose common UI components to scripts and plugins, similar to how Cobalt Strike allows Aggressor Script extensions to create custom menus and dialogs.
In particular, exposing the existing code editor, along with other reusable dialog types, would enable plugins to build more complete operator workflows without requiring modifications to the Adaptix client itself.
Example Workflow
A plugin could implement a workflow such as:
- Right-click an agent.
- Select a custom Run C Code menu item.
- Adaptix opens a code editor dialog.
- The operator writes or pastes C code.
- The operator clicks a custom Run button within the dialog.
- The plugin receives the editor contents and sends them to a C interpreter, compiler, VM, or other execution backend.
This example is based on Cobalt Strike-style C interpreter or VM functionality, but the underlying request is for general-purpose, scriptable UI support.
Summary
It would be useful for Adaptix to expose common UI components to scripts and plugins, similar to how Cobalt Strike allows Aggressor Script extensions to create custom menus and dialogs.
In particular, exposing the existing code editor, along with other reusable dialog types, would enable plugins to build more complete operator workflows without requiring modifications to the Adaptix client itself.
Example Workflow
A plugin could implement a workflow such as:
This example is based on Cobalt Strike-style C interpreter or VM functionality, but the underlying request is for general-purpose, scriptable UI support.