mirror of https://github.com/wu736139669/hapi.git synced 2026-08-05 06:24:37 +00:00

Files

T

73584e925a feat(cursor): multitask slash, autoReview mode, native worktree/add-dir (#1014 )

* feat(cursor): multitask slash, autoReview mode, native worktree/add-dir

Close the highest-value Cursor Agent gaps for remote HAPI: expand ACP-safe
slash pass-through (/multitask, worktree, add-dir, …), add autoReview
permission mode (--auto-review spawn + mid-session slash), and route Cursor
New Session worktrees through agent --worktree instead of HAPI sibling trees.

Fixes #1013

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(cli): accept --mode autoReview for hapi cursor

Align --mode parsing with CURSOR_PERMISSION_MODES so documented
`hapi cursor --mode autoReview` enables Smart Auto instead of silently
falling back to default.

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-07-12 18:41:52 +08:00

5.0 KiB

Raw Blame History

Cursor Agent

HAPI supports Cursor Agent CLI for running Cursor's AI coding agent with remote control via web and phone.

Prerequisites

Install Cursor Agent CLI:

macOS/Linux: curl https://cursor.com/install -fsS | bash
Windows: irm 'https://cursor.com/install?win32=true' | iex

Verify installation:

agent --version

Usage

hapi cursor                    # Start Cursor Agent session
hapi cursor resume <chatId>    # Resume a specific chat
hapi cursor --continue         # Resume the most recent chat
hapi cursor --mode plan        # Start in Plan mode
hapi cursor --mode ask         # Start in Ask mode
hapi cursor --auto-review      # Start with Auto-review (Smart Auto)
hapi cursor --yolo             # Bypass approval prompts (--force)
hapi cursor --model <model>    # Specify model
hapi cursor --cursor-worktree feature-x   # Cursor-native worktree
hapi cursor --cursor-add-dir ../shared    # Extra workspace root (repeatable)

Permission Modes

Mode	Description
`default`	Standard agent behavior
`plan`	Plan mode - design approach before coding
`ask`	Ask mode - explore code without edits
`debug`	Debug mode - hypotheses + instrumentation
`autoReview`	Auto-review (Smart Auto) - allowlist/sandbox/classifier instead of full YOLO
`yolo`	Bypass approval prompts

Set mode via --mode / --permission-mode / --auto-review, or change from the web UI during a session.

Cursor-native worktree & multi-root

New Session Worktree for Cursor uses Cursor's --worktree (~/.cursor/worktrees/<repo>/<name>), not HAPI's sibling-directory worktree.
Mid-session: send /worktree, /apply-worktree, /delete-worktree, or /add-dir <path> (isolated pass-through).
CLI: hapi cursor --cursor-worktree feature-x --cursor-add-dir ../shared

Slash pass-through (remote)

These commands are isolated in the queue and forwarded to the agent (ACP prompt or legacy -p):

/compress /summarize /compact /model /multitask /best-of-n /worktree /apply-worktree /delete-worktree /add-dir /context /fork /auto-review

Interactive TUI-only commands (/config, /mcp, /sandbox, /btw, /rewind, …) are not supported remotely.

Modes

Local mode - Run hapi cursor from terminal. Full interactive experience.
Remote mode - Spawn from web/phone when no terminal. New Cursor sessions use agent acp with HAPI permission approval, plan/question UI, and richer tool updates. Legacy sessions created before the ACP migration may still resume via the old agent -p stream-json path temporarily.

Limitations

Multitask UI - /multitask is slash-driven; HAPI does not yet provide an Agents Window-style fleet pane. Subagent cursor/task notifications show as CursorTask cards when the agent emits them.
Legacy sessions - Cursor sessions created before the ACP migration can still resume temporarily via stream-json. Start a new Cursor session to get ACP permissions, plans, todos, and question support.
Session resume - ACP sessions resume through session/load. Old stream-json session_id values are not loadable via ACP; those sessions keep using the legacy path until you start fresh.

Legacy stream-json safety: AskQuestion behavior

New cursor remote sessions go through ACP, which handles AskQuestion via the bidirectional cursor/ask_question extension method and is immune to the issue below. The intercept described here exists only for legacy sessions that resume via the older agent -p stream-json launcher.

When running cursor-agent under --print --output-format stream-json, the cursor-agent CLI returns a synthetic Questions skipped by the user, continue with the information you already have response for the AskQuestion tool because there is no IDE surface to render the question. The agent's underlying model can interpret this as legitimate user consent and act on it.

HAPI's legacy event converter intercepts this synthetic response and rewrites it to an explicit no_input_surface error (status: failed), so downstream consumers (web UI, Telegram, log readers) surface the fabrication as an error instead of silently passing through fabricated consent. The intercept scans the raw tool_call payload for the literal marker text and is scoped to AskQuestion-shaped (and converter-fallback name=unknown) calls; legitimate read/write/function tools are not affected.

The intercept drains naturally with the legacy session population - resumed pre-ACP sessions are the only path that still hits this code.

Tracking issue: tiann/hapi#784.

Integration

Once running, your Cursor session appears in the HAPI web app and Telegram Mini App. You can:

Monitor session activity
Approve permissions from your phone
Send messages when in local mode (messages queue for when you switch)

Cursor CLI Documentation
How it Works - Architecture and data flow

5.0 KiB Raw Blame History