Add import context docs

docs.json

@@ -30,6 +30,7 @@
         "pages": [
           "features/chat",
           "features/connectors",
+          "features/imports",
           "features/mcp",
           "features/skills",
           "features/tasks",

features/imports.mdx

@@ -0,0 +1,144 @@
+---
+title: Imports
+sidebarTitle: Imports
+description: Bring useful context from ChatGPT, Claude, or another agent into Fluso as projects, files, and context.
+---
+
+Imports move useful context from another AI product into Fluso.
+
+This is context migration, not chat migration. Fluso reads an export zip and turns the useful parts into projects, files, and markdown context. It does not recreate your old ChatGPT or Claude conversations as native Fluso chats.
+
+Use imports when you already have work somewhere else: project notes in another agent, ChatGPT conversations with research and drafts, Claude conversations with decisions, or a folder of files an agent can package for you.
+
+## What gets imported
+
+Fluso creates:
+
+- Projects for high-confidence areas of work.
+- `context.md` files with goals, decisions, useful conversations, and next steps.
+- Supporting files and attachments when the export includes them.
+- A Home spillover file for useful context that does not deserve its own project.
+
+Low-signal conversations stay out of the project list. The import is meant to give Fluso working context, not a complete archive.
+
+## Open the import dialog
+
+Open **Projects** from the left sidebar. Click **Import** in the top right.
+
+<Frame>
+  <img src="/images/features/imports/projects-import-button.png" alt="Fluso Projects page in dark mode with an Import button and New Project button in the top right." />
+</Frame>
+
+The dialog is called **Import context**. Pick the source, follow the instructions, then upload the zip.
+
+<Frame>
+  <img src="/images/features/imports/import-dialog-agent.png" alt="Import context dialog with source tabs for Agent app, ChatGPT, and Claude. The Agent app source is selected, showing a copyable export prompt and a zip upload area." />
+</Frame>
+
+## Sources
+
+### Agent app
+
+Use this for Claude Cowork, OpenClaw, Perplexity Computer, and similar agent tools.
+
+Click **Copy** next to the export prompt, paste it into the agent you want to export from, and let it build `fluso-import.zip`.
+
+Before you upload the zip, skim the `MANIFEST.md` the agent prints. Check that real files were copied, especially logs, trackers, notes, datasets, and per-entry files. If the bundle is only a few kilobytes of summaries, ask the source agent to copy the original files instead.
+
+The expected shape is:
+
+```text
+fluso-import.zip
+  project-a/
+    context.md
+    conversations.md
+    decisions.md
+    files/
+      ...
+  project-b/
+    context.md
+    files/
+      ...
+```
+
+Each top-level folder becomes a Fluso project. Files inside it become that project's files. A root `context.md` becomes the project's context.
+
+### ChatGPT
+
+Use the official ChatGPT data export.
+
+1. In ChatGPT, open **Settings → Data controls → Export data**.
+2. Confirm the export.
+3. Wait for the "Your data export is ready" email.
+4. Download the zip and upload it to Fluso. Do not unpack it first.
+
+The email link expires after 24 hours.
+
+### Claude
+
+Use the official Claude data export.
+
+1. In Claude, open **Settings → Privacy**.
+2. Select **Export data**.
+3. Wait for the email from Anthropic.
+4. Download the zip and upload it to Fluso.
+
+Large Claude exports may arrive as multiple batch files. Import them one at a time.
+
+## What happens after upload
+
+After you click **Start import**, Fluso creates a real import thread in the Home project and starts the import there.
+
+You can close the dialog. The import keeps running. Reopen the thread from the dialog if you want to watch the work happen.
+
+When the import finishes, the dialog shows the projects created, files added to Home, skipped items, and warnings. The thread also ends with a readable summary.
+
+## Limits
+
+| Item | Limit |
+|---|---|
+| Upload file | `.zip` only |
+| Zip size | 300 MB |
+| Sources | Agent app, ChatGPT export, Claude export |
+| Projects | Up to 8 planned; 10 hard limit |
+| Files per project | 500 |
+| Claude batches | Import one batch at a time |
+
+If a project name already exists, Fluso keeps both by adding a number to the imported project name.
+
+## Good imports
+
+A good import has real source material, not just summaries.
+
+For official ChatGPT and Claude exports, upload the downloaded zip unchanged.
+
+For agent-app exports, use the prompt in the dialog and check the manifest before uploading. The manifest should show the files and folders the source agent found, with each item marked as copied or summarized.
+
+<Tip>
+  For projects with logs, trackers, journals, spreadsheets, or datasets, preserve the original files. A summary is useful context, but it should not replace the detailed record.
+</Tip>
+
+## Troubleshooting
+
+<AccordionGroup>
+  <Accordion title="The zip is rejected">
+    Check that you uploaded a `.zip` file under 300 MB. For ChatGPT and Claude, upload the official export zip without unpacking it.
+  </Accordion>
+  <Accordion title="The import failed">
+    Open the import thread from the dialog. The thread usually shows the step that failed and what Fluso tried before stopping.
+  </Accordion>
+  <Accordion title="The agent-app bundle only imported summaries">
+    Go back to the source agent and use the export prompt again. Ask it to copy the original files and print the manifest before zipping the folder.
+  </Accordion>
+  <Accordion title="I expected more projects">
+    Fluso groups conservatively. One-off or weak conversations go into a Home spillover file instead of becoming separate projects.
+  </Accordion>
+</AccordionGroup>
+
+## Next
+
+After importing, open one of the new projects and ask:
+
+> *"Summarise this project. What is decided, what is still unclear, and what should I do next?"*
+
+For project habits after import, see [Going deeper](/going-deeper#use-projects-properly).

going-deeper.mdx

@@ -49,6 +49,8 @@ Drop a `context.md` into the project's workspace if your context is non-obvious.
 
 Fluso reads it before answering anything inside the project. The cost is two minutes; the payoff shows up in every reply for months.
 
+If you are bringing work over from ChatGPT, Claude, or another agent, use [Imports](/features/imports) to turn that context into Fluso projects and files.
+
 For developer projects, `context.md` is where your stack and conventions go:
 
 ```markdown

quickstart.mdx

@@ -88,6 +88,8 @@ For example:
 
 The first goal is not to organize everything. The first goal is to give Fluso enough context to produce one useful answer.
 
+If that context already lives in ChatGPT, Claude, or another agent, use [Imports](/features/imports) instead of rebuilding the project by hand.
+
 ## Step 4: connect one or two tools
 
 Connect the tools that hold the project context.