feat(workflow): implement standalone TOML execution

- Add octomind workflow CLI command for TOML files
- Move workflow definitions from main config to separate files
- Add auto_capabilities configuration setting
- Document GIT_TREE and HOME template variables
- Update builtin server tool mappings for core and runtime
- Update default compression model to gpt-5-mini
- Rename default tap to muvon/tap
- Add capability command to session reference
- Refine MCP server and compression documentation
- Remove /workflow slash command from editor integrations
- Update session command counts and architecture docs

Author: donk8r

README.md

@@ -292,6 +292,7 @@ You're in an interactive session with a specialist that can read your code, run
 | `schedule` | Inject messages at future times |
 | `skill` | Inject reusable instruction packs from taps |
 | `tap` | Delegate to any specialist role from a tap registry |
+| `capability` | Auto-activate capabilities by semantic intent matching |
 
 ### Filesystem tools (via [octofs](https://github.com/muvon/octofs))
 
@@ -323,20 +324,16 @@ temperature = 0.2
 server_refs = ["filesystem", "github"]
 allowed_tools = ["view", "ast_grep", "create_pr"]
 
-# Workflows — multi-step, each step its own model and toolset
-[[workflows]]
-name = "deep_review"
-[[workflows.steps]]
-name = "analyze"
-layer = "context_researcher"     # gemini-flash, broad context
-[[workflows.steps]]
-name = "critique"
-layer = "senior_reviewer"        # claude-opus, precision
-
 # Sandbox — lock all writes to current directory
 sandbox = true
 ```
 
+```bash
+# Workflows — multi-step, each step its own model and toolset
+# Defined in standalone TOML files, run via CLI
+octomind workflow deep_review.toml
+```
+
 - **Roles** — model, temperature, system prompt, MCP servers, tool permissions per role.
 - **Layers** — chained AI sub-agents that run after each response.
 - **Guardrails** — deterministic policy (guards, hooks, validators) and input pipes.
@@ -366,7 +363,7 @@ octomind acp developer:general
 octomind run developer "Explain the auth module" --format plain
 
 # Structured JSON output for pipelines
-octomind run developer "List TODO items" --schema todos.json --format jsonl
+octomind run developer "List TODO items" --format jsonl
 ```
 
 One binary. Every workflow.

doc/README.md

@@ -80,7 +80,7 @@ Real-world examples showing how to solve practical problems with Octomind.
 | Document | Description |
 |----------|-------------|
 | [CLI Reference](reference/01-cli-reference.md) | All CLI commands and flags |
-| [Session Commands](reference/02-session-commands.md) | All 25 interactive session commands |
+| [Session Commands](reference/02-session-commands.md) | All 27 interactive session commands |
 | [Config Reference](reference/03-config-reference.md) | Every configuration field documented |
 | [Environment Variables](reference/04-environment-variables.md) | API keys, overrides, template variables |
 

doc/dev/02-architecture.md

@@ -32,7 +32,6 @@ src/
     roles.rs                 # Role configuration
     mcp.rs                   # MCP server config (Builtin/Http/Stdio)
     hooks.rs                 # Webhook hook config
-    workflows.rs             # Workflow + step definitions
     guardrails.rs           # Guardrails (pipe) configuration
     layers.rs                # Layer configuration
     agents.rs                # Agent (ACP) configuration
@@ -86,7 +85,7 @@ src/
 
     chat/
       mod.rs                 # Chat orchestration
-      commands.rs            # Command constants (28 entries, COMMANDS array)
+      commands.rs            # Command constants (27 entries, COMMANDS array)
       animation.rs / animation_manager.rs  # Spinner & animation
       status_prefix.rs       # Shared status formatting (prompt + spinner)
       assistant_output.rs    # Assistant output formatting
@@ -123,7 +122,7 @@ src/
         core.rs              # ChatSession struct, SessionInitParams builder
         api_executor.rs      # API call execution
         api_prep.rs          # API call preparation (compression, auto-activation)
-        commands/            # 28 command handler modules
+        commands/            # 26 command handler modules (28 files incl. mod.rs + utils.rs)
         display.rs           # Session display
         error_utils.rs       # Error utilities
         layer_processor.rs   # Layer processing in session context

doc/dev/03-mcp-server-development.md

@@ -15,7 +15,7 @@ For external tools, prefer configuring a `stdio` or `http` server in config.
 
 | Server | Location | Purpose |
 |--------|----------|---------|
-| `core` | `src/mcp/core/` | Plan, tap, capability, skills, scheduling, dynamic servers |
+| `core` | `src/mcp/core/` | Plan, tap |
 | `runtime` | `src/mcp/runtime/` | MCP management, agent delegation, skills, scheduling, capability |
 | `agent` | `src/mcp/agent/` | Agent delegation via ACP |
 

doc/integration/04-tap-system.md

@@ -49,13 +49,13 @@ octomind untap myorg/my-agents
 
 ### Built-in Tap
 
-The default tap `muvon/octomind-tap` is always active and ships production-ready agents.
+The default tap `muvon/tap` is always active and ships production-ready agents.
 
 ## Tap Priority
 
 When multiple taps provide the same agent tag, priority is:
 1. User-added taps (in order added)
-2. Built-in default tap (`muvon/octomind-tap`)
+2. Built-in default tap (`muvon/tap`)
 
 ## Using Tap Agents
 

doc/reference/01-cli-reference.md

@@ -179,6 +179,22 @@ octomind config --validate
 octomind config --list-themes
 ```
 
+## `octomind workflow <FILE>`
+
+Run a multi-step workflow defined in a TOML file.
+
+| Flag | Short | Description |
+|------|-------|-------------|
+| `FILE` | | Path to workflow TOML file (required) |
+| `--dry-run` | | Validate and print execution plan without spawning processes |
+
+Reads input from stdin. Per-step progress, cost, and token stats go to stderr. The final step's output goes to stdout.
+
+```bash
+echo "build a JSON-to-CSV CLI in Rust" | octomind workflow myflow.toml
+octomind workflow myflow.toml --dry-run
+```
+
 ## `octomind completion <SHELL>`
 
 Generate shell completion scripts.

doc/reference/03-config-reference.md

@@ -16,6 +16,7 @@ All values shown match `config-templates/default.toml`. Fields marked **(require
 | `custom_instructions_file_name` | string | `"INSTRUCTIONS.md"` | File auto-loaded as user message in new sessions. Empty string to disable. |
 | `custom_constraints_file_name` | string | `"CONSTRAINTS.md"` | File appended to each request in `<constraints>` tags. Empty string to disable. |
 | `sandbox` | bool | `false` | Restrict filesystem writes to working directory. Also available as `--sandbox` CLI flag. |
+| `auto_capabilities` | bool | `true` | Enable automatic capability activation on user messages. Disable to require manual `capability(action="enable")` calls. |
 
 ## Performance & Limits
 
@@ -121,10 +122,8 @@ MCP server definitions. Three types supported: `builtin`, `http`, `stdio`.
 
 **Builtin servers** (always available, no external process):
 
-| Name | Tools | Purpose |
-|------|-------|---------|
-| `core` | `plan`, `schedule`, `capability`, `tap` | High-level day-to-day tools |
-| `runtime` | `mcp`, `agent`, `skill` | Low-level harness reconfiguration |
+| `core` | `plan`, `tap` | High-level planning and agent management |
+| `runtime` | `mcp`, `agent`, `skill`, `schedule`, `capability` | Harness reconfiguration and scheduling |
 | `agent` | `agent_<name>` per `[[agents]]` entry | ACP sub-agent dispatch |
 
 `filesystem` is no longer a builtin — it's an external `stdio` server backed by `octofs`. See [MCP Tools](../usage/07-mcp-tools.md) for the tool surface.
@@ -450,6 +449,8 @@ Available in `system` and `welcome` fields:
 | `{{OS}}` | Operating system |
 | `{{BINARIES}}` | Available binary tools |
 | `{{GIT_STATUS}}` | Git repository status |
+| `{{GIT_TREE}}` | Project file tree |
 | `{{README}}` | Contents of README.md in project root |
+| `{{HOME}}` | User's home directory path |
 | `{{CONTEXT}}` | Session context (for layers) |
 | `{{SYSTEM}}` | Parent system prompt (for layers) |

doc/reference/04-environment-variables.md

@@ -56,9 +56,11 @@ Available in `system` and `welcome` config fields. Use `octomind vars` to see cu
 | `{{DATE}}` | Current date |
 | `{{SHELL}}` | User's shell (e.g., `bash`, `zsh`) |
 | `{{OS}}` | Operating system name |
-| `{{BINARIES}}` | Available binary tools on PATH |
+| `{{BINARIES}}` | Available development tools and their versions |
 | `{{GIT_STATUS}}` | Git repository status (branch, changes) |
+| `{{GIT_TREE}}` | Project file tree |
 | `{{README}}` | Contents of `README.md` in project root |
+| `{{HOME}}` | User's home directory path |
 | `{{CONTEXT}}` | Session context (for layer system prompts) |
 | `{{SYSTEM}}` | Parent system prompt (for layer system prompts) |
 

doc/troubleshooting/02-migration-guide.md

@@ -125,14 +125,14 @@ The `core` builtin server was split into two: high-level tools stay in `core`, l
 | Tool | Old server | New server |
 |------|------------|------------|
 | `plan` | `core` | `core` |
-| `schedule` | `core` | `core` |
-| `capability` | `core` | `core` |
 | `tap` *(new)* | -- | `core` |
 | `mcp` | `core` | **`runtime`** |
 | `agent` | `core` | **`runtime`** |
 | `skill` | `core` | **`runtime`** |
+| `schedule` | `core` | **`runtime`** |
+| `capability` | `core` | **`runtime`** |
 
-If your config or tap manifest has `server_refs = ["core", ...]` and the role calls any of `mcp`, `agent`, or `skill`, add `"runtime"` to the list:
+If your config or tap manifest has `server_refs = ["core", ...]` and the role calls any of `mcp`, `agent`, `skill`, `schedule`, or `capability`, add `"runtime"` to the list:
 
 ```diff
  [roles.mcp]
@@ -154,7 +154,7 @@ tools = []
 
 If you have a hand-rolled config without it, add the block.
 
-Roles that don't call `mcp`/`agent`/`skill` (most roles) don't need `"runtime"` at all — drop it from `server_refs` to keep the tool surface tighter.
+Roles that don't call `mcp`/`agent`/`skill`/`schedule`/`capability` (most roles) don't need `"runtime"` at all — drop it from `server_refs` to keep the tool surface tighter.
 
 ## Filesystem Is Now External
 

doc/usage/03-configuration.md

@@ -244,8 +244,9 @@ System prompts and welcome messages support variables:
 | `{{BINARIES}}` | Available binaries in PATH |
 | `{{OS}}` | Operating system |
 | `{{GIT_STATUS}}` | Git status |
+| `{{GIT_TREE}}` | Project file tree |
 | `{{README}}` | Project README.md contents |
-
+| `{{HOME}}` | User's home directory path |
 Use `octomind vars` to see all current values.
 
 ## Further Reading