Skip to main content

    Filter by idea status

    Filter by product

    4862 Ideas

    Native CLI functionality within MiroOpen

    This is a copy and paste from one of our users. Hey folks, we use Miro for architectural diagrams and would benefit from an official CLI. Agents do best when they write code [1]. The shell provides a mechanism for composing tools in code via the shell language and pipes. Agents utilize both general purpose languages like Python [6], and DSLs like jq [4], to compose pipelines which can then be saved as new utilities.CLI tools help to manage context in multiple ways [2][3]:By enabling the composition of output into filters [5], the agent is not forced to consume the full output of a tool call, conserving the context window. By allowing progressive discovery of documentation via --help and man pages, the agent only fills its context with documentation when it needs to utilize the tool. This is similar to the skills mechanism included in some harnesses.Since the CLI is utilized by both the agent, humans, build pipelines, etc.; any workflows or utilities utilized by the agent can be incorporated into a deterministic workflow.A CLI could be automatically generated from OpenAPI specifications, in the style of gws [7], which provides a discoverable command hierarchy and encapsulates the specific REST calls.[1]: https://machinelearning.apple.com/research/codeact[2]: https://lucumr.pocoo.org/2025/8/18/code-mcps/[3]: https://blog.cloudflare.com/code-mode/[4]: https://jqlang.org/[5]: https://www.cs.dartmouth.edu/~doug/reader.pdf[6]: https://arxiv.org/pdf/2503.17181v1[7]: https://github.com/googleworkspace/cli

    Aman Sharma
    Aman SharmaNew Here

    Please bring back legacy smooth transitions / panning in Presentation ModeOpen

    I’d like to request that Miro restore the legacy presenter transition behavior, or provide it as an optional mode in Presentation Mode. For years, I built my presentations around smooth panning and fly-through transitions between frames and concepts. That motion was not just cosmetic — it was a core part of how I structured and delivered my work. It made presentations feel connected, engaging, and distinctly Miro.This is now urgent for me because I have over a dozen slides/frames built around that capability, and I have an upcoming talk next week that depends on this presentation style. The newer static presentation experience materially disrupts that workflow and makes much of my existing work far less effective as designed.I also want to note that this approach had broader value beyond my own use. After previous talks, several people reached out asking how I built those slides, and some started using the same style themselves. That suggests this capability is valuable to more than just one workflow — it helps people create presentations that are memorable, interactive, and easy to follow.I completely understand that product direction evolves, but removing this behavior without an option to preserve it creates a real regression for long-time users. I respectfully ask that Miro either bring back the legacy transition behavior or add a toggle so users can choose between static slides and the smoother, more dynamic presentation style.