openvinotoolkit / openvinotoolkit/physicalai
Investigate merging the `physicalai-studio-plugin` back into `physicalai`
Open
@samet-akcay is already working on this.
Since Sep 14, 2026.
- Dominant language
- Python
- Stars
- 28
- Forks
- 22
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 30
Description
The physicalai-studio-plugin exposes additional interfaces that are used by Studio for its robot plugin implementation.
Its important part is:
@dataclass
class RobotCatalogDefinition(Generic[_PayloadT]):
"""Complete definition of a plugin robot type for Studio registration."""
type: str
display_name: str
role: Literal["follower", "leader"]
robot_builder: BuildRobotCallable | None = None
robot_payload: _PayloadModelT | None = None
asset: RobotAsset | None = None
adapter_options: RobotAdapterOptions = field(default_factory=RobotAdapterOptions)
probe: RobotProbe[_PayloadT] | None = None
which helps studio in building a robot driver, constructing a UI from the payload schema.
The RobotProbe and RobotAsset fields are both fields that could be beneficial to the physicalai runtime itself.
@maxxgx can you also look into removing the adapter_options. Before these were used in studio's runtime, but I believe that they may now be ignored..?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.