stacktaste init or stacktaste agents add cursor writes three things under .cursor/. Re-run agents add cursor after a CLI upgrade so new hook events land.
Files#
| File | Role |
|---|---|
.cursor/mcp.json | Starts stacktaste mcp on stdio |
.cursor/hooks.json | Session hooks plus tool / shell / MCP gates |
.cursor/rules/stacktaste.mdc | Always-apply ranked taste |
Hooks#
| Event | What happens |
|---|---|
sessionStart, beforeSubmitPrompt, afterFileEdit | Ranked taste as additional_context |
stop | Harvests “do not use X” into a proposed item |
preToolUse, beforeShellExecution, beforeMCPExecution | Allow, or StackTaste Alert and deny |
Gate hooks use failClosed so a crashed check does not silently allow the call. Hooks print JSON only.
StackTaste Alert#
The user sees the policy title and the full reason. The action does not run.
The agent is told: do not retry or work around it; ask the user if they want an exception; wait for an explicit yes; do not execute the blocked action.
The agent cannot force a blocked tool. A chat “yes” does not disable the policy. Accept an exception from stacktaste review or the dashboard.
MCP#
See MCP overview. Cursor launches the server. You do not start it by hand.
Dashboard#
/{org}/{project}/agents → Cursor tab is live. Other tabs say Coming soon.