Amplenote Explained 18: Organizing tasks with inline tags (GTD)

TL;DR

Inline tags let tasks be labeled at the line or section level, avoiding the all-or-nothing limitation of traditional sidebar tags.

Briefing Cornell Notes

Briefing

Inline tags in Amplenote turn task management from “whole-note labeling” into line-by-line control. Instead of applying a traditional sidebar tag to an entire note, inline tags can be attached to a single line, a specific section, or even one task—making it easier to slice a long to-do list into actionable chunks that match real-world constraints.

The core idea is to use “context” notes—ordinary notes that represent the conditions needed to complete a task. A task can be tagged with a context like “at home” (because it requires being at a specific location) or “at errands” (because it requires leaving the house). The “at” prefix is presented as a convention that helps contexts stand out and enables quick lookup by typing a double at (“@@”), which brings up a list of available contexts. Contexts are meant to reflect what actually determines whether work gets done: location, nearby people, required tools, internet availability, time of day, and even mental or physical state.

Practical examples illustrate how varied these contexts can be. The system includes an “at offline” context for tasks that can be completed during longer plane flights without internet access, an “at phone call” context for grouping short calls, and an “at low energy” context for tasks that remain doable even when motivation is poor. The transcript emphasizes that contexts differ from person to person, and encourages pausing to brainstorm situations where time and means exist but the next action is hard to identify.

To use these contexts effectively, the workflow is anchored in Amplenote’s Tasks mode. From there, users can open “filter tasks” and select a context to narrow the task list. For instance, searching for the “at offline” note during travel surfaces only tasks that were tagged as doable without connectivity. Selecting an “errands” filter and saving it to shortcuts supports mobile use: tasks that can’t be done at home can be batched while out.

Contexts also help with exclusion. Tasks blocked by other people can be tagged with “at waiting,” then filtered out by shifting and excluding that context from the search results. For habit tracking, contexts can function like time-based triggers without assigning calendar start times: tagging habits with “at evening routine” enables a pinned filter for quick access every evening. Even “at busy” is framed as a practical tool—used not for doing the task itself, but for tracking how to get out of bowling night.

Overall, the method relies on linking tasks to context notes, then retrieving those tasks through inline-tag filters in Tasks mode. The payoff is a to-do list that adapts to the situation at hand—what’s possible right now—rather than a static list that assumes perfect conditions.

Cornell Notes

Inline tags in Amplenote let tasks be labeled at a granular level—down to a single line—rather than tagging an entire note. By linking tasks to “context” notes (ordinary notes like “at home” or “at offline”), users capture the real conditions needed to complete work: location, people, tools, internet access, time of day, and even mental or physical state. In Tasks mode, context filters make it easy to pull up only the tasks that match the current situation, such as errands while out or offline tasks during flights. Contexts can also support exclusion (e.g., “at waiting”) and time-based habit access (e.g., “at evening routine”) without calendar start times.

How do inline tags differ from traditional sidebar tags in Amplenote, and why does that matter for task lists?

Inline tags can be applied to a single line or a specific section of a note, while traditional sidebar tags apply to an entire note. That granularity matters because long to-do notes often contain multiple tasks with different requirements; line-level tagging lets each task carry the right constraint (like location or connectivity) instead of forcing everything in the note to share one label.

What are “context” notes, and what kinds of constraints should they represent?

Context notes are ordinary notes used as targets for inline tags—often named with an “at” prefix by convention (e.g., “at home,” “at errands,” “at offline”). They represent the conditions needed to complete tasks: being in a certain location, having another person nearby, having specific tools, lacking or having internet access, doing work at a particular time of day, or being in a certain mental/physical state.

How does the double “at” convention help users manage contexts?

Using “at” in the context note title makes contexts easier to distinguish and enables a quick lookup workflow: typing a double at (“@@”) prompts Amplenote to show a list of contexts. That speeds up tagging because users can select the right context note without manually searching for it.

What workflow turns context tags into an actionable task list?

The workflow centers on Tasks mode. Users click “filter tasks” and choose a context. For example, selecting the “at offline” context surfaces only tasks tagged as doable without internet access—useful during plane flights. Selecting “errands” and saving it to shortcuts supports quick access on mobile while out, enabling batching of tasks that can’t be done at home.

How can contexts be used to exclude tasks that are blocked?

Tasks waiting on other people can be tagged with “at waiting.” When searching, users can shift-click the “at waiting” context to exclude those tasks from the results, keeping the active list focused on what can be done now.

How can contexts support habit tracking without calendar start times?

For habits that depend on time of day, users can tag them with a context like “at evening routine” instead of assigning start times on the calendar. Then a pinned filter in the sidebar provides quick access to those evening-tagged habits each day.

Review Questions

What types of task constraints are best captured as contexts, and which examples from the transcript match those constraints?
Describe how a user would use Tasks mode filters to find offline tasks during travel.
Give one example of using a context for exclusion and explain why that improves a to-do list.

Key Points

1
Inline tags let tasks be labeled at the line or section level, avoiding the all-or-nothing limitation of traditional sidebar tags.
2
“Context” notes are ordinary notes that represent the conditions required to complete a task, such as location, people, tools, internet access, time of day, and mental or physical state.
3
Using an “at” prefix is a convention that makes contexts easier to distinguish and enables fast context selection via typing “@@.”
4
Tasks mode plus “filter tasks” turns context tags into situation-aware task lists, such as “at offline” for flights or “errands” for mobile batching.
5
Contexts can also support exclusion: tagging blocked work with “at waiting” allows users to shift-click and remove those tasks from active searches.
6
Pinned context filters can streamline habit tracking by grouping time-of-day-dependent habits like “at evening routine” without calendar start times.
7
The most effective contexts are personal: they should match how the user typically looks for work they can do in the moment.

Highlights

Inline tags make it possible to tag a single task (or even a single line) with the exact constraint it needs, instead of tagging an entire note.

Context notes like “at offline,” “at phone call,” and “at low energy” show how task lists can adapt to travel, communication windows, and motivation levels.

Filtering tasks by context in Tasks mode enables quick, batchable action—especially when paired with saved shortcuts on mobile.

Tagging blocked items as “at waiting” supports exclusion, keeping the active list focused on what’s actually doable now.

Topics

Inline Tags
Task Contexts
Tasks Mode Filters
Habit Tracking
Productivity Workflow

Mentioned

Amplenote