warp-allow-notify
Write the Cursor allowlist so Slack and Jira calls Warp makes do not stop for Allow or Run.
Skill by smlsr
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/smlsr-warp-allow-notify
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: writing, productivity, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/warp-allow-notify
What's inside
- Skill name
warp-allow-notify- Description
- Write the Cursor allowlist so Slack and Jira calls Warp makes do not stop for Allow or Run. Use when a prompt names slack_send_message or addOrEditJiraIssueComment, or after init if autoAllowTools was off.
- License
- MIT
- Instructions
- 53 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- files: referenced but missing: scripts/mcp_tools.py, scripts/mcp_allow.py
Files (1)
- SKILL.md
SKILL.md (first lines)
# Allow notify `/warp-init` writes this list for the project when `autoAllowTools` is true. Run this command to refresh it, to add `--with-git`, or to edit user-level files after an explicit yes. Tool names come from `scripts/mcp_tools.py`. Jira tools are included. Extra pairs come from `notifyAllow` in `.warp/config.yaml`, each one `server:tool`, with no wildcard. `server:*` is written only with `--allow-server-tools`, and that allows every tool on the server, including destructive ones. ## Which Cursor surface this changes | Surface | What the script writes | What it does | |---|---|---| | IDE, this repo | `.cursor/permissions.json` `mcpAllowlist` | Skips the Run prompt for those tools when Run Mode is Auto-review, Allowlist, or Run Everything. | | IDE, all repos | `~/.cursor/permissions.json` `mcpAllowlist` | Same, only with `--user` after an explicit yes. | | CLI, this repo | `.cursor/cli.json` `permissions.allow` `Mcp(server:tool)` | Cursor CLI and headless runs. Does not change the IDE Run button. `agent -f` approves tools for that process. | | CLI, all repos | `~/.cursor/cli-config.json` | Same, only with `--user`. | | Hook | `.cursor/hooks.json` or `~/.cursor/hooks.json` `beforeMCPExecution` | Local IDE only. Returns allow for this list and ask for every other tool. A hook allow does not currently skip the Run prompt. The permissions file does. Cloud runners do not execute this hook. | | Cloud agents and automations | `scripts/mcp_allow.py` | They do not use Run Modes and do not ask for approval. Plugin hooks do not run there. Call an MCP tool only when `mcp_allow.py` prints `allow`. `ask` means do not call it. The list is the same Slack, Teams, Jira, and optional GitHub pairs, not every tool. | Setting `mcpAllowlist` replaces the in-app MCP allowlist. Entries that exist only in Cursor Settings prompt again until they are in the file. The terminal allowlist and `autoRun` are left alone. Ask Every Time does not consult the file. A team admin Run Mode override ignores it. The default list is Slack (post and the `warp:status` reads), Teams, and Jira, on the configured name plus `user-<name>`, `project-<name>`, `plugin-<name>-<name>`, and `*<name>*:<tool>`. `--with-jira` changes nothing. `--with-git` adds GitHub `add_issue_comment`, `merge_pull_request`, and `create_pull_request` only. Warp does not name a Bitbucket comment tool; that belongs in `notifyAllow`. `--list` and `--check` write nothing. `--check` is the diagnostic when a prompt is still there. ## Run `python3 <plugin>/scripts/allow_notify.py ?` prints every option (`help`, `-h`, and `--help` do the same). Quote `?` if the shell expands it. Show that output when the user asks what the command can do. 1. Show a dry run first. This writes nothing. ```bash python3 <plugin>/scripts/allow_notify.py --dry-run ``` Add `--with-jira` and/or `--with-git` when the user asked for those tools too. Read the diff to the user, including which files change. 2. Project scope is the default. Running this command is the user's ask to edit the project files. After the dry run, apply it: ```bash python3 <plugin>/scripts/allow_notify.py ``` 3. User scope (`--user`) edits files in the home directory. Stop after the dry run. Ask, in your own words, whether to edit `~/.cursor/permissions.json`, `~/.cursor/cli-config.json`, and `~/.cursor/hooks.json`. Wait for an explicit yes. Silence or a vague reply is a no. Only then: ```bash python3 <plugin>/scripts/allow_notify.py --user --dry-run python3 <plugin>/scripts/allow_notify.py --user --yes ``` The script refuses `--user` without `--yes`. 4. Tell the user what changed, and tell them to reload Cursor (Developer: Reload Window) or start a new agent chat. Run Mode has to be Auto-review, Allowlist, or Run Everything. If the prompt names a tool that is not in the list, add `server:tool` to `notifyAllow` and run the command again. `--revoke` removes only the entries the manifest recorded. It does not remove entries the user already had. `/warp-uninstall` does that revoke for the project files only.
From smlsr/Warp, MIT.
More from smlsr/Warp
- 0.565score
warp-jira-map
smlsr
Map plan ticket ids to real Jira issue keys.
SkillAFreshness: AClaude Code +9 - 0.565score
warp-sync
smlsr
Read Jira statuses into the beam.
SkillAFreshness: AClaude Code +9 - 0.565score
warp-jira-check
smlsr
Explain, per ticket, which Jira transition and which Jira or pull-request comment should have happened, what the beam recorded, and what is missing.
SkillAFreshness: AClaude Code +9 - 0.565score
warp-cleanup
smlsr
List registered Warp agents and clear idle or leftover cloud agents for this repo.
SkillAFreshness: AClaude Code +9 - 0.565score
warp-status-post
smlsr
Post Warp status to Slack and Teams, including the status files.
SkillAFreshness: AClaude Code +9 - 0.561score
warp-scan
smlsr
Scan any repo, or one folder of it, for CURSOR_PLAN.md, schedule.json, a build map, or a Jira ticket export and build the Warp plan.
SkillAFreshness: AClaude Code +9 - 0.561score
warp-jira-external-id
smlsr
Write the plan id into Jira's External ID field for tickets that are already mapped.
SkillAFreshness: AClaude Code +9 - 0.561score
warp-jira-match
smlsr
Link unmapped Warp tickets to Jira issues by summary.
SkillAFreshness: AClaude Code +9 - 0.561score
warp-alarm
smlsr
Raise, record, and clear Warp alarms when a PR cannot pass Bugbot, a lock is escaped, or a ticket is stuck.
SkillAFreshness: AClaude Code +9 - 0.560score
shuttle-run
smlsr
Run one claimed ticket on its own VM, or in its own git worktree, through an open pull request.
SkillAFreshness: AClaude Code +9 - 0.560score
warp-from-jira
smlsr
Build the plan files /warp-scan reads from the Jira issues that carry one or more labels, for example /warp-from-jira version:1.5.5,ui.
SkillAFreshness: AClaude Code +9 - 0.560score
warp-status
smlsr
Write and report the Warp status file: done, working, and left.
SkillAFreshness: AClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 14, 2026 (16 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/smlsr/Warp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from smlsr
- 0.565score
warp-status-post
smlsr
Post Warp status to Slack and Teams, including the status files.
SkillAFreshness: AClaude Code +9 - 0.565score
warp-sync
smlsr
Read Jira statuses into the beam.
SkillAFreshness: AClaude Code +9 - 0.565score
warp-jira-check
smlsr
Explain, per ticket, which Jira transition and which Jira or pull-request comment should have happened, what the beam recorded, and what is missing.
SkillAFreshness: AClaude Code +9 - 0.565score
warp-cleanup
smlsr
List registered Warp agents and clear idle or leftover cloud agents for this repo.
SkillAFreshness: AClaude Code +9 - 0.565score
warp-jira-map
smlsr
Map plan ticket ids to real Jira issue keys.
SkillAFreshness: AClaude Code +9 - 0.561score
warp-jira-match
smlsr
Link unmapped Warp tickets to Jira issues by summary.
SkillAFreshness: AClaude Code +9
Cite this page
warp-allow-notify skill. Agent Mart. https://agentmart.dev/skills/smlsr-warp-allow-notify (last updated 2026-10-24)