@olhapi/maestro-darwin-x64 0.1.0-rc.5 → 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -9
- package/lib/maestro +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,22 +4,36 @@ Maestro is a local-first orchestration runtime for agent-driven software work.
|
|
|
4
4
|
|
|
5
5
|
Website: [maestro.olhapi.com](https://maestro.olhapi.com/)
|
|
6
6
|
Repository: [github.com/olhapi/maestro](https://github.com/olhapi/maestro)
|
|
7
|
+
Docs: [maestro.olhapi.com/docs](https://maestro.olhapi.com/docs)
|
|
7
8
|
|
|
8
9
|
It combines a SQLite-backed tracker, an orchestrator that reads `WORKFLOW.md`, a private MCP daemon bridged by `maestro mcp`, and an HTTP server that serves the embedded dashboard plus JSON/WebSocket APIs.
|
|
9
10
|
|
|
10
11
|
Maestro stays local-first even when a project syncs issues from Linear. Provider-backed issues are synchronized into the local store, then supervised through the same local queue, runtime state, MCP tools, and dashboard surfaces as local kanban issues.
|
|
11
12
|
|
|
13
|
+
## Docs Website
|
|
14
|
+
|
|
15
|
+
The docs site is organized around the same operator flow the product uses:
|
|
16
|
+
|
|
17
|
+
- [Install](https://maestro.olhapi.com/docs/install)
|
|
18
|
+
- [Quickstart](https://maestro.olhapi.com/docs/quickstart)
|
|
19
|
+
- [Architecture](https://maestro.olhapi.com/docs/architecture)
|
|
20
|
+
- [Control center](https://maestro.olhapi.com/docs/control-center)
|
|
21
|
+
- [Workflow config](https://maestro.olhapi.com/docs/workflow-config)
|
|
22
|
+
- [Operations and observability](https://maestro.olhapi.com/docs/operations)
|
|
23
|
+
- [CLI reference](https://maestro.olhapi.com/docs/cli-reference)
|
|
24
|
+
- [Real Codex E2E harness](https://maestro.olhapi.com/docs/advanced/e2e-harness)
|
|
25
|
+
|
|
12
26
|
## Install
|
|
13
27
|
|
|
14
28
|
### npm
|
|
15
29
|
|
|
16
|
-
Current public
|
|
30
|
+
Current public npm install on supported platforms:
|
|
17
31
|
|
|
18
32
|
```bash
|
|
19
|
-
npm install -g @olhapi/maestro
|
|
33
|
+
npm install -g @olhapi/maestro
|
|
20
34
|
```
|
|
21
35
|
|
|
22
|
-
|
|
36
|
+
Install the newest prerelease instead:
|
|
23
37
|
|
|
24
38
|
```bash
|
|
25
39
|
npm install -g @olhapi/maestro@next
|
|
@@ -27,8 +41,6 @@ npm install -g @olhapi/maestro@next
|
|
|
27
41
|
|
|
28
42
|
The installed command name is still `maestro`.
|
|
29
43
|
|
|
30
|
-
Until the first stable release ships, the npm prerelease channel is published on `next`. After `v0.1.0`, `npm install -g @olhapi/maestro` will follow the stable `latest` channel.
|
|
31
|
-
|
|
32
44
|
Official npm builds currently cover:
|
|
33
45
|
|
|
34
46
|
| Platform | Arch | Notes |
|
|
@@ -260,11 +272,12 @@ Fresh `maestro workflow init --defaults` output currently defaults to:
|
|
|
260
272
|
- `agent.mode: app_server`
|
|
261
273
|
- `agent.dispatch_mode: parallel`
|
|
262
274
|
- `codex.command: codex app-server`
|
|
263
|
-
- `codex.expected_version: 0.
|
|
275
|
+
- `codex.expected_version: 0.114.0`
|
|
264
276
|
- `codex.approval_policy: never`
|
|
265
|
-
- `codex.
|
|
266
|
-
- `
|
|
267
|
-
|
|
277
|
+
- `codex.initial_collaboration_mode: default` for fresh `app_server` threads
|
|
278
|
+
- runtime permission profiles now live in the DB per project/issue instead of `WORKFLOW.md`
|
|
279
|
+
|
|
280
|
+
`initial_collaboration_mode: default` keeps unattended runs execution-first for a fresh `app_server` thread. Use `plan` only when you explicitly want a plan-gated startup mode. Interactive approvals and `requestUserInput` prompts still depend on using a non-`never` approval policy, and those prompts are queued through the dashboard's global interrupt panel. Resumed threads and `stdio` runs do not use that startup-mode path.
|
|
268
281
|
|
|
269
282
|
Supported prompt-template variables are:
|
|
270
283
|
|
|
@@ -279,6 +292,7 @@ Supported prompt-template variables are:
|
|
|
279
292
|
- `{{ attempt }}`
|
|
280
293
|
|
|
281
294
|
When a project has a description, Maestro's default implementation, review, and done prompts include it automatically under a `Project context:` section. Custom workflows can place `{{ project.description }}` wherever they want.
|
|
295
|
+
The default done prompt also tells the agent to create a short local preview video when the change can be demonstrated and attach it to an issue comment when the available tracker or provider tooling supports that flow.
|
|
282
296
|
|
|
283
297
|
The checked-in [`WORKFLOW.md`](WORKFLOW.md) is this repository's own workflow example. It is not guaranteed to match fresh `workflow init` defaults exactly.
|
|
284
298
|
|
package/lib/maestro
CHANGED
|
Binary file
|