体化AI操作系统

1. Install

```bash git clone https://github.com/PhyAgentOS/PhyAgentOS-core.git cd PhyAgentOS-core python -m pip install -e .

Or install a local, independently obtained bundle

paos skill install /path/to/<skill-name>-<version>.tar.gz --local paos skill inspect <skill-name> paos skill start <skill-name> --profile <profile> paos skill status <skill-name>

With no non-terminal AgentTask, select another installed Runtime

paos skill switch <other-skill-name> --profile <profile> paos skill logs <skill-name> paos skill stop <skill-name>

Verify the executable locked by the installed Skill manifest

paos forge-node install <skill-name> <node-id> --archive /path/to/<node>.tar.gz paos forge-node verify <skill-name> <node-id> ```

Each Forge Skill bundle declares its workflow document, required Tool IDs, named runtime profiles, and exact platform/architecture Node locks. Each locked archive has an exact SHA-256 and contains one named root-level executable. For Registry Node downloads, the verified Skill lock supplies the digest when the Registry omits that duplicate field, and the exact size is resolved before the download begins; installation records and verifies the extracted binary hash. python scripts/package_skill.py <bundle-dir> --output-dir <directory> creates a deterministic bundle for publication. The PhyAgentOS source and release packages do not bundle concrete Forge Skills, Forge nodes, models, or simulation assets; obtain only the Skills needed for a deployment and install them explicitly. The integration development guide documents Bundle layout, local validation, immutable publication order, and Registry acceptance.

5-minute quick start

3. Configure a provider and Forge

The configuration file is serialized in camelCase; snake_case keys are also accepted.

{
  "agents": {
    "defaults": {
      "workspace": "~/.PhyAgentOS/workspace",
      "model": "openrouter/openai/gpt-4o-mini",
      "provider": "openrouter"
    },
    "verification": {
      "serviceEnabled": true,
      "evidenceRetention": "failed",
      "maxReplansPerEpisode": 2,
      "maxVerifierCallsPerRun": 50
    },
    "evolution": {
      "enabled": true,
      "scope": "verified_forge_lineage",
      "promotionMode": "guarded_auto",
      "minSuccessfulEpisodes": 3,
      "minLessonEpisodes": 3,
      "maxLessonsPerSkill": 8,
      "maxEvolutionCallsPerRun": 20
    }
  },
  "providers": {
    "openrouter": {
      "apiKey": "YOUR_API_KEY"
    }
  },
  "forge": {
    "requestTimeoutS": 10,
    "pollIntervalS": 0.5,
    "executionTimeoutS": 300,
    "evidence": {
      "requiredImageSources": ["front"],
      "captureTimeoutS": 5,
      "postCaptureTimeoutS": 5,
      "connectionTimeoutS": 2,
      "maxArtifactBytes": 8388608,
      "associationQuality": "best_effort"
    }
  },
  "resourceRegistry": {
    "url": "https://paos-resource-manager.dev.x-era.com"
  }
}

The front source is only an example. resourceRegistry.url selects a generic package registry; it may be empty when all artifacts are installed from local bundles or a supplied static index. PAOS connects only to the Gateway URL in the manifest of the explicitly started, healthy Skill Runtime. It never starts or downloads a concrete Skill merely because the Agent starts.

dora-cli 0.4.1

One request; the Agent may create an AgentTask and bind Tool API calls to it

paos agent -m "Inspect Forge capabilities, then place the object in the target area and verify the visible result."

Long-running channels, Cron, Heartbeat, Agent, and Forge Tool API integration

paos gateway ```

Use paos status to inspect the local model/workspace configuration. Use forge_tool_context for a live ToolSpec, binding, readiness, endpoint status, and frame profile.