Warp now has built-in support for the Grok Build CLI. - Use Warp's rich input for agent prompts, with support for longer pasted prompts and multi-cursor - Use /remote-control to share your agent session to another device - Access the file explorer and code review panels

Not enough people use /create-workflow in grok build! Today, it saved me 10k+ tokens by updating the harness (my plugins) to learn from how I've been using it. Here's how: I told grok to /create-workflow to map reduce every single trace on my laptop to find: - repeated phrases I can turn into skills (made 2 new ones) - skills i should update since the codebase has changed (updated 10) - plugins/mcps/skills I don't use I can delete (deleted 50+!!) My prompt was: ``` /create-workflow to read EVERY single traces in my ~/.grok. One agent should read one trace itself and explain what it found: phrases OUTSIDE of skills, skills used (which ones + count), mcps used + count, area of the codebase and type of PR I was making (feature, bug fix, etc), and so on. Then, have one agent for every 10 traces map reduce this information alongside context from the codebase (e.g. skill filepath references) over and over again until we get a synthesis of: - repeated phrases I can turn into skills OR add into my pre-existing skills - skills i need to update since they are old - plugins/mcps/skills with low usage I can delete Present this information as a concise report that we can actionably work on together (present a short version to me and a fully fledged markdown doc in /tmp for yourself). We will then make these changes after I confirm. ``` I need to iterate a little more, but I'll ship this as a /learn skill soon :0