Write work that can be handed over
Title the outcome. Put scope, constraints, and acceptance criteria in the description. Status, priority, dates, type, and custom fields travel with the Task.
HiFoxTasks
Work of people and Agentsis all Tasks
A Task is the complete record of one piece of work: which Space owns it, which Project it sits in, who it is assigned to. Responsibility and execution are written in the same place.
How it works
Tasks thread product development context together
Private sessions lose context. A Task keeps the goal, the people responsible, the Agent that executed, and the comments that followed on one record.
Assign responsibility and execution separately
People carry responsibility, an Agent or Crew carries execution. Both are set in the Assignee field.
Keep dialogue on the Task
Comments are the discussion record. Activity logs status changes. An Agent trace opens from the comment that produced it.
Task Workflow
The Task is the core node of all work
A Task is not a scratch note. Assignment, comments, Workflow, Projects, and Agent runs all meet here.
01Task
The whole record on one item
Title, description, type, status, priority, dates, assignees, Project, labels, and custom fields, plus comments and history.
- Task types are defined by the Space and shared across it
- Attach a Project, or leave it unattached
- Execution state and result stay attached to the item
02Assignees
People own it. Agents execute.
A Task can have several responsible people. When something should run, an Agent or Crew takes the execution slot.
- One assignee control across the product
- The responsible person stays on the Task while an Agent runs
- Crew assignment coordinates several Agents on one Task
03Types
Each type binds its own fields and Workflow
A Bug, a Feature, and a Chore do not need the same form. Each task type binds its own fields and a bounded set of statuses.
- Exactly one default type per Space
- Statuses are selectable only within the type's Workflow
- Process differences live in the type; labels stay lightweight
04Conversation
Talk to the Agent on the Task, then start the run
Stay on the Task and work with an Agent in a comment. Reply, trace, and result all stay on that record.
- Agent dialogue happens in Task Conversation, not a private chat
- An eligible comment starts or continues a run
- The Agent's reply and run record stay on the Task
05Project
Group related Tasks around one outcome
A Project is the larger goal. People, Agents, comments, and runs stay on the Tasks; the Project gives them one outcome, owner, and progress.
- A Task takes at most one Project, and always belongs to one Space
- A Project can aggregate work from several Spaces
- Ownership and status stay on the Tasks, with no second tracker
06Inbox
Task changes reach people as they happen
Inbox is a personal activity queue grouped by Task. Opening a row opens that Task.
- Primary, Other, Later, and Cleared separate attention from the board
- Snoozing or clearing a row leaves the Task unchanged
- Triage notifications also arrive in the responsible person's Inbox
The Task system
The primitives a work item actually needs
A field, a comment, or a run that cannot attach to the Task is not part of the work system yet.
Task
The complete record of one piece of work: goal, type, status, assignees, execution, and history.
Assignee
People for responsibility, Agent or Crew for execution. One field for every handler type.
Task type & Workflow
Space-owned classification bound to its own fields and statuses.
Conversation
On-task dialogue with the Agent. Eligible comments start or continue a run.
Project
Optional grouping that puts related Tasks under one outcome and owner.
Inbox
A personal queue of Task activity. Snoozing or clearing it leaves the Task unchanged.
Connected features
A Task connects the whole system
Plan, Triage, Agents, and Automations all write back to the same Task.
Quality of life, built in
A Task that holds up to review
Discussion and execution attach to the Task, so the work stays inspectable and reviewable.
On one Task: people are the assignees, an Agent or Crew executes
Space-owned task types, each with its own Workflow
Start an Agent run from a comment on the Task
Projects that group related Tasks under one outcome
Inbox grouped by Task, with snooze and clear
Follow a Task without becoming its assignee
Every Agent run lands on a Task
Write the outcome, assign people and an Agent, and keep the discussion on the record.