Projects
Group related chats, knowledge, and instructions into a named workspace for a specific goal.
Projects let you create focused contexts around a piece of work — a client engagement, a research topic, a product launch, or any ongoing task. Give the project a name, write custom instructions that apply to every conversation inside it, share it with specific teammates via access grants, and pick it up exactly where you left off.
Think of a project as a persistent workspace with its own memory: the instructions you write become the default system context, and any files or notes you attach stay scoped to that project.
Why Projects?
Keep context in one place
Instead of hunting through chat history or re-attaching files every conversation, a project gives you a stable home. Everything relevant to that piece of work lives there.
Project-level instructions
Write instructions once — describe the goal, set constraints, define terminology — and every chat inside the project inherits them. You never have to re-type context you've already established.
Shared ownership
Grant read or write access to other users or groups. Team members see the same project, contribute conversations, and work from the same instructions without emailing each other the setup.
Pagination-ready for large organizations
The project list supports page-based navigation (?page=N) for instances with many projects.
Key Features
| 📝 Custom instructions | Free-form text injected as project-level context for every conversation |
| 🔐 Access grants | Share with specific users or groups with read or write permissions |
| 🗂️ Rich metadata | Attach arbitrary data and meta JSON for integrations |
| 📄 Description | Human-readable summary shown in the project list |
| 🔄 Full update | All fields updatable after creation |
Creating a Project
- Go to Workspace > Projects in the sidebar.
- Click New Project.
- Enter a name and optional description.
- Write instructions — what should the AI know about this project? What are the goals, constraints, or vocabulary to use?
- Click Create.
The project appears in your list. Open it to start conversations inside it.
Writing Good Project Instructions
Instructions are injected before your first message in every conversation that belongs to the project. Think of them as a standing system prompt scoped to this work context.
Useful patterns:
You are helping me with the Acme Corp website redesign.
The client wants a mobile-first, accessibility-first approach.
Always cite WCAG 2.1 guidelines when relevant.
Current deadline: end of Q3.
Stakeholders: Sarah (PM), James (Design), our team (Engineering).
Sharing a Project
After creating a project, open its settings and use Access Grants to add collaborators:
- Read access — collaborator can view and chat inside the project, but cannot edit the instructions or settings.
- Write access — collaborator can also edit instructions and metadata.
Access grants use the same system as model and knowledge base sharing, so you can target individual users or entire groups.
API
| Method | Path | Description |
|---|---|---|
GET | /api/v1/projects/ | List all accessible projects (paginated with ?page=N) |
POST | /api/v1/projects/create | Create a new project |
GET | /api/v1/projects/{id} | Get a specific project |
POST | /api/v1/projects/{id}/update | Update project fields |
DELETE | /api/v1/projects/{id}/delete | Delete a project |