Files and knowledge
Attach reference material once and retrieve relevant chunks when the active model needs them.
Public launch: July 12, 2026 · Projects
Long-running work needs a home, not another loose chat.
Projects are the workspace layer for recurring work: chats, files, instructions, memories, artifacts, connectors, and model preferences grouped under one objective.
FilesInstructionsChatsArtifactsMemory
Project anatomy
Make repeated work feel continuous.
Standing behavior
Store tone, format, constraints, project goals, and model preferences without re-prompting every chat.
Multiple threads, one objective
Let users run parallel conversations under the same project while preserving project-level context.
Outputs stay attached to the project
Reports, dashboards, docs, and prototypes should be discoverable from the project after the chat is gone.
Project memory is not magic
Show what AGI remembers, where it came from, and how to remove or import it.
Team context hub
Teams need shared projects with role-aware access and clear restrictions for shared chats and connected data.
Implementation bar
What project pages should promise.
| Create | Name, description, icon, and optional starter instructions. |
| Upload | Files process into searchable project knowledge, with status and errors visible. |
| Retrieve | AGI searches project knowledge rather than blindly loading everything. |
| Move | Eligible chats can move into projects and inherit context from that point forward. |
| Share | Team projects need access rules, shared files, and clear connector restrictions. |
Public launch: July 12, 2026
Projects are where AGI becomes a work OS.
Use this page to explain why users should create durable workspaces instead of treating AGI as a disposable chat box.