@open-mercato/cezar 0.12.0-pr1132.2000 → 0.12.0-pr1137.2005

package/README.md

@@ -60,6 +60,11 @@
 - 🧩 Skills are Markdown files and workflows are short YAML files. Mix agents per step.
 - 🐙 Run the agent straight on a GitHub issue. Nothing merges on its own.
 - 📂 One cockpit for all your projects.
+- 📊 A workspace dashboard shows what needs you, what is running and what finished across your projects.
+- 💸 Track reported cost and token usage by project in **Usage & cost**.
+- ⏰ Schedule recurring work or launch tasks from GitHub and supported tracker events with **Automations**.
+- 🌳 Agents can delegate independent work to child tasks, each in its own worktree, and receive their reports in the parent session.
+- 🎫 Connect **Jira or Linear** to browse issues and launch tasks from your project tracker.
 - 💾 No database. Everything is saved as plain files in `.ai/cezar/`.
 
 ## Screenshots
@@ -88,6 +93,18 @@
 
 [![Skills + Autonomous: Pick a playbook, flip Autonomous and walk away.](docs/screenshots/skills-autonomous.png)](docs/screenshots/skills-autonomous.png)
 
+**Dashboard** — See what needs your input or review, what is running and what finished across your workspace.
+
+[![Dashboard: Workspace task counts, review requests and recent results.](docs/screenshots/dashboard.png)](docs/screenshots/dashboard.png)
+
+**Usage & cost** — Compare reported spend and token usage across projects.
+
+[![Usage and cost: Reported spend, input and output tokens, and a project breakdown.](docs/screenshots/usage-costs.png)](docs/screenshots/usage-costs.png)
+
+**Automations** — Schedule maintenance and reviews, and see the week ahead alongside GitHub triggers.
+
+[![Automations: A weekly calendar of scheduled tasks and a pull-request review trigger.](docs/screenshots/automation-calendar.png)](docs/screenshots/automation-calendar.png)
+
 **On your phone** — the same cockpit, from the task list to the diff.
 
 <table>
@@ -152,6 +169,27 @@ steps:
 
 The built-in `quick-task` workflow runs with no setup.
 
+## Automations
+
+Turn repeatable work into an automation: check dependencies every morning, draft
+release notes on Fridays, or review each new pull request. Each match or scheduled
+occurrence launches an ordinary cezar task with the workflow and agent you choose.
+
+Create one in **Automations**, or ask the agent to set it up from a prompt.
+Preview event filters before enabling them. The list shows triggers, upcoming
+runs and recent outcomes; pause an automation whenever you need to.
+
+[![Automation list: Triggers, next runs and recent task outcomes.](docs/screenshots/automations.png)](docs/screenshots/automations.png)
+
+## Task dispatch
+
+For independent pieces of work, an agent can dispatch child tasks — for example,
+changes in separate modules or a fresh review of a finished branch. Each child
+gets its own worktree, appears under its parent in the task list and reports back
+into the parent session.
+cezar limits a parent to four children in flight; when a parent has a budget,
+its children share that budget. Nothing auto-merges.
+
 ## Documentation
 
 The [reference](docs/reference.md) covers everything else:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-mercato/cezar",
-  "version": "0.12.0-pr1132.2000",
+  "version": "0.12.0-pr1137.2005",
   "description": "Local cockpit for running and tracking AI agent tasks in your repo. Uses your logged-in `claude` CLI and `gh` — zero config, zero database.",
   "license": "MIT",
   "type": "module",
@@ -54,8 +54,8 @@
     "zod": "^4.4.3"
   },
   "devDependencies": {
-    "@open-mercato/cezar-api-client": "0.12.0-pr1132.2000",
-    "@open-mercato/cezar-contract": "0.12.0-pr1132.2000",
+    "@open-mercato/cezar-api-client": "0.12.0-pr1137.2005",
+    "@open-mercato/cezar-contract": "0.12.0-pr1137.2005",
     "@types/node": "^20.14.0",
     "@types/proper-lockfile": "4.1.4",
     "@types/ws": "^8.18.1",