AgentsInFlow
AgentsInFlow
v0.14.0

One Workspace for
All Your AI Agents

AgentsInFlow: Run Claude Code, Codex, and Cursor in one desktop app with git control, diagrams, and persistent memory

Run Claude Code, Codex, and Cursor from one window. Git version control, 28 diagram types, persistent AI memory, and isolated branching. Close everything else.

AgentsInFlow Kanban Board - Manage AI tasks across projects

// every feature solves a real problem

Built from Real Workflow Friction

Nothing was added speculatively. Each capability exists because something was broken in daily AI-assisted development. Here is what we solved, and how.

1

// the first problem

Too Many Apps Open

Working across multiple projects, personal and professional, meant Cursor in three windows, a dozen terminals, SourceTree for git, and constant context switching between all of them. The goal was simple: consolidate everything into one workspace with just what you need. No plugins, no noise.

Multiple projects, one window

What was built:

  • Multi-project workspace where each project gets its own scope, tabs, and state
  • Kanban board to see all tasks at a glance across statuses
  • Cross-project active agents panel so you never lose track of running work
2

// code became a black box

Let the AI Show You

With the latest models, you no longer review code line by line. You review by asking targeted questions. But when something gets too complex to understand through text alone, you need the AI to communicate visually. That is why diagrams were added: to give the AI a way to show you what it built, not just tell you.

28 diagram types + freehand sketching

What was built:

  • 28 diagram types: Mermaid, PlantUML, Graphviz, D2, DBML, BPMN, C4, ERD, and more
  • Freehand sketching canvas for quick visual notes
  • Diagrams render inline in both ticket descriptions and assistant chat
Flowcharts and sequence diagrams rendered inline in AgentsInFlow
3

// ideas move faster than typing

Capture at the Speed of Thought

If your mind generates ideas faster than your hands can type, you need tools that keep up. A new task should be one shortcut away. When even a shortcut is too slow, just speak. But a raw transcript is too shallow for an agent to execute. So the assistant takes over: it turns your rough idea into a proper ticket with a detailed description, creates it, and you can forward it to an agent immediately.

Voice, shortcuts, and AI assistant

Capture fast:

  • Cmd+G for instant ticket capture without breaking flow
  • Voice-to-text transcription built in (OpenAI Whisper), no separate app needed
  • Fast Prompts: reusable prompt actions you configure once (Commit, Merge, Mark as Done) with template variables like #{branch} and #{ticketId}, pinned to an action bar for one-click execution

Then let the assistant handle the rest:

  • Talk to the assistant and it builds a proper ticket with a detailed description for you
  • The assistant can manage your tickets: rename, reorganize, move status, close, and brief you on progress
  • Full MCP access to your application: the assistant acts on your behalf across all your projects
  • Multiple assistant chats if you prefer to work with chat as your primary interface
Fast Prompt actions and project memory settings in AgentsInFlow
4

// multiple agents, one branch = disaster

Let Agents Run Free

When you have multiple agents working at the same time, they cannot all be on the same branch. They will overwrite each other. So a proper branching system was needed: isolated worktrees where each agent gets its own branch, with memory propagation and manual merge-back when you are ready.

Isolated worktrees per agent

What was built:

  • Isolated git worktree per execution, agents cannot interfere with each other
  • Automatic branch naming from ticket type and title
  • Merge-back stays manual and under your control
Git graph with worktree branches and inline diffs in AgentsInFlow
5

// agents forget everything between sessions

Never Forget

Every time you start a new session, the agent starts from zero. All the context from yesterday, the decisions, the constraints, the architecture, gone. So persistent memory was added: per-project and per-assistant, stored locally in .aif/ and carried across every session.

Persistent, local, private

What was built:

  • Project memory that agents auto-capture and reference across sessions
  • Assistant memory for the built-in chat, separate from agent context
  • All stored locally on disk, toggle or clear from Settings at any time
Project memory and keyboard shortcuts settings in AgentsInFlow
6

// switching apps for each engine is friction

All Engines, One Ticket

Claude Code, Codex, and Cursor each have their strengths. You want to use all of them without switching applications. One ticket can now have multiple executions on different engines. Run the same task on Claude and Codex, compare the approaches, keep the best one.

Claude Code, Codex, Cursor

What was built:

  • Multiple executions per ticket, each on a different CLI engine
  • Token analytics per execution so you know the cost of each approach
  • Runtime MCP injection so each engine gets the tools it needs automatically
Claude Code, Codex, and Cursor engine configuration in AgentsInFlow
7

// complex projects need structure

Orchestrate the Work

A flat list of tasks does not scale. Complex projects need hierarchy, dependencies, and visibility into what blocks what. Task hierarchy replaced flat subtasks. Dependencies enforce execution order. Sub-ticket executions are grouped under their parent. And this is just the first layer.

Hierarchy, dependencies, control

What was built:

  • Parent/child ticket hierarchy with nested children visible on the kanban board
  • Ticket dependencies that enforce execution order
  • MCP-based orchestration layer on top of each engine's native capabilities
Task hierarchy with children tabs and flowcharts in AgentsInFlow

// more of what it looks like

See It in Action

Freehand sketching with AI analysis in AgentsInFlow

Sketch on the canvas, then ask the AI to describe what it sees

Assistant chat with C4 System Context diagram in AgentsInFlow

Assistant generating C4 System Context and Container diagrams

C4 Container diagram with full architecture breakdown in AgentsInFlow

C4 Container diagram showing the full system architecture breakdown

// where we are now

That Is How We Got Here

One window. Git version control, file explorer, terminal, rich editor, kanban board, 28 diagram types, voice input, persistent memory, three AI engines, and full orchestration. Close everything else.

3

AI Engines

28

Diagram Types

1

Window Needed

0

Other Apps

Ready to Build with AI Agents?

Free during beta. We'd love your feedback and feature requests.