---
title: Quick add syntax
summary: Every word quick add understands: dates, times, projects, labels, priorities, estimates, nine languages and voice capture.
audience: user
section: Reference
specs: [natural-language-capture, voice-capture, manual-ordering, task-list-presentation]
screens: [settings/quick-add, settings/voice]
order: 10
---
# Quick add syntax
Type one line in the quick-add box (press `q` in any task view) and OpenTodo picks out the due date and time, project, labels, priority and estimate:
```
Meeting with Sarah next Wed at 3pm #work @call p1 +30m
```
creates **Meeting with Sarah**, due next Wednesday at 15:00, in project *Work*, with the label *call*, priority 1, estimated at 30 minutes.
Everything runs in your browser. The parser needs no network, sends nothing anywhere, and gives the same result on every device for the same line, date, languages and projects. The created task stores the resolved date, so other devices never parse the line again.
## Preview chips
As you type, each thing OpenTodo recognises shows up as a chip under the input and is tinted in the line itself (underlined in high contrast), and the title preview (`→ Meeting with Sarah`) shows what will be saved. Nothing is hidden: if there is no chip, the text stays in the title. The same line works in the list, the phone's add sheet and the [command bar](#in-the-command-bar)'s Add mode, and gives the same task everywhere. The command bar lists what it understood as one row per field, with the token that sets each one; the phone's sheet shows plain chips, and buttons under them (date, priority, label, estimate, project) start a token for you.
| To… | Do this |
| --- | --- |
| Keep a word literally ("may" is not May 1st) | Click the `×` on its chip, **or** press Backspace at the end of the line: the first press highlights the last chip, the second dismisses it. The text itself is not changed. |
| Never parse some text | Put it in double quotes: `Watch "Next Friday" tomorrow` → title *Watch Next Friday*, due tomorrow. The quotes are removed from the title. |
| Turn parsing off on this device | Settings → Capture → Quick add → **Parse natural language**. Quick add then saves the line exactly as typed. |
A dismissed chip stays dismissed while you keep typing; it comes back only if you edit that word. Backspace only highlights a chip when that chip's text ends the line; otherwise Backspace deletes text as usual.
## Long titles and notes
A long title wraps onto more lines as you type, so you can read it back and put the caret anywhere; past five lines the box scrolls. The title is still one line of text: Enter adds the task.
To write the task's [notes](notes-and-subtasks.md#write-notes) while you add it, press Shift+Enter in the box (on a phone, tap the notes button in the add sheet's tool row). A **Notes** field opens under the title. Whatever you write there is saved as the task's notes, exactly as typed: a link stays a link, and nothing in the notes is read as a date or a project. Enter adds the task from the notes too, Shift+Enter starts a new line in them, and Backspace in empty notes closes them. The command bar keeps Shift+Enter for adding and opening the task, and the [share screen](capture.md) has its own Description field.
## In the command bar
In the [command bar](search.md#four-modes)'s Add mode (q on screens without a quick add, or + in the box), what quick add understood is a row per field: **When**, **Project**, **Label**, **Priority** and **Estimate**, plus **Deadline**, **Repeats**, **Reminder** and **Time spent** when you type them. Each row shows its value, or how to set it (`#`, `@`, `p1`, `+30m`). Click a row, or move to it with ↓ and press Tab: a set field's words are selected so you can type over them, and an empty field gets its token at the end of the line. The `×` on a row keeps its words as text. Enter adds the task and keeps the box open for the next one; Shift+Enter adds it and opens it.
On a phone, the add sheet shows plain chips for what it understood, and buttons under them (date, priority, label, estimate, project) that start a token for you, then a notes button that opens the notes field. The sheet stays open after you add a task, with the box empty and the keyboard up, so you can type the next one straight away; tap outside it or swipe it down when you are done.
## Tokens (any language)
| Token | Meaning | Examples |
| --- | --- | --- |
| `#name` | Project, including sub-projects. Case-insensitive; spaces, `-` and `_` are ignored. An exact name wins, otherwise a unique prefix; `#Home/Docs` picks *Docs* under *Home*. If nothing matches, or a prefix fits several projects, the token stays in the title and a grey chip says so. | `#work`, `#trav` (Travel), `#sideproject` (Side Project), `#Home/Docs` |
| `@name` | Label, matched ignoring case. A name with no label yet creates one when you press Enter; its chip says *New label* until then. Use as many as you like. | `@call`, `@waiting-for` |
| `p1`–`p4` | Priority, 1 highest, 4 [no priority](priorities.md#no-priority), the default. Typing `p` after a space lists the four levels with [your names for them](priorities.md); only the number is read. | `p1`, `P3` |
| `+duration` | Estimate in minutes, from 1 minute to 7 days (10080 minutes). Shown on the task row. | `+30`, `+30m`, `+45min`, `+2h`, `+1h30`, `+1.5h` |
| `spent/estimate` | Time already spent and an estimate (see [Time spent](#time-spent)). | `30m/2h`, `1h/1h30`, `45min/2h` |
The same works when you edit a title in the task panel: type ` tomorrow p1` after the title and press Enter, and the date and priority are set with the title left as it was; only what you typed in this edit is read, and **Undo** takes it back.
Type `#` or `@` and a list of your projects or labels opens under the field, narrowed as you type; arrows move, Enter or Tab picks, Esc closes it. When nothing has that name, the last entry creates it.
Without the `+`, `45min` and `2h` also work, except that `2h` is left alone when French, Spanish or Portuguese is active, because those languages write times as `15h`.
### Time spent
`Draft the offer 30m/2h` creates the task with a two-hour estimate and one closed [time entry](time-tracking.md) of 30 minutes ending now, in the same step; the preview shows a **Spent 30 min** chip beside the estimate, and the row reads `30m / 2h`. Both parts need a unit (`h`, `m`, `min`), so `Pay rent 30/12` stays a date, and `Réunion 15h` with French active is still a meeting at 15:00. `+30m` remains an estimate only. Units are not translated: the token works the same in all seven languages. Backspace on the chip keeps the text in the title, like every token.
## Dates and times
| Phrase | Resolves to |
| --- | --- |
| `today`, `tonight`, `tomorrow`, `day after tomorrow` | that day |
| `Monday` … `Sunday`, `mon`, `wed.` | the next one **after** today (on a Friday, `fri` means next Friday) |
| `this sat` | same as the bare weekday |
| `next Monday` | same as the bare weekday, unless that day is still in the current week; then the one a week later. Weeks start on your first day of the week (Monday unless you change it). On Friday 9 Oct, `next Wed` is 14 Oct and `next Sat` is 17 Oct (not tomorrow). |
| `second Monday`, `2nd monday`, `last Friday`, `Bins last Wednesday of the month` | that weekday of this month, or of next month once it has passed (`first` … `fourth` and `last`; on Friday 9 Oct, `second Monday` is 12 Oct and `first Monday` is 2 Nov). There is no fifth: `5th Friday` stays as typed. |
| `the 3rd Friday of November`, `first Friday of October 2028` | that weekday of that month, this year or next (today counts); with a year, that year |
| `in 3 days`, `in 2 weeks`, `in a month` | today plus that much (months keep the day, clamped to the month's end) |
| `next week`, `next month` | the first day of next week (Monday unless you start your week on Sunday or Saturday); the 1st of next month |
| `3 Feb`, `Feb 3`, `3rd of February`, `December 25th 2027` | that date; without a year, the next time it comes round (today counts) |
| `May`, `December` (full name alone) | the 1st of that month, but only when the line has no other date: a later date wins (`Collect the invoices from September and send them next Monday at 10am` is due next Monday at 10:00, and *September* stays in the title). Right after `from`, `since`, `of` or `for` (`seit`, `von`, `ab`, `für`; `depuis`, `de`, `du`; `da`, `di`, `del`; `desde`, `de`, `del`; `desde`, `de`, `do`) a month name alone is always text. Abbreviations (`mar`, `jan`) need a day number next to them. |
| `12/11`, `12-11`, `12/11/2027`, `2026-11-03` | numeric dates; see day/month order below |
| `at 3pm`, `3:30 pm`, `16:30`, `at 9`, `noon`, `midnight` | that time today, unless a date is also given. A time on its own always means today, even if it has passed. Without `am`/`pm`, hours are 24-hour (`at 3` is 03:00). |
| `in 3 hours` | that clock time, rolling to tomorrow past midnight |
Words like `on` and `due` in front of a date are removed with it (`Pay bill on Friday` → *Pay bill*); `by` in front of a date sets the deadline instead (see **Deadlines** below). `last Friday` always means the last Friday of the month, never the one that has passed: in `Review notes from last Friday`, dismiss the chip (or quote the words) to keep them in the title. Bare numbers are never times (`Buy 3 apples` stays as typed): write `at 3`, `3pm` or `15:00`.
**Deadlines.** Put `deadline` right before a date to set the task's [deadline](tasks-and-projects.md#deadlines) instead of its due date: `Send report deadline friday` → *Send report*, no due date, deadline Friday, shown as its own chip with an hourglass. Combine both: `Send report tomorrow deadline friday` is planned for tomorrow and due by Friday. A deadline has no time, so a time right after it stays in the title. Without a date after it the word is just text (`Review deadline policy`).
`by` before a date sets the deadline too: `Install winter tires by March 31` → *Install winter tires*, no due date, deadline 31 March, and `Pay tax tomorrow by friday` is planned for tomorrow with a deadline on Friday. `on` and `due` still set the due date. `by` before a time is a due time (`Call back by 5pm` → today at 17:00), and so is `by` before a date with a time (`Pay tax by friday 5pm` is due Friday at 17:00), since a deadline has no time. A [repeating](recurrence.md) line keeps its rule (`Water plants every monday by friday` repeats every Monday, with a deadline on Friday). German, Italian, Portuguese and Dutch have a `by` word as well; French and Spanish `pour` and `para` mean "for" and still set the due date. Each language has its own words:
| Language | Deadline word | `by` word |
| --- | --- | --- |
| English | `deadline` | `by` |
| German | `Frist`, `Deadline` | `bis` |
| French | `échéance`, `deadline` | |
| Italian | `scadenza` | `entro` |
| Spanish | `fecha límite`, `plazo` | |
| Portuguese | `prazo` | `até` |
| Dutch | `deadline` | `uiterlijk` |
| Polish | `termin`, `deadline` | `do` |
**Someday and tonight.** `someday` parks the task in [Someday](tasks-and-projects.md#when-a-task-starts): `Learn to sail someday @hobby` → *Learn to sail*, parked. If the line also has a date, the word stays in the title (`Plan someday trip friday` is due Friday). `tonight` and `this evening` make the task due today and mark it for **This Evening**, a group below the day's tasks in Today; a time still sets the due time (`Call Ana tonight at 8pm`). Before this, `tonight` only meant today; the date is the same, the task now also shows the moon. Each gets its own chip.
| Language | Someday | Tonight |
| --- | --- | --- |
| English | `someday`, `some day` | `tonight`, `this evening` |
| German | `irgendwann` | `heute Abend` |
| French | `un jour` | `ce soir` |
| Italian | `prima o poi` | `stasera` |
| Spanish | `algún día` | `esta noche` |
| Portuguese | `algum dia` | `hoje à noite` |
| Dutch | `ooit` | `vanavond` |
| Polish | `kiedyś` | `dziś wieczorem` |
**Energy.** With **Energy levels** on ([Set up](method/set-up.md#energy-levels)), `~deep`, `~medium` and `~low`, or any start of them (`~d`, `~me`, `~L`), set the task's energy, in every language and in any letter case: `Draft the strategy #Work ~deep +2h` → *Draft the strategy*, in Work, 2 hours, Deep. The chip reads "Deep energy"; typing `~` suggests the three, and on a phone the lightning tool under the line starts one. The last one on the line wins. `~` followed by anything else stays in the title (`Dinner for ~6 people`), and with Energy levels off the token is not read.
**Time sectors.** With **Time sectors** on (Settings → Account → Profile → How you work), a phrase for a period plans the task for that week, month or quarter instead of a date: `Draft the budget this week #Work` → *Draft the budget*, in Work, This week. `next week` and `next month` alone keep their date meaning; say `sometime next week` for the sector. A line that also has a date takes the date and keeps the phrase in the title (`Review this week plan friday` is due Friday), and with the switch off no phrase is read. A deadline stays beside the sector. See [Time sectors](time-sectors.md).
| Language | This week | Next week | This month | Next month | This quarter | Next quarter |
| --- | --- | --- | --- | --- | --- | --- |
| English | `this week` | `sometime next week` | `this month` | `sometime next month` | `this quarter` | `next quarter` |
| German | `diese Woche` | `irgendwann nächste Woche` | `diesen Monat` | `irgendwann nächsten Monat` | `dieses Quartal` | `nächstes Quartal` |
| French | `cette semaine` | `dans le courant de la semaine prochaine` | `ce mois-ci` | `dans le courant du mois prochain` | `ce trimestre` | `le trimestre prochain` |
| Italian | `questa settimana` | `nel corso della prossima settimana` | `questo mese` | `nel corso del prossimo mese` | `questo trimestre` | `il prossimo trimestre` |
| Spanish | `esta semana` | `en algún momento de la próxima semana` | `este mes` | `en algún momento del próximo mes` | `este trimestre` | `el próximo trimestre` |
| Portuguese | `esta semana` | `em algum momento da próxima semana` | `este mês` | `em algum momento do próximo mês` | `este trimestre` | `no próximo trimestre` |
| Dutch | `deze week` | `ergens volgende week` | `deze maand` | `ergens volgende maand` | `dit kwartaal` | `volgend kwartaal` |
| Polish | `w tym tygodniu` | `kiedyś w przyszłym tygodniu` | `w tym miesiącu` | `kiedyś w przyszłym miesiącu` | `w tym kwartale` | `w przyszłym kwartale` |
Every "this" phrase also has its "sometime" form (`sometime this month`, `irgendwann diese Woche`, …).
**Morning and afternoon.** With [day parts](day-parts.md) on, `this morning` and `this afternoon` make the task due today with that part, and a part word right after a date phrase gives that date the part: `Stretch tomorrow morning` → *Stretch*, due tomorrow, Morning; `Dinner fri evening` → due Friday, This Evening. A part word anywhere else stays in the title (`Morning run tomorrow` keeps *Morning run*), and with day parts off none of these are read. Each gets its own chip.
| Language | This morning, this afternoon | After a date |
| --- | --- | --- |
| English | `this morning`, `this afternoon` | `morning`, `afternoon`, `evening` |
| German | `heute Morgen`, `heute früh`, `heute Vormittag`, `heute Nachmittag` | `früh`, `Vormittag`, `Nachmittag`, `Abend` |
| French | `ce matin`, `cet après-midi` | `matin`, `après-midi`, `soir` |
| Italian | `stamattina`, `stamani`, `questa mattina`, `oggi pomeriggio`, `questo pomeriggio` | `mattina`, `pomeriggio`, `sera` |
| Spanish | `esta mañana`, `esta tarde` | `por la mañana`, `por la tarde`, `por la noche` |
| Portuguese | `esta manhã`, `hoje de manhã`, `esta tarde`, `hoje à tarde` | `de manhã`, `à tarde`, `à noite` |
| Dutch | `vanochtend`, `vanmorgen`, `vanmiddag` | `ochtend`, `middag`, `avond`, `'s ochtends`, `'s middags`, `'s avonds` |
| Polish | `dziś rano`, `dziś po południu` | `rano`, `po południu`, `wieczorem` |
When a line has two dates, the first one counts and the second stays in the title. The same goes for a second time, deadline, project, priority or estimate.
**Day/month order.** Numeric dates follow your date format in **Settings → Language and region → Date and time**: day-month reads `12/11` as 12 November, month-day as 11 December. With the date format on System or ISO, they follow your language instead: 11 December when your first language is US English (`en`, `en-US`) and 12 November for every other language, including English outside the US. The date format syncs, so every device reads a line the same way. If one reading is impossible (`25/12`), the other is used. Dotted dates (`12.11.`) are always day.month and only used when the order is day/month.
**Week start.** `next week` and `next ` use **Week starts on** in **Settings → Language and region → Date and time**, so they give the same result on all your devices.
## Languages
Vocabulary is bundled for **English, German, French, Italian, Spanish, Portuguese, Dutch, Turkish and Polish**. The active languages are the [interface language](language.md) when you picked one, then your browser's preferred languages that are bundled, plus English, which is always on; all of them are matched at the same time. With the interface language on **System** the order is your browser's, as before. Settings → Capture → Quick add can override the list on this device. Where two languages read a word differently, the longer phrase wins (Spanish `mar` alone is Tuesday; `mar 3` is March 3rd).
| | Examples |
| --- | --- |
| German | `heute`, `morgen`, `übermorgen`, `am Freitag`, `Mi.`, `nächsten Mittwoch um 15 Uhr`, `in 3 Tagen`, `nächste Woche`, `3. Februar`, `12.11.`, `14:30 Uhr` |
| French | `aujourd'hui`, `demain à 15h`, `après-demain`, `mardi prochain`, `dans 2 semaines`, `semaine prochaine`, `3 février`, `15h30`, `à 9 heures`, `midi` |
| Italian | `oggi`, `domani alle 15`, `dopodomani`, `lunedì prossimo`, `prossimo sabato`, `tra 3 giorni`, `fra una settimana`, `il 3 febbraio`, `mezzogiorno` |
| Spanish | `hoy`, `mañana a las 15:00`, `pasado mañana`, `el próximo lunes`, `martes que viene`, `en 3 días`, `dentro de 2 semanas`, `3 de febrero` |
| Portuguese | `hoje`, `amanhã às 15h`, `depois de amanhã`, `próxima segunda`, `sábado que vem`, `daqui a 3 dias`, `em 2 semanas`, `3 de fevereiro` |
| Dutch | `vandaag`, `morgen om 15 uur`, `overmorgen`, `op vrijdag`, `volgende woensdag`, `komende vrijdag`, `over 3 dagen`, `volgende week`, `3 maart`, `ma 1 mrt`, `om 15:30`, `om half 4`, `om 8 uur 's avonds` |
| Polish | `dziś`, `jutro o 9:30`, `pojutrze`, `w piątek`, `w środę o 15:00`, `w przyszły poniedziałek`, `za 3 dni`, `za 2 tygodnie`, `12 listopada`, `pon. 2 lis`, `o 17:00` |
Ordinal weekdays work in every language, with the ordinal words or a number with its suffix (`2nd`, `2.`, `2º`, `2e`): `am zweiten Montag`, `dritten Freitag im November`, `le 2e lundi de novembre`, `secondo lunedì`, `tercer viernes de noviembre`, `segunda segunda-feira`, `última sexta`. In Portuguese, `segunda` and `quarta` count as *second* and *fourth* only right before a weekday; alone they are Monday and Wednesday.
Accents are optional (`manana`, `nachsten`, `fevrier` work too). Two-letter German abbreviations need their dot (`Mi.`, `Do.`) so ordinary words like *do* and *so* are not mistaken for weekdays. Two-letter Dutch abbreviations (`ma`, `di`, `wo`, `do`, `vr`, `za`, `zo`) count only next to a date: after `op`, `elke` or `volgende`, or before a day and month or a time (`op ma`, `ma 1 mrt`, `ma om 9 uur`), so `Bel ma` stays *Bel ma*. A weekday right before a full date names that date in every language (`Monday, March 3`). Polish weekdays and months are read in the forms people type: `w środę`, `do piątku` (a deadline), `pierwszego poniedziałku miesiąca`, `12 listopada`. In Dutch, `half 4` is half past three: `om half 4` is 03:30 and `om half 4 's middags` 15:30; `'s ochtends`, `'s middags`, `'s avonds` and `'s nachts` after a time work like *am* and *pm* (`om 8 uur 's avonds` is 20:00).
## Views and defaults
Quick add still takes the view's context for anything the line does not set: today in Today, tomorrow in Upcoming, the current project in a project view, the current label in a label view. Anything the line does set wins, so `Plan trip next Monday #travel` typed in Today goes to *Travel* on Monday. Labels add up instead: `@call` typed in the *errand* label view gives the task both labels, so it stays in the view you added it from. A task added in **Someday** is parked, unless the line sets a date (`Read Proust tomorrow` is due tomorrow instead).
## Where new tasks go
Settings → Capture → Quick add → **Add new tasks** decides where a task added from a list lands: **At the bottom of the list** (the default) or **At the top of the list**. The choice is kept for your account, so all your devices follow it, and it works offline like any change.
It applies to the quick add of a project and the Inbox, to a section's **+** row, to a board column's add row, and to the command bar and the phone's add sheet. With *top*, the task is first in its project, section or column, right under the quick add, so you see it arrive. Lists ordered by date, priority or anything other than manual order keep their order: there the setting only decides which of two equal tasks comes first, so Today and Upcoming look the same either way.
Some adds keep their own place: a subtask goes below its siblings, a task added with o goes right after the selected task, and duplicates, templates, imports and tasks created through the API, the [CLI](cli.md) or [MCP](mcp.md) are appended (see [Task fields](api.md#task-fields)).
When a new task lands out of sight, at the end of a long list, a short note says where it went, such as *Added to the bottom of Inbox*, with **Show**, which scrolls to the task and selects it.
From 768 px wide, the quick add stays under the page's title while the list scrolls under it, so you can add a task wherever you are in a long list without scrolling back up. On a phone the floating **+** button does the same, and the quick add scrolls with the list.
## Paste a list
Copy a list from a chat, a note or meeting minutes and paste it into an empty quick add. When the text has two or more lines, OpenTodo asks first: *Add 7 tasks, one per line?*, with the first five lines as they will be titled and how many more follow.
- **Add 7 tasks** (or Enter) creates one task per line, in the pasted order.
- **Paste as one line** puts the lines into the box joined by spaces, as before.
- Esc closes the question and pastes nothing.
Each line is cleaned first: spaces at either end and blank lines are dropped, and one list marker at the start is removed: `-`, `*`, `+`, `•`, `1.`, `1)`, `a)`, `[ ]`, `[x]`, `- [ ]`, `- [x]`, `☐` and `☑`. A ticked box does not complete the task; it starts open like the others.
With parsing on, each line is read like a line you typed, with the [view's defaults](#views-and-defaults) for what it does not set. Pasting
```
Call Anna tomorrow 10am
Send invoice #Work p1
```
into Today creates *Call Anna*, due tomorrow at 10:00, and *Send invoice*, due today in *Work* with priority 1. A line with only a date, such as `tomorrow`, keeps its text as the title.
All the tasks of one paste are saved together, offline too, and a note says *7 tasks added* with **Undo**, which removes them all in one step. In the Inbox, the note also counts the lines that went elsewhere because they set a date or a project. If one line cannot be saved (in an [encrypted account](e2ee.md), a title too long to encrypt), none of them is, and the question says why.
A paste into a box that already holds text goes in as text: OpenTodo assumes you are in the middle of a line. Up to 100 lines are added at once; for a longer list the question says so and offers [Import](import-export.md) and **Paste as one line**. Pasting works the same in a section's add row, the command bar's Add mode, the phone's add sheet, the [share screen](capture.md) and a calendar day's add dialog. To paste several subtasks, see [Break a task into subtasks](notes-and-subtasks.md#break-a-task-into-subtasks).
## Voice
Quick add can also be dictated. Voice capture is **off by default** and is switched on per device in **Settings → Capture → Voice capture**; it is not synced, so turning it on for your phone leaves your laptop as it is. Browsers without speech recognition (Firefox, for example) show the switch disabled with an explanation, and quick add has no microphone button there.
**Who recognises speech.** By default your browser does, and some browsers send the audio to their vendor. If the server owner connected a [speech service](self-hosting/speech-to-text.md), **Recognition** offers **This server's speech service** too. Each phrase is then recorded in the browser and sent once through your server to that service, which returns the text. Neither keeps the audio or the text. The statement you confirm names the service's host.
With voice capture on, press the microphone button in quick add or `Shift+V` anywhere outside a text field (plain `v` already toggles list and board in a project). Words appear in the box as they are recognised; when you stop talking, press the button again or press `Esc`, the final transcript is inserted at the caret and parsed exactly like typed text, chips included. **Nothing is saved until you press Enter**, so you can correct the line by hand first. To speak several tasks at once, a whole brain dump, use **Ramble into tasks** in the command palette instead: the [assistant](assistant-capture.md) turns it into a batch of tasks to review.
Spoken forms of the tokens are turned into their typed forms first, in the active quick-add languages (English is always on):
| Said | Becomes |
| --- | --- |
| "renew insurance hashtag home priority two" | `renew insurance #home p2` |
| "standup at nine thirty am" | `standup at 9:30am` |
| "call the dentist tomorrow at nine" | `call the dentist tomorrow at 9` |
| "label errands buy stamps" | `@errands buy stamps` |
| "phone mum at call" (an existing label *call*) | `phone mum @call` |
| "plan move project home office" (an existing project) | `plan move #homeoffice` |
| "write report for thirty minutes", "one hour and fifteen minutes" | `write report +30m`, `+75m` |
| "ping Ana in two hours" | `ping Ana in 2 hours` |
| "um neun Uhr dreißig", "alle nove", "a las diez", "à neuf heures", "às onze" | `um 9:30`, `alle 9`, `a las 10`, `à 9 heures`, `às 11` |
Trigger words per language: *hashtag* (all), *project / Projekt / projet / progetto / proyecto / projeto* (only before an existing project's name), *label / Etikett / étiquette / etichetta / etiqueta*, and *priority / Priorität / priorité / priorità / prioridad / prioridade* followed by one to four. Numbers are only converted next to a time, priority or duration cue, so "buy two apples" stays as it is.
The recognition language follows your first quick-add language, so the interface language when you picked one (with your browser's region, for example `en-GB`), and can be changed in Settings. If the browser cannot recognise that language, OpenTodo says so once and listens in the browser's default language.
If the microphone is blocked, a message explains how to allow it in the browser's site settings and the button stays there to retry. In the [Android app](android-app.md#voice-input) the phone asks the first time, and a refusal is changed in the app's settings. When nothing is said, listening just stops. When recognition is unavailable (for example offline, in a browser that needs its vendor's service), quick add says "Voice capture is unavailable right now" and typing works as usual. Text already in the box is never cleared.
### Privacy
Before voice capture can be switched on, Settings shows this statement and waits for you to confirm:
- Speech is recognised by your browser, not by OpenTodo.
- Depending on the browser, your audio may be sent to the browser vendor's speech service (for example Google for Chrome, Apple for Safari) and handled under their privacy policy.
- OpenTodo asks the browser to recognise speech on this device when it offers that choice.
- Your OpenTodo server never receives audio or transcripts. Only the task you save with Enter is stored and synced, like a typed one.
- The microphone is used only while you dictate; the browser asks for permission the first time.
OpenTodo's code never records, stores or sends audio: the Web Speech API hands it text. On-device recognition is requested whenever the browser reports it available for the language (Chromium's `processLocally`); OpenTodo never asks the browser to download a speech model. The browser asks for microphone permission on your first dictation, not when you switch the setting on.
## Repeat and remind
A rule and reminders can be typed in the same line. Each gets its own chip and is removed from the title.
| English | Deutsch | Français | Italiano | Español | Português | Nederlands | Polski |
| --- | --- | --- | --- | --- | --- | --- | --- |
| `every Monday` | `jeden Montag` | `tous les lundis` | `ogni lunedì` | `cada lunes` | `toda segunda-feira` | `elke maandag` | `co poniedziałek` |
| `every 3 days after completion` | `alle 3 Tage nach Erledigung` | `tous les 3 jours après achèvement` | `ogni 3 giorni dopo il completamento` | `cada 3 días después de completar` | `todo 3 dias após a conclusão` | `elke 3 dagen na voltooiing` | `co 3 dni po ukończeniu` |
| `daily`, `weekly`, `monthly`, `yearly` | `täglich`, `wöchentlich`, `monatlich`, `jährlich` | `quotidiennement`, `hebdomadairement`, `mensuellement`, `annuellement` | `quotidianamente`, `settimanalmente`, `mensilmente`, `annualmente` | `diariamente`, `semanalmente`, `mensualmente`, `anualmente` | `diariamente`, `semanalmente`, `mensalmente`, `anualmente` | `dagelijks`, `wekelijks`, `maandelijks`, `jaarlijks` | `codziennie`, `cotygodniowo`, `comiesięcznie`, `corocznie` |
| `every other Friday`, `every other week` | `jeden zweiten Freitag`, `jede zweite Woche`, `alle zwei Tage` | `un vendredi sur deux`, `une semaine sur deux`, `tous les deux jours` | `ogni due venerdì`, `ogni due settimane`, `a settimane alterne` | `cada dos viernes`, `cada dos semanas` | `a cada duas sextas`, `a cada duas semanas` | `om de vrijdag`, `om de week`, `tweewekelijks` | `co drugi piątek`, `co drugi tydzień` |
| `every 2 weeks on Saturday` | `alle 2 Wochen am Samstag` | `toutes les 2 semaines le samedi` | `ogni 2 settimane il sabato` | `cada 2 semanas los sábados` | `cada 2 semanas aos sábados` | `elke 2 weken op zaterdag` | `co 2 tygodnie w sobotę` |
| `and repeat every Monday`, `and then every Monday` | `und dann jeden Montag`, `wiederholen jeden Montag` | `et répéter tous les lundis`, `puis tous les lundis` | `e poi ogni lunedì`, `ripeti ogni lunedì` | `y repetir cada lunes`, `luego cada lunes` | `e repetir toda segunda-feira`, `depois toda segunda-feira` | `en dan elke maandag`, `herhaal elke maandag` | `i powtarzaj co poniedziałek` |
| `every day starting tomorrow`, `every Monday from 16 Nov` | `jeden Tag ab morgen` | `tous les jours à partir de demain` | `ogni giorno a partire da domani`, `da domani` | `cada día a partir de mañana`, `desde mañana` | `todo dia a partir de amanhã`, `desde amanhã` | `elke dag vanaf morgen` | `codziennie od jutra`, `co poniedziałek od 16 listopada` |
| `remind me 30 min before` | `erinnere mich 30 Minuten vorher` | `rappelle-moi 30 min avant` | `ricordamelo 30 minuti prima` | `recuérdame 30 minutos antes` | `lembre-me 30 minutos antes` | `herinner me 30 minuten van tevoren` | `przypomnij mi 30 minut wcześniej` |
| `remind me at 9` | `erinnere mich um 9 Uhr` | `rappelle-moi à 9h` | `ricordamelo alle 9` | `recuérdame a las 9` | `lembre-me às 9` | `herinner me om 9 uur` | `przypomnij mi o 9` |
Rules cover the whole [rule grammar](recurrence.md): weekday lists (`every mon, wed and fri`), `every weekday`, `every 15th`, `every 2nd Tuesday`, `every last Friday`, `every last day`, `every first weekday` (`jeden ersten Werktag`, `chaque premier jour ouvré`, `ogni primo giorno feriale`, `cada primer día laborable`, `todo primeiro dia útil`; in Dutch also `elke werkdag` and `op werkdagen` for every weekday, in Polish `co dzień roboczy`), with `after completion`, `until 31 Dec` or `for 10 times` at the end. The stored rule is always the English canonical form, whatever language you typed. A phrase the grammar cannot express, such as `every 3 hours`, stays in the title; only the first rule of a line counts. After a monthly rule, `of the month` is accepted and changes nothing (`every 2nd monday of the month`, `jeden zweiten Montag im Monat`, `tous les 2e lundis du mois`, `ogni secondo lunedì del mese`, `cada segundo lunes del mes`, `toda segunda segunda-feira do mês` are all `every 2nd monday`). A bare number before a weekday is a count, not an ordinal: `every 2 Mondays` (`alle 2 Montage`, `cada 2 lunes`) is not a rule and stays as typed, with no date.
**Every other.** `every other day`, `week`, `month` or `year` repeats every 2 of them. `every other Friday` is the same as typing `every 2 weeks on Friday`: the series stays on Fridays whatever date the task starts on. When the task is due on a Friday, the rule is stored as `every 2 weeks`, which means the same and which [older devices](recurrence.md#rules-older-devices-read) read; otherwise it is stored as `every 2 weeks on friday`. In German, `jeden zweiten Freitag` is every other Friday, while `jeden zweiten Freitag im Monat` stays the second Friday of each month; in the other languages `every second Friday` (`ogni secondo venerdì`, `cada segundo viernes`) is the second Friday of the month.
**First date.** Without a date in the line, the task is due on the rule's first occurrence from today, and the rule chip shows it (`every monday · Mon 12 Oct`). With a date (`Invoice every month 3 Nov at 10:00`) that date starts the series; a time becomes the series' time. The date counts even when it is not on the rule's weekday: `take the bins out today and repeat every other Saturday`, typed on a Wednesday, is due today with the rule `every 2 weeks on saturday`, and completing it moves it to Saturday, then every other Saturday after that; typed on a Saturday, it is due today with the rule `every 2 weeks`. A start phrase next to the rule (`starting today`, `starting tomorrow`, `starting 16 Nov`, `from Monday`, `ab heute`, `à partir de demain`, `a partir de mañana`, `a partire da domani`, `a partir de amanhã`) instead makes the task due on the rule's first date on or after it: `every other Saturday starting today`, typed on a Wednesday, is due this Saturday. The view's own default date never replaces the rule's date.
**Connectors.** `and repeat`, `repeat`, `repeating`, `and then`, `then` or `and` directly before a rule leave the title with it (`und dann`, `wiederholen`; `et répéter`, `puis`; `y repetir`, `luego`; `e poi`, `ripeti`; `e repetir`, `depois`). Without a rule after them they stay: `Repeat the test` is just a title, and so is `Work from home` or `Call mom starting tomorrow` without a rule next to the start word.
**Reminders.** `remind me` followed by an offset (`30 min before`, `1 hour after`, `2 days before`) or a moment (`at 9`, `tomorrow at 9`, `20 Oct at 9`). Several reminders per line are fine. A moment on a task with a due date becomes a reminder relative to it, counting a date-only due as 09:00 (`Pay rent 3 Nov remind me at 8` reminds an hour before), so it moves with the task and repeats with the series. On a task without a due date a moment is a one-off reminder at that time (tomorrow if the time has passed today), and an offset waits until the task gets a due date (its chip says *needs a due date*). `remind me` alone, or in quotes, stays in the title. The task, its rule and its reminders are saved together, offline too.
## Not understood
An unknown `#name` stays in the title unless you pick **Create project** from the list. The server and the REST API do not parse lines; the [`ot` CLI](cli.md) does with `ot add --natural`. Some ideas are listed under [future ideas](../ROADMAP.md#future-ideas).
## Data
Estimates are stored in the additive task field `estimate_minutes` (integer 1–10080 or null; see [api.md](api.md) and [sync.md](sync.md)). `@name` tokens are stored as label ids in the task's `labels` list, never as names; a new label is written as its own operation before the task, so both sync together and work offline.