Skip to main content

Tag work with labels

Labels add a second, flexible layer of organization. A task has one primary category, but it can carry multiple labels for initiatives, urgency, waiting states, or another property that cuts across category boundaries.

All screenshots
Usage counts reveal which labels are active in the workspace; the lock marks a private label.
ScreenshotMobile view
Label settings containing Awaiting Mission Control, Habitat critical, Project Waddle, and Sardine market sensitive with task usage counts

The Intergalactic Penguin Logistics workspace uses labels deliberately:

  • Project Waddle connects launch work across Penguin Operations, Mission Control, and Fish Diplomacy.
  • Habitat critical identifies work that must finish before the expedition enters the orbital habitat.
  • Awaiting Mission Control records a real blocking state.
  • Sardine market sensitive keeps private negotiation work identifiable.

Create and edit a label​

  1. Open Settings → Labels.
  2. Select Create label.
  3. Add a concise name and an optional description.
  4. Choose a color that remains distinguishable beside other labels.
  5. Decide whether the label is private and which categories may use it.
  6. Save.
All screenshots
ScreenshotMobile view
Project Waddle label editor showing its launch-critical description, blue color, privacy option, and three applicable categories

Descriptions are worth writing when a label could be interpreted in more than one way. They provide the operational meaning without forcing that explanation into every task title.

Applicable categories constrain where the label can be selected. Project Waddle is available in the three parts of the expedition involved in launch, while a specialist label can remain limited to one category. This keeps pickers relevant instead of presenting every label everywhere.

Apply labels to tasks​

Open a task and use its label control to add or remove labels. Labels work alongside task status, priority, and category filters, so you can ask focused questions such as “show open P1 habitat-critical work” without inventing a new category for that temporary view.

Let a task agent suggest labels​

When a configured task agent has enough task context, it can suggest fitting labels alongside other task changes. Lotti only makes active labels available when they are valid for the task's category, and it rejects deleted, out-of-scope, duplicate, or low-confidence suggestions. The agent never gets a free-form way to create arbitrary tags from a prompt.

Review an agent-originated label in the task's proposed-changes area just as you would a checklist, date, or status change. Confirm it when the label improves future filtering; dismiss it when it does not. This keeps the task's visible organization under your control rather than treating a model guess as source truth.

Removing a label from a task is treated as an intentional rejection when automatic label suggestions are enabled. Lotti records that choice so the same suggestion is not immediately re-applied without a new reason.

Keep labels useful​

  • Prefer labels that change a decision, filter, or review.
  • Reuse one stable label instead of creating spelling variants.
  • Check the usage counts before deleting or consolidating labels.
  • Use privacy when the label name itself reveals sensitive context.
  • Retire labels that no longer describe live work.

If something is the primary, durable home of the work, make it a category instead.