Skip to content

docs(readme, cli, system requirements): add full CLI reference, delete stale development README#1524

Merged
spomichter merged 26 commits intodevfrom
docs/cli-reference
Mar 11, 2026
Merged

docs(readme, cli, system requirements): add full CLI reference, delete stale development README#1524
spomichter merged 26 commits intodevfrom
docs/cli-reference

Conversation

@spomichter
Copy link
Contributor

@spomichter spomichter commented Mar 11, 2026

  • New docs/usage/cli.md: all commands, global options, standalone tools, MCP integration, config precedence, file locations
  • Delete docs/development/README.md: duplicated main README content
  • Delete docs/development/dimos_run.md: superseded by cli.md

Problem

Closes DIM-XXX

Solution

Breaking Changes

How to Test

Contributor License Agreement

  • I have read and approved the CLA.

- New docs/usage/cli.md: all commands, global options, standalone tools,
  MCP integration, config precedence, file locations
- Delete docs/development/README.md: duplicated main README content
- Delete docs/development/dimos_run.md: superseded by cli.md
@spomichter spomichter changed the title docs(cli): add full CLI reference, delete stale dev README docs(readme, cli, system requirements): add full CLI reference, delete stale development README Mar 11, 2026
- README: compact hardware table, link to full details
- docs/requirements.md: tested configs, all dependency extras,
  core vs docker tier, platform compatibility notes
- Subsumes PR #1402 content with expanded dependency coverage
…iers

- Alpha Pre-Release → Pre-Release Beta
- Arms (Xarm, Piper): experimental → beta
- Drones (MAVLink, DJI): experimental → alpha
- Delete System Requirements section (moved to docs/requirements.md)
- Delete ROS interop section (transports link in Library API)
- Add CLI & MCP overview with common commands
- Add blueprint composition examples with dimos list
- Quote all pip install extras for zsh compatibility
- Fix todo.md links → manipulation docs for arms
README.md Outdated
dimos log -f # Follow logs
dimos agent-send "explore the room" # Send agent a command
dimos mcp list-tools # List available MCP skills
dimos mcp call move --arg x=0.5 # Call a skill directly
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this works. I've removed it from Unitree Go2 because it didn't work right (it used direct velocities, not positions). I've replaced it with relative_move.

Suggested change
dimos mcp call move --arg x=0.5 # Call a skill directly
dimos mcp call relative_move --arg forward=0.5 # Call a skill directly

Looks like there's a move on UnitreeG1SkillContainer. I should replace that.

There's also a move on the drone, but it takes a Vector3 param, and I don't think we can construct that from JSON arguments from the agent.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Comment on lines +32 to +35
pip install dimos[base,unitree] # Full stack + Unitree
pip install dimos[base,unitree,sim] # + MuJoCo simulation
pip install dimos[base,unitree,drone] # + Drone support
pip install dimos[base,unitree,manipulation] # + Arm control
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
pip install dimos[base,unitree] # Full stack + Unitree
pip install dimos[base,unitree,sim] # + MuJoCo simulation
pip install dimos[base,unitree,drone] # + Drone support
pip install dimos[base,unitree,manipulation] # + Arm control
pip install 'dimos[base,unitree]' # Full stack + Unitree
pip install 'dimos[base,unitree,sim]' # + MuJoCo simulation
pip install 'dimos[base,unitree,drone]' # + Drone support
pip install 'dimos[base,unitree,manipulation]' # + Arm control

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@spomichter spomichter marked this pull request as ready for review March 11, 2026 22:27
@spomichter spomichter merged commit 00d8dcc into dev Mar 11, 2026
14 checks passed
@spomichter spomichter deleted the docs/cli-reference branch March 11, 2026 22:27
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 11, 2026

Greptile Summary

This PR is a documentation overhaul that adds a comprehensive CLI reference (docs/usage/cli.md), restructures the main README.md with new "Agent CLI & MCP" and "Featured Runfiles" sections, and cleans up stale or stub files (docs/development/README.md, docs/development/dimos_run.md, docs/hardware/integration_guide.md, docs/todo.md). It also moves system requirements into a dedicated docs/requirements.md and adds full agents documentation to docs/capabilities/agents/readme.md.

Key changes:

  • New docs/usage/cli.md: Full CLI reference covering all global flags, run/status/stop/restart/log/list/show-config commands, agent-send, all dimos mcp subcommands, standalone tools (humancli, lcmspy, agentspy, dtop, rerun-bridge), configuration precedence, and file locations.
  • AGENTS.md not updated: Still references the now-deleted docs/development/dimos_run.md on line 383 — this will produce a broken link for AI agents directed to that file.
  • docs/development/README.md deletion: The PR description says the file duplicated the main README, but Sections 2 ("How to Hack on DimOS") and 3 ("How to Make a PR") contained unique content — architecture pointers, testing cheatsheet, and PR contribution guidelines — that is not reproduced anywhere in the new docs and no CONTRIBUTING.md exists in the repo.
  • Minor copy errors in docs/capabilities/agents/readme.md: "sufficent" typo and "which with be used" word transposition on lines 40–41.
  • Shell quoting fixes: uv pip install dimos[...]uv pip install 'dimos[...]' consistently applied across all platform and installation docs.

Confidence Score: 4/5

  • Safe to merge with minor fixes — this is a docs-only PR with no functional code changes.
  • All changes are documentation only. The new CLI reference and agents docs are accurate and well-structured. The main concern is the stale reference in AGENTS.md pointing to the deleted dimos_run.md, and the loss of unique contributor/PR guidelines from the deleted development README without a replacement. Two minor copy errors in the agents doc are trivially fixable.
  • AGENTS.md (stale link to deleted file) and docs/development/README.md deletion (unique contributor guidance lost).

Important Files Changed

Filename Overview
README.md Major restructuring: new "Agent CLI and MCP" and "Featured Runfiles" sections, navigation links updated, system requirements moved to docs/requirements.md, install script branch changed dev→main, shell quoting fixes throughout.
docs/capabilities/agents/readme.md New comprehensive agents documentation covering architecture, skills, MCP, input methods, and models — contains two copy errors on lines 40-41 ("sufficent" typo and "which with be used" grammar).
docs/development/README.md Deleted as "duplicated content", but Sections 2 ("How to Hack on DimOS" — debugging, architecture map, testing cheatsheet) and 3 ("How to Make a PR" — contribution guidelines) were unique and are not reproduced elsewhere in the new docs. No CONTRIBUTING.md exists in the repo.
docs/usage/cli.md New comprehensive CLI reference covering all global flags, commands (run/status/stop/restart/log/list/show-config), agent/MCP subcommands, standalone tools, and file locations. Well structured and accurate.
docs/requirements.md New system requirements file consolidating hardware specs, tested configurations, dependency tier table, and headless server notes moved from the main README.
AGENTS.md Not updated alongside the deleted docs/development/dimos_run.md — line 383 still references the now-deleted file, which will cause broken navigation for AI agents directed to this file.

Sequence Diagram

sequenceDiagram
    participant User
    participant CLI as dimos CLI
    participant Registry as Run Registry
    participant Daemon as DimOS Daemon
    participant MCP as MCP Server
    participant Agent as LLM Agent

    User->>CLI: dimos run blueprint --daemon
    CLI->>Daemon: fork + health check
    Daemon->>Registry: write run-id, PID, args, ports
    CLI-->>User: run ID, PID, log path, MCP endpoint

    User->>CLI: dimos status
    CLI->>Registry: read run entry
    CLI->>Daemon: verify PID alive
    CLI-->>User: uptime, blueprint, MCP port

    User->>CLI: dimos agent-send text
    CLI->>Daemon: publish to /human_input via LCM
    Daemon->>Agent: deliver text
    Agent-->>Daemon: skill calls + response

    User->>CLI: dimos mcp list-tools
    CLI->>MCP: GET /mcp tool listing
    MCP-->>CLI: JSON tool schemas
    CLI-->>User: available skills

    User->>CLI: dimos mcp call relative_move --arg forward=0.5
    CLI->>MCP: POST /mcp tool call
    MCP->>Daemon: execute skill RPC
    Daemon-->>MCP: result
    MCP-->>CLI: tool result
    CLI-->>User: output

    User->>CLI: dimos stop
    CLI->>Daemon: SIGTERM then SIGKILL
    CLI->>Registry: remove run entry
Loading

Comments Outside Diff (1)

  1. AGENTS.md, line 383 (link)

    Stale reference to deleted file

    AGENTS.md line 383 references docs/development/dimos_run.md which is deleted by this PR. Users (including AI agents directed to this file) will follow the link and get a 404. This should be updated to point to the new CLI reference.

Last reviewed commit: 36c5916

Comment on lines +40 to +41
- Docstrings become the tool description the LLM sees. Write them clearly so the agent has sufficent context.
- The function must return a string or image which with be used by the agent to decide what to do next.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two copy errors in the Skills rules

Line 40 has a typo ("sufficent" → "sufficient") and line 41 has a word transposition ("which with be used" → "which will be used").

Suggested change
- Docstrings become the tool description the LLM sees. Write them clearly so the agent has sufficent context.
- The function must return a string or image which with be used by the agent to decide what to do next.
- Docstrings become the tool description the LLM sees. Write them clearly so the agent has sufficient context.
- The function must return a string or image which will be used by the agent to decide what to do next.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants