This quickstart is the shortest path to "Filepad makes sense to me" — one workspace, one document, one reviewed change.
1) Create a workspace
Sign in and create a new workspace. Name it something you'd keep for months (client-alpha, content-pipeline, research-q3).
Your workspace starts with an empty file tree. There's no fixed folder scaffold — you organize it however the work needs.
2) Add or create a document
Upload a source file, or create a new artifact directly in Filepad — a note, a sheet, a diagram, whatever the work calls for. Every artifact you create or edit is versioned automatically.
3) Talk to FilepadAI
Open a thread and ask FilepadAI to do something with the document — summarize it, draft a section, restructure a sheet. You'll see its working trace (what it searched, what it read) and the final result.
4) Review a governed change
If the action FilepadAI takes is higher-risk (editing an existing document, moving files), it may pause and ask for your approval before the change lands. Review the diff, then accept or reject it. Nothing lands until you decide.
5) Connect an external agent (optional)
If you have a pipeline or external agent that should report into this workspace, open the Agents tab and create an Agent Access key. Grant it only the scopes it needs:
events.write— push activity events back to Filepadsignals:write— raise findings for the workspace to seenotifications:read— read and acknowledge its mailbox
For an agent that needs to search, read, or edit workspace content directly, connect it to the MCP endpoint (/mcp) instead, with scopes like artifacts:read, artifacts:write, or memory:read/memory:write. Higher-risk writes from external agents go through the same approval flow as FilepadAI's.
Copy the key secret when you create it — it's shown once.
Next: Core concepts — the mental model behind workspaces, artifacts, and governed writes.