# AgentOS Beta v0.3.1

AgentOS is a portable, PowerShell-first local agent workspace for Windows. It connects to an operator-selected model endpoint, keeps workspace state local, and exposes verified local file actions through OS, OSX, OSP, and browser interfaces.

## Supported baseline

- Windows PowerShell 5.1
- Standard-user installation; no administrator rights required
- OS and OSX startup, HTTP model turns, and local `SAVE_FILE` actions tested in PowerShell Constrained Language Mode
- Optional bundled Python 3.12 runtime for OSP and the dashboard
- OpenAI-compatible chat-completions endpoints; additional provider adapters are experimental

Policy may still block outbound network access, child processes, or optional browser/Python features. “Works in CLM” is not a magic spell that overrides enterprise policy.

## First run

1. Extract the ZIP to a normal writable folder.
2. Double-click `Install Mix of Agents.bat`.
3. Enter a provider profile name, chat-completions endpoint, model ID, and API key. Leave the key blank for a local endpoint that does not require authentication.
4. Launch `Start AgentOS.bat` or `Start AgentOSX.bat`.
5. Run `/doctor`, then enter a small test prompt.

The package starts with a neutral `local-ollama` template. It does not contain an API key, OAuth token, personal profile, chat history, or configured remote provider.

## Launchers

| File | Purpose |
|---|---|
| `Start AgentOS.bat` | Primary PowerShell console (OS) |
| `Start AgentOSX.bat` | Alternate PowerShell console (OSX) |
| `Start AgentOSP.bat` | Optional Python console (OSP) |
| `Start AgentOSH.bat` | Browser chat interface |
| `Adapters\UI\LiveDashboard\Launch-Dashboard.ps1` | Local dashboard bridge |

## PowerShell direct

```powershell
cd "C:\path\to\AgentOS-Beta-v0.3.1"
powershell -NoProfile -ExecutionPolicy Bypass -File ".\Scripts\AgentOS.ps1"
powershell -NoProfile -ExecutionPolicy Bypass -File ".\Scripts\AgentOSX.ps1"
```

The launch commands use `-ExecutionPolicy Bypass` for the process only. They do not change machine or user execution policy.

## Provider files

- `Config\provider.json`: active endpoint/model metadata; no raw key
- `Config\providers.json`: provider profiles; all packaged profiles have `apiKeySet: false`
- `Config\Keys\<provider>.key.txt`: created locally by the installer, restricted to the current Windows identity, and excluded from releases

Runtime commands: `/providers`, `/provider NAME`, `/endpoint URL`, `/model MODEL`, and `/key`.

## Verification

- `powershell -NoProfile -ExecutionPolicy Bypass -File .\Scripts\AgentOS.ps1 -SelfTest`
- `powershell -NoProfile -ExecutionPolicy Bypass -File .\Scripts\AgentOSX.ps1 -SelfTest`
- `.\Tools\Python\python.exe .\Scripts\AgentOSP.py --selftest`

Use `/doctor` after configuring a real provider. A self-test validates package structure; it does not prove that your endpoint credentials or network policy are correct.

## Security and beta limitations

- AgentOS can create, read, and modify files within its extracted workspace when the model emits supported action tags.
- Absolute paths and `..` traversal are rejected by the runtime action boundary.
- Do not place secrets in prompts or ordinary workspace files.
- Keep the package in a writable folder you control and review generated outputs.
- This is public beta software, not a claim of universal compliance, accreditation, or production hardening.

Downloading and using the beta is subject to the terms published at https://mix-of-agents.com.
