@hiveai/cli 0.9.11 → 0.9.12
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 +26 -0
- package/dist/index.js +849 -662
- package/dist/index.js.map +1 -1
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -28,6 +28,7 @@ This installs the `haive` command globally. **The MCP server is bundled** — us
|
|
|
28
28
|
# 1. Initialize hAIve in your project (strict enforcement ON by default)
|
|
29
29
|
cd my-project
|
|
30
30
|
haive init # .ai/, MCP config, hooks, CI, code-map
|
|
31
|
+
haive agent status # confirm MCP/wrapper/fallback mode
|
|
31
32
|
haive enforce install # re-apply strict MCP + Git + CI enforcement gates
|
|
32
33
|
|
|
33
34
|
# 2. Point your AI client at the MCP server
|
|
@@ -67,6 +68,7 @@ haive init # Autopilot: policy config, hooks, CI, MCP setup,
|
|
|
67
68
|
haive init --manual # Manual mode: you approve every memory yourself
|
|
68
69
|
haive init --no-bridges # Skip bridge file generation (CLAUDE.md, .cursorrules, etc.)
|
|
69
70
|
haive init --dir /other/path # Initialize in a specific directory
|
|
71
|
+
haive init --yes # Also approve user-level AI client MCP configuration
|
|
70
72
|
```
|
|
71
73
|
|
|
72
74
|
**Autopilot mode** (default):
|
|
@@ -102,6 +104,30 @@ your-project/
|
|
|
102
104
|
|
|
103
105
|
Bridge files include mandatory rules, but they are not the enforcement boundary. hAIve's portable enforcement comes from MCP policy, Git hooks, CI checks, and `haive run -- <agent>` for CLI agents.
|
|
104
106
|
|
|
107
|
+
`haive init` also runs agent-aware setup. It always writes project-level MCP configs and records the selected mode in `.ai/.runtime/enforcement/agent-mode.json`. When it needs to change user-level configs such as Cursor, Claude Code, VS Code, Windsurf, or Codex, it asks for confirmation in an interactive shell. In CI/non-interactive shells, re-run:
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
haive agent setup --yes
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
### `haive agent`
|
|
114
|
+
|
|
115
|
+
Detect and configure the best hAIve mode for the current machine.
|
|
116
|
+
|
|
117
|
+
```bash
|
|
118
|
+
haive agent detect # inspect project MCP + installed agents
|
|
119
|
+
haive agent status # same report, human-readable or --json
|
|
120
|
+
haive agent setup # project MCP + optional global MCP setup
|
|
121
|
+
haive agent setup --no-global # project-only setup, no user config writes
|
|
122
|
+
haive agent setup --yes # approve user-level MCP config writes
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
Modes:
|
|
126
|
+
|
|
127
|
+
- `mcp`: native hAIve tools are available through the AI client.
|
|
128
|
+
- `wrapped`: use `haive run -- <agent>` when native MCP is unavailable.
|
|
129
|
+
- `fallback`: use `haive briefing` and `haive enforce check` manually.
|
|
130
|
+
|
|
105
131
|
---
|
|
106
132
|
|
|
107
133
|
### `haive enforce`
|