dimensionalOS / dimensionalOS/dimos
External blueprint discovery via package entry points
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Summary
Add dynamic discovery for externally packaged DimOS blueprints via Python package entry points.
External packages can expose runnable blueprints with the dimos.blueprints entry point group and users can run them by namespaced name, for example:
dimos run my-robot-stack.go2
dimos run unitree-go2 my-robot-stack.keyboard-teleop
PR
Scope
- Discover external blueprints through installed package metadata.
- Keep bare blueprint names reserved for built-in DimOS blueprints/modules.
- Support external targets that are
Blueprintobjects or DimOSModuleclasses. - Add grouped
dimos listoutput for built-in and external blueprints. - Cover CLI, Python API, and coordinator resolver paths.
- Update user/contributor docs.
Suggested labels
enhancement, core
Synced from DIM-1023 by che
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.
Research direction
Start by reviewing the linked external blueprint registration PR, then trace the CLI, Python API, and coordinator resolver paths named in the issue. Done means installed entry points are discovered with namespaced targets, built-ins remain protected, supported target types resolve correctly, grouped listing and coverage are present, and the user and contributor docs are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, cli, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100