> ## Documentation Index
> Fetch the complete documentation index at: https://superthread.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Notes and templates

> Read and update saved note templates, revise enhanced notes, and check enhancement status with the CLI.

[Log in and select your workspace](/docs/cli/index#getting-started) before running these commands. Use `--output json` to inspect full results. Note IDs must be UUIDs; template IDs must be exact saved IDs from `st notes templates list`, not template titles or URLs.

## Note templates

List accessible templates and read their instructions and sections:

```bash theme={null}
st notes templates list --output json
st notes templates get <template-id> --output json
```

Update a template you own:

```bash theme={null}
st notes templates update <template-id> \
  --title "Weekly team meeting" \
  --context "Focus on decisions, commitments, and unresolved risks." \
  --sections-file sections.json
```

`sections.json` contains the entire replacement list, in heading order:

```json theme={null}
[
  {"title": "Decisions", "description": "Record decisions and their reasoning."},
  {"title": "Action items", "description": "Include an owner and deadline when stated."},
  {"title": "Open questions", "description": "List unresolved questions and risks."}
]
```

Omit a flag to preserve that field. `--context ""` clears instructions, and a sections file containing `[]` clears all sections. Read the existing template before replacing its section list. Only the owner can edit; shared and built-in templates you do not own are read-only.

Template changes affect later enhancements. Existing enhanced notes change only when you explicitly re-enhance them. Template create and delete commands are not part of this command group. See [note templates](/docs/help/note-templates) for the existing settings controls.

## Enhance or revise a note

Read the saved note first:

```bash theme={null}
st notes get <note-id> --output json
```

Use its `revision` and inspect `ai_notes`. The current enhanced entry matches `last_note_template_id`.

Revise that saved enhanced content with instructions:

```bash theme={null}
st notes enhance <note-id> \
  --instructions "Make this shorter and group action items by owner." \
  --expected-revision <revision>
```

To revise a specific saved enhanced entry, add `--enhanced-note <enhanced-note-id>`. Instruction-only revision requires an existing non-empty enhanced entry.

Regenerate from the original user notes and transcript with a different template:

```bash theme={null}
st notes enhance <note-id> \
  --template <template-id> \
  --instructions "Keep all decisions and include owners for action items." \
  --expected-revision <revision> \
  --output json
```

`--instructions` is optional when `--template` is present. Use `--enhanced-note` for instruction-only revision, or `--template` for re-enhancement. Neither changes the original notes, transcript, or saved template.

| Flag | Meaning |
| - | - |
| `--instructions` | Instructions for revision or additional instructions when using a template |
| `--template` | Exact saved template ID for re-enhancement |
| `--enhanced-note` | Specific saved enhanced entry for instruction-only revision |
| `--expected-revision` | Whole-note revision from the latest `st notes get`; stale values fail |
| `--operation` | UUID to reuse for an identical retry |

When `--expected-revision` or `--operation` is omitted, the operation adapter supplies the current revision or a new UUID. A final concurrent edit still prevents the enhancement from overwriting newer content.

## Check enhancement status

```bash theme={null}
st notes enhancement <note-id> --output json
st notes enhancement <note-id> --operation <operation-id> --output json
```

Without `--operation`, the command reads the latest operation. Status is `idle`, `running`, `completed`, or `failed`. `running` content is a preview; only `completed` with `ai_note` confirms a durable save. A running response includes an operation ID you can check with this command, even after disconnecting.

Failed enhancements return an error and do not save their preview. A stale revision, conflicting retry input, or another running operation also fails. Read the latest note before retrying a conflict. Reuse `--operation` only for an identical request; use a new UUID for a new request.

Only the note owner can start or observe an enhancement. Custom agents given read access to a note cannot enhance it. See the [enhancement API](/docs/api-docs/notes/enhance-a-note) and [MCP operations](/docs/help/mcp#note-enhancement-operations).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.