What it is
One Workspace is the equivalent of the software repo for knowledge work: the place where context, tools, artifacts, history, and future work can compound.
Homebase Building Block
One Workspace.
A persistent workspace where files, notes, outputs, tools, procedures, and history accumulate instead of disappearing into chat sessions.
Calls server parsing with rate limits.
The work repo for a non-coder
Scattered context gets a durable home.
Click a source to see what kind of context it contributes to the workspace.
Inbox
open asks and active tasks
Files
source documents and datasets
Notes
rough thinking and summaries
Artifacts
durable outputs and templates
Tools
scripts and generated interfaces
Memory
preferences and reusable context
Work log
what happened and why
Permissions
read, write, send, delete boundaries
PDFs contributes
Research packets, citations, policies, and evidence trails.
Software has repos. Knowledge work needs a workspace that plays the same role.
Problem
Chat sessions and project folders fragment work. Users keep rebuilding context because the product is not where the work lives.
How it works
- Persist files, notes, decisions, outputs, and procedures in one professional workspace.
- Allow projects to exist inside the workspace without becoming the whole container.
- Keep work history and reusable context available for future tasks.
Why it matters
- Every completed task should increase the value of the next task.
- Persistent context reduces repeated explanation.
- The workspace becomes a user's professional memory and toolbench.
Behavior
Good behavior
The system reuses last month's report format, the latest CSV export, and the saved review procedure before starting the next recurring analysis.
Bad behavior
The user has to re-upload, paste, and explain the same context again.
Recruiter signal
This shows product judgment around trust, AI UX, systems thinking, and the difference between useful automation and opaque automation.