I like how both Jetbrains Junie and Claude code allows you to specify a markdown file with system prompt rules etc.
Warp's rules options are un-intuitive right now, because it's not clear to me if I should be adding every rule one by one or I can dump a bigger set of rules there as a markdown? (like Claude.md and .junie/guidelines.md)
I think providing a path or input field for a whole markdown file that would be passed as a context or system prompt would be better. Bonus point if we could link them to specific projects/directories
#Guidelines.md file instead of individual rules for some system prompt context
young nymph
glossy swiftBOT
Hi @young nymph. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Currently, Warp’s Rules feature is designed for users to add, edit, and manage individual rules through the UI, each with a name and description. These rules are then used to guide agent responses according to your coding standards, project conventions, or personal preferences. However, the knowledge sources do not mention support for importing or referencing an entire markdown file (like Claude.md or .junie/guidelines.md) as a set of rules, nor do they describe a way to link such files to specific projects or directories.
There is user feedback and feature requests suggesting the need for project- or directory-specific rules, and for more intuitive ways to manage sets of rules—such as folders or toggling rules on/off per project. Some users have specifically mentioned wanting a system similar to what you describe, but as of now, this is not a built-in feature in Warp. The current workflow requires adding rules individually via the Rules pane, and there is no documented support for bulk importing rules from a markdown file or automatically associating them with directories or projects. These ideas are being discussed in the community, and feature requests have been submitted, but they are not yet implemented features in WarpRules documentation Feature request: Rules folders and toggling.
In summary:
- You must currently add rules one by one in Warp.
- There is no official support for referencing a markdown file as a rules source or for project/directory-specific rule linking.
- These features have been requested by users, but are not available yet.
If this is important to your workflow, you may want to upvote or comment on the relevant feature requests to help prioritize them.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
young nymph
@glossy swift you mentioned:
If this is important to your workflow, you may want to upvote or comment on the relevant feature requests to help prioritize them.
But isn't this exact post a feature request? Or there's a better place to submit or look through feature requests?
glossy swiftBOT
Let me check the knowledge base for you again. One moment! :books:
Yes, your post here is essentially a feature request, and it aligns with similar feedback already submitted by other users. However, the best and most effective place to submit or track feature requests for Warp is their GitHub Issues board. This is the official channel where the Warp team collects, prioritizes, and provides updates on feature requests. Other users can also upvote and comment on issues, which helps the team gauge interest and prioritize development accordingly.
You can also search existing feature requests on GitHub to see if your idea has already been submitted, and add your support or additional context there. This process is recommended by Warp in their documentation and FAQs as the preferred way to provide feedback and request new features FAQ Sending Feedback & Logs.
In summary:
- Submitting or upvoting feature requests on the Warp GitHub Issues board is the best way to influence Warp’s roadmap and get updates on your request.
- You can also use the in-app "Send Feedback" option, but GitHub is the main public forum for feature requests.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
sharp roost
@young nymph @glossy swift - can confirm. The 'rules' in this application need loving. This is feedback.
glossy swiftBOT
Let me check the knowledge base for you again. One moment! :books:
Thank you for your feedback regarding the Rules feature in Warp. The need for improvements and more intuitive management of rules has been echoed by other users as well. There are active discussions and feature requests in the Warp community and on GitHub about making Rules more flexible—such as supporting project-specific rules, folders, toggling rules on/off, and even file-based approaches similar to what you described (e.g., referencing a markdown file for system prompt context) Feature request: Rules folders and toggling.
If you’d like your feedback to directly influence Warp’s development, the best place to submit or upvote feature requests is the Warp GitHub Issues board, as this is where the team tracks and prioritizes user suggestions. You can also use the in-app "Send Feedback" option or join the community on Discord for discussion, but GitHub is the primary channel for feature requests and updates Sending Feedback & Logs.