kestrel-one

Organize team work in Projects

Give related Threads a shared team, instructions, files, Knowledge selection, and context history.

Kestrel OnebeginnerCurrent releases
Verified 2026-08-04View sourceReport a docs issue

A Project is the shared home for work that should outlive one conversation or one person. It groups the members, Threads, instructions, files, and selected Knowledge that belong to the same outcome.

Kestrel One Project home showing shared context, members, and Project Threads
A Project keeps team membership and reusable context beside the Threads that depend on them.

Create a Project

  1. Open Projects at /projects and create a Project with a recognizable name and purpose.
  2. Add only the members who should see its private context and Threads.
  3. Add concise instructions and the files or Knowledge required for the first task.
  4. Create the Thread from inside the Project.

Attach context, Knowledge, and Apps

Project instructions, files, selected Knowledge, and allowed Apps become revisioned inputs for future turns. The Environment supplies the maximum execution and capability boundary; the Project may narrow it.

Choose an Environment

Select the Environment that owns the project Workspace, runtime image, shared Apps/MCP, network policy, model paths, and activity. Confirm readiness before starting the first Project Thread.

Use Mission Control

Mission Control records work items, attempts, evidence, review, and acceptance for the Project. Conversation control and project acceptance remain separate actions.

Understand Project roles

RoleWhat the person can do
OwnerManage membership, Project lifecycle, context, files, Threads, and sharing
EditorUpdate context and files, and create or continue Threads
MemberRead and continue the Project Threads they can access

Every Project retains at least one owner. Archiving removes completed work from active views while preserving its history.

Move Threads into or out of Projects

Moving a Thread changes future access and context, not the historical revision used by prior turns. Kestrel discloses the change before it is accepted.

Confirm project readiness

At least one owner remains; intended members can open the Project; context is current; the Environment and model are ready; required Apps are allowed; and a new Thread records the expected revision.

Continue with Apps and agent capabilities to understand the personal and Environment connections available to Project work.