Getting started
DagFlo turns a prompt, code context, or technical system into an editable visualization. Start with a short description of what you want to explain, then refine the resulting diagram with follow-up instructions.
For a guided first diagram, visit Setup. You can also explore the product overview to see the kinds of visualizations DagFlo can create.
Creating and editing diagrams
Be specific about the audience, the important components, and the relationship you want to show. For example: “Show how a webhook flows from checkout through retry handling to our warehouse system.”
- Use follow-up instructions to add, remove, rename, or regroup elements.
- Ask DagFlo to simplify a dense diagram, add annotations, or focus on a particular flow.
- Save your work so you can return to it, revise it, or share it later.
If a result is not quite right, describe the desired change rather than starting over. Iterative instructions usually produce the clearest diagram.
Using DagFlo with MCP
DagFlo can connect to supported coding agents through the Model Context Protocol (MCP), allowing an agent to send relevant project context at your direction and request a visualization.
- Review each coding-agent request before authorizing it.
- Share only the files and context needed for the diagram you are creating.
- Do not authorize prompts or context containing passwords, API keys, private keys, or other sensitive credentials.
If an MCP connection fails, include your coding-agent name, the action you were attempting, and any error text in your support request.
Account and data help
For help with sign-in, account access, diagrams, or data requests, email us from the address associated with your DagFlo account. We may ask for additional details to verify account ownership before making account-level changes.
For privacy questions or deletion requests, see our Privacy Policy or email hello@dagflo.com.
Contact support
Email hello@dagflo.com and tell us what you were trying to do, what happened instead, and any relevant link or error message. Screenshots are helpful when the issue involves the diagram editor or layout.
Please do not include passwords, access tokens, private keys, or other secrets in your message. We’ll use the information you provide to investigate and respond to your request.