# Task Editor

The Task Editor is where you view and change a task's structured fields without editing Markdown by hand. It works the same for inline and file tasks, because both are the same kind of task record underneath.

> **MEDIA-DOCS-021-1:** The Task Editor open on a task, showing its fields and, for a file task, the Markdown body.

![MEDIA-DOCS-021-1 - Task Editor fields and Markdown body](/assets/docs/media/MEDIA-DOCS-021-1.png?v=06c5691a3bb9)

## How to open it

- On an existing inline task, run **Create or edit inline task**.
- On a file task or a note with task fields, run **Edit or convert to file task**.
- From any Operon surface, open a task's contextual menu and choose **Open editor**. See [Contextual menu actions](/docs/docs-042-contextual-menu-actions/).

The same command that creates an inline task also edits one, so the editor is never more than a keystroke away from the task.

> **MEDIA-DOCS-021-2:** Opening the Task Editor from a task's contextual menu with Open editor.

![MEDIA-DOCS-021-2 - Open Task Editor from contextual menu](/assets/docs/media/MEDIA-DOCS-021-2.png?v=85fa514d14ef)

## What you can change

The Task Editor exposes the canonical fields as proper controls:

- Status and priority.
- Dates: due, scheduled, started, and timed start/end blocks.
- Parent task and dependencies.
- Recurrence. See [Recurring tasks](/docs/docs-033-recurring-tasks/).
- Pinning. See [Pinned Task Dock](/docs/docs-032-pinned-task-dock/).
- Time tracking, including session history. See [Time tracking](/docs/docs-034-time-tracking/).
- Icon, color, and a short note.

For a file task, the editor can also show the Markdown body alongside the fields, so you edit the work and its metadata together. For an inline task, it can reveal the source note when you need the surrounding context. It can also **Show checkboxes** for the task's [plain checklist](/docs/docs-017-plain-checkbox-lists/).

> **MEDIA-DOCS-021-3:** The Task Editor on a file task, the fields beside the Markdown body.

![MEDIA-DOCS-021-3 - Task Editor file task layout](/assets/docs/media/MEDIA-DOCS-021-3.png?v=221c632be787)

## Why edit here instead of in Markdown

You can always edit the raw `{{key:: value}}` text, and Operon will read it. But the Task Editor is safer: it writes fields in the right format, keeps `operonId` intact, and updates rollups and links for you. Hand-editing is best for quick text tweaks; the editor is best for anything structural. See [Task identity and operonId](/docs/docs-015-task-identity-and-operonid/).

## FAQ

**Is the editor different for inline and file tasks?** The fields are the same. File tasks additionally show the note body; inline tasks can jump to their source line.

**Will editing here change my Markdown?** Yes. The Task Editor writes back to the task's Markdown, inline line or file frontmatter, so your notes stay the source of truth.

## Settings

Operon settings for this live in **Settings → Operon → Interface → Task Editor**, which configures the Task Editor layout and which fields it shows.

## Related

- [Operon Docs MOC](/docs/docs-001-operon-docs-moc/)
- [Task Creator](/docs/docs-020-task-creator/)
- [Inline task syntax](/docs/docs-012-inline-task-syntax/)