dimensionalOS / dimensionalOS/dimos
Agent skills: distinguish parallel-safe vs sequential-only execution
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Currently there is no distinction between skills that can be dispatched in parallel (e.g. perception queries, lookups) and skills that must run sequentially because they are physical actions (e.g. navigate, pick, place). The agent has no way to know which skills are safe to chain concurrently and which require ordered execution.
We need a mechanism (decorator flag, capability annotation, or similar) so the agent can parallelize independent queries while still enforcing sequential ordering for action skills that mutate world state.
Synced from DIM-939 by summer
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 locating the skill dispatch and execution entry points, then trace how independent queries and physical actions are currently scheduled. Define how skills declare parallel safety and how the agent enforces ordering for state-changing actions. Done means the distinction is represented in the skill system and covered by tests for concurrent queries and sequential actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, robotics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100