Problem Description

I'm frustrated when I need to manage Warp assets because:

1. Context Switching: I have to leave the terminal and open the Warp Drive UI to add/edit content
2. No Programmatic Access: I can't automate rule/prompt, workflow, notebook, environment variable management or bulk operations
3. Limited Formatting: Current rules are plain text with no rich formatting support
4. No Project Context: Rules are global only - I can't have project-specific coding standards or workflows

This makes it difficult to:

• Quickly capture and codify new workflow patterns I discover
• Maintain different rule sets for different projects
• Create comprehensive, well-documented rules with examples using Warp's LLM, which is weird to say the least

Proposed Solution

I want the ability to create, edit, and manage Warp files directly through the AI agent, with markdown format support, similar to Claude Code's approach with context files, commands, agents, hooks and whatnot. And either using a Warp CLI and/or a Warp MCP to guide an LLM where to find those rules (list), where to create, edit and delete them.

Specific capabilities needed:

1. Warp CLI/MCP for Rules Management

• warp [content-type: rule | workflow | notebook | env-var] create "Name" --content="Content"
• warp [content-type] list - Show all current [content-type] files
• warp [content-type] delete "Name"
• warp [content-type] export --output=./prompts - Export [content-type] to markdown files in prompts folder
• warp [content-type] export --output=./prompts.md - Export [content-type] to a single markdown file
• warp [content-type] import ./prompt.md - Import file from markdown

2. Markdown Format Support for rules

• Rich formatting within rules (headers, lists, code blocks), same as with Notebooks.
• Syntax highlighting for code snippets in rules
• Support for structured documentation like Claude Code's CLAUDE.md

3. Project-Specific Rules

• Support for conventional rule files AGENT.md, AGENTS.md, CLAUDE.md, .cursorrules, .github/copilot-instructions, etc. rules (see https://github.com/johnlindquist/dotagent, https://ampcode.com/AGENT.md for more info)
• Support for .warp/rules/*.md, .warp/notebooks/*.md folders in project directories
• Support for .warp/rules.md, .warp/workflows.md single files in project directories
• Hierarchical rules that can override global settings
• Version-controlled rules

Example Use Case:

# Git Workflow Rules
When working with git:
- Always use conventional commit messages
- Run tests before pushing  
- Use `git rebase` instead of merge for feature branches

## Custom Commands
- `gac`: git add . && git commit
- `gpu`: git push -u origin $(git branch --show-current)

Benefits

• Improved Productivity: Quickly create and modify rules, workflows, notebooks without leaving the terminal
• Better Organization: Markdown format allows for structured, readable rules
• Version Control: Shareable, version-controlled prompts and notebooks
• Context Awareness: Project-specific rules that adapt to different codebases
• Automation: Bulk import/export capabilities for rule management

Related Issues

This builds upon existing feature requests:

• Warp Rules - allow for to create folder and toggle on / off #6723: File-based rules support
• Features: custom slash commands and agent hooks #6857: Project-specific configuration

Technical Considerations

• Backward compatibility with existing UI-based rules
• Security considerations for programmatic rule access
• Integration with current Warp Drive infrastructure (https://app.warp.dev/app)

Note: This feature would make Warp competitive with other AI coding assistants like Claude Code that support project-specific configuration files (CLAUDE.md) and rich markdown formatting for instructions.