Everything you need to master FlowState

Resources

Video tutorials, comprehensive guides, and community support to help you orchestrate AI like a senior engineer from day one.

7
Video Tutorials
20+
FAQ Answers
<24h
Support Response

Quick Start

Video Library

Step-by-step walkthroughs for every scenario you'll encounter

VIDEO 3

FlowState in Visual Studio & GitHub Copilot

Single vs multi-project solutions, nested .sln files, Ask vs Agent modes. Everything VS users need to know, demonstrated with real repos.

COMING SOON
VIDEO 4

Privacy & 'Invisible Mode'

Use FlowState in work repos without coworkers seeing it in git. Set up cloaked mode so FlowState files never appear in git status.

COMING SOON

Frequently Asked Questions

Answers to the questions every FlowState user asks

Getting Started & Installation

Where do I put the FlowState files in my project?
You'll put the directory containing the files at the root of the project or solution you want FlowState to orchestrate, usually where your .sln or main README lives.
Do I need to run git init before I use FlowState?
Recommended: Yes, if you're in a work repo and want invisible mode. Optional: FlowState can initialize git for you if you prefer.
Can I add FlowState to an existing project, or only new ones?
Both. It just takes longer on existing projects because it scans more files.
Which tools/editors does FlowState work with?
GitHub Copilot Chat (VS / VS Code), Claude Code, "Codex style" CLIs, etc. Anything that can: read files, write files, run shell commands, and follow text instructions.

Using FlowState Day-to-Day

How should I talk to FlowState during a session?
Treat it like a coworker: give it objectives, ask "why" it did something, and use proceed commands (proceed, proceed next, proceed all) to control the pace.
What's a "Phase 0 success metric," and how specific does it need to be?
It's the first measurable win. "Fix bug #123 so tests pass" or "Get a basic login → dashboard flow working" is enough.
What if I don't know my deployment target / subscription model yet?
It's fine to answer "local dev only" or "not decided yet"; FlowState will still work.
What is FlowState actually doing for me under the hood?
High-level: breaking work into plans, tracking tasks, enforcing engineering discipline (small files, tests, docs, logs), and remembering context across sessions.

Troubleshooting & Weird Behavior

FlowState says it's working but nothing is happening. What should I do?
Ask it to summarize its current state, list tasks, and resume the next task.
FlowState wrote a plan but didn't tell me what to do next.
Tell it: "Resume your plan, start with Task 1, and explicitly tell me when to say PROCEED."
FlowState says it can't find the framework file, but it's right there.
Have it list its working directory and confirm paths; often it's running from a different folder than you think.
Initialization looks "different" between environments. Is that normal?
Some variation is normal because of tool differences, but FlowState should always: read its core docs, ask you key questions, and produce a plan and setup logs.

Pricing & Learning

Will FlowState help me learn to code / architect, or just do stuff for me?
FlowState forces architectural thinking through its framework. You're not just getting code—you're learning systematic workflows and engineering discipline.
Can FlowState help with ML projects, like my 1D CNN virus scanner?
Yes. FlowState helps with building the scaffolding and tooling around ML projects, including experiment tracking and modeling workflows.
Will I get future updates?
You get 12 months of updates included, then optional renewals/discounted upgrades available.

Community & Support

Is there a Discord server or community for FlowState?
Yes. Join our Discord for founders/early buyers, vibe coders, and to get help from the community in our #help forum channel.
How much support do I get as a customer?
Email support, access to the founders Discord, and self-serve resources. We aim for self-serve first, 1:1 for edge cases.
I'm not a "real dev" (sysadmin, infra, etc.). Is FlowState still for me?
Absolutely. FlowState works for anyone who builds with code—DevOps engineers, sys admins, data scientists, ML engineers, and software engineers alike.

Join the Community

Connect with other FlowState users, share workflows, and get help

Discord Community

Active community of founders, early adopters, and vibe coders. Get help, share wins, and connect with others building with FlowState.

Join Discord

Need Help?

Can't find what you're looking for? We're here to help.

abe@flowstateai.dev
Average response: < 24 hours