01
Context that follows the work
Chats, files, instructions, and discussions live on the project's tabs, so nobody re-pastes background into a fresh composer.
Projects overviewProjects
What are Projects in Tale?
Projects are shared workspaces that bundle the chats, files, instructions, and task board for one piece of work — so context follows the work and agents pick tasks up where your team leaves them.
How projects run work
Assign a task to an agent, resume the project chat with its context, ground replies in project files, and keep outbound steps behind review.
01 Tasks
Assign a card, an agent takes it
Assigning a board task to an agent starts the task-ops loop — execution, checks, and escalation run on workflows your organization owns and can tune.
02 Chats
Every chat starts with the context
Project instructions and files ride along in every thread, so a new chat picks up the relaunch where the last one stopped.
03 Knowledge
Files that stay inside the project
The Knowledge tab keeps the project's folder tree indexed for retrieval — cited in project chats, invisible outside the project.
04 Review
Nothing ships without a decision
When a task would publish or send, the approval card lands with the project's owner — and the decision stays in the audit trail.
One workspace per piece of work
A project keeps everything a customer, a launch, or an investigation needs in one place — and puts agents to work inside it.
02
A board agents work from
Assign a task card to an agent and the task-ops pack runs it — triage, execution, review, and escalation included.
Task automation03
A backlog with human triage
Automations propose work; a teammate starts what is worth doing and closes what is not. Nothing runs unvetted.
Project backlog04
Files scoped to the project
The Knowledge tab holds the project's folder tree — indexed for retrieval inside the project, invisible outside it.
Manage files05
The right agents on call
Curate which agents and models members see in the project, so the recommended specialist is one click away.
Agents and models
Projects FAQ
A shared workspace that bundles chats, files, instructions, tasks, and discussions around one piece of work — a customer, a launch, an investigation — so the context stays with the work.
Assigning a board task to an agent starts the task-ops loop: the agent executes, a human review gate checks the result, and budgets, concurrency limits, and a kill switch keep runs inside guardrails.
Only the project's members. Chats, files, and threads stay scoped to the workspace they live in — support escalations stay out of engineering.
A chat answers one question and moves on. A project carries ongoing work: shared history, a task board, instructions that apply to every chat, and files agents can cite.
See Tale on your stack
Book a guided demo or talk to the team about self-hosted deployment, pricing, and hardware.