Meet Files: AI-Native Project Documentation

Every engineering project generates context. Specs, research, design rationale, simulation results, trade-off notes. But until now, a lot of that context lived outside of Flux: in Google Docs, local files, Slack threads, or just in your head. Even the context that was in Flux was spread across chat sessions, inspector panels, and uploaded assets. Your coworkers and the AI could only work with what they could see, and too often, the most important details were somewhere else.

Today, we're introducing the Files tab, a new top-level tab in every Flux project.

Files makes Flux the source of truth for your project. Documents, uploaded assets, generated outputs, and project descriptions all live in one place, and the AI can access all of it. The more context your project has, the better Flux works.

Find what you need in one place

The Files tab brings together everything your project need:

• Documents: longer-form markdown docs like specs, research, and design notes that live directly inside your project
• Uploaded assets: reference files, datasheets, images, and other materials you bring in
• Generated outputs: reports, simulation results, calculations, and artifacts the agent produces
• Project descriptions: the high-level summary of what the project is and what it's for

Assets that previously lived in the Inspector have moved into Files, so all of your project's supporting material is in one spot.

More context for Flux means better results for you

Files isn't just a cleaner way to organize your project. It changes how Flux works with you.

When context is scattered across chat history or living outside Flux entirely, the agent doesn't have much to work with. Files gives it access to your specs, research, prior outputs, and rationale across every session. That means better outputs, auditable work you can actually find, and continuity that builds over time instead of resetting with each new conversation.

The star of the Files tab is Documents: longer-form markdown docs that live directly inside your project. Product specs, design notes, background research, engineering rationale, test results, anything that deserves to outlive a single chat session. And Flux can create and update them for you. When you start a project, the agent can draft a living spec. As things evolve, it updates the doc to reflect new decisions, calculations, and trade-offs, so your project record stays current without extra effort on your part.

What you can do with Files

Here are a few workflows that Files makes possible:

📋 Living design spec

Start a project with a rough idea and let Flux draft a design spec: target components, power budget, key constraints. As requirements shift, the spec stays current so the agent always knows what you're building.

Checkout the project example.

💡 Deep research workspace

Flux can perform deep technical research to assess feasibility, explore architectures, and propose multiple design directions. The agent breaks the system into functional blocks and maintains dedicated documents for each—covering detailed datasheet analysis, app note insights, validated assumptions, trade-offs, and alternative approaches—so you get a structured, engineering-grade understanding of what will work and why.

Checkout the project example.

🔍 Design review report

After a schematic review, Flux can generate a full report with findings, flagged issues, and recommendations. The chat gives you the summary. Files keeps the full document for your records.

Checkout the project example.

📈 Simulation and test results the agent can reuse

Save simulation outputs or test data to Files so the agent can reference them in future sessions. No re-uploading, no re-explaining what you already tested.

Checkout the project example.

📎 Datasheets and reference materials

Upload component datasheets, reference designs, or app notes to Files. The agent can read them and factor them into its work, so you don't have to re-explain what you're working with.

Checkout the project example.

📓 Engineering decision log

As your project evolves, Flux can save the reasoning behind key decisions as a document: why you chose a certain topology, what trade-offs you considered, what changed along the way. A record you and your team can review, challenge, or build on later.

Start with a prompt, or just start writing

There are several ways to work with Files:

• Ask the agent to create a document for you. Just describe what you need in chat.
• Collaborate with the agent to refine and iterate on docs together.
• Paste in content you've written elsewhere (markdown is fully supported).
• Write directly in the built-in editor.

Flux will also automatically create documents when it's working on a bigger project for you, or when a question is best answered in long-form rather than a chat response. You can ask Flux to reference a specific doc to inform its work, and it will also try to automatically read relevant docs based on their titles.

And because everything lives in the project, your whole team has access to the same specs, decisions, and reference materials. No more context stuck in one person's chat history or local drive.

Project memory that compounds over time

Files is the foundation for how project knowledge works in Flux going forward. Your project's context grows across sessions, the AI's work is reviewable and trustworthy, and your team collaborates from a shared record of everything that matters.

This is just the start.

{{underline}}

Try it now

Open a project, click the new Files tab, and try this prompt to get started:

"Set up my project with document templates for each phase of hardware development. I need a product requirements doc, a design spec for schematic capture, a component selection and BOM tracker, a design review template, a test and validation plan, and a DFM checklist for pre-production. Include the key sections and fields I should fill out at each stage."
Try this prompt

Flux will generate a full set of templates in your Files tab, one for each phase from requirements through manufacturing. Use them as-is, customize them for your workflow, or ask the agent to start filling them in based on your project. It's the kind of documentation most teams know they should have but never get around to creating.

{{open-flux-and-try}}