Using Tabs in OmniFocus

Introducing Tabs


OmniFocus’ recent builds (beta test build version 2.8 as of this writing) have introduced tabs, much like we find in our Internet browsers. Here’s an example:


I’ve been experimenting with using the tabs to organize how I approach work by sessions. Notice the above arrangement. When working, I do so from right to left. On the right are the project tasks:


I can work away, adding thoughts to the Inbox as needed via Quick Entry. When I feel that I have done enough work in the session, I close the tab with Command-w.

Using the above structure, this brings me to the Inbox, where I can process it as part of closing the session.


When I’m done processing the Inbox, and I feel that there is nothing more about the session that comes to mind, I once again close the tab with command-w to return me to the Dashboard:


… where I can mark the “Develop: Blog post on tabs” task as complete and once again decide what to do next.

Menu Options

There are 6 menu options related to tabs that are scattered throughout the menu bars:

  • File > New Tab
  • View > Show Tab Bar
  • Window > Show Previous Tab
  • Window > Show Next Tab
  • Window > Move Tab to New Window
  • Window > Merge All Windows

The last one, “Merge All Windows” takes all of your open windows and converts them into a single window with multiple tabs.

Using Shortcuts

Using Keyboard Maestro, I’ve added shortcuts as follows:

  • New Tab (Command-t)
  • Show Previous Tab (Control-Option-Command →)
  • Show Next Tab (Control-Option-Command ←)
  • Merge All Windows (Control-m)

The “New Tab” function already has a built in command (Option-Command-t), but I prefer the same key command as I find in Safari.

Using the Go To Link Script

Jesse Hollington created a script that takes you straight to a link from a task in a note field using a Key Command. A neat side effect is that, using the command opens a tab. (If it just opens in the same window for you, see the footnote below.) 1. So, for instance, here I select a session I want to work on:


I’ve opened the note field to show the Copy as Link pasted link in the note field. However, the note field does not need to be opened for the process to work. I then type my assigned key command (Command-g) and a new tab with my desired project opens:


The system is not perfect as no system is, but it’s been fun to play with.  There are still some variations I’m entertaining, too.


  1. Well, this works sometimes. Sometimes it opens a new window instead of a new tab. If that happens, I type Control-m to merge windows. I haven’t figured out what I’m doing differently to create the inconsistency yet.Also, you need to have the “Open in a New Window” option checked in the Open Panel (Command-o) for this to work, too:open-in-new-windowOtherwise, it just replaces the current window with the linked window.↩︎

Reviewing Large Projects

Large projects can be difficult to navigate for any number of reasons. When I refer to large projects, I mean those that span at least several OmniFocus projects and possibly several folders of projects.1 Here is an example from Zen & The Art of Work which had 16 video modules and other projects within several folders:


One reason large projects can be difficult is that there are so many tasks. It becomes hard to quickly know what a most efficient or impactful next action might be.

One means of addressing this is arranging the tasks in a project, perhaps setting priority tasks higher in the project itself. That way, if you are visiting the project or using a perspective with a “Sort actions by:” setting at “Project”, you will see those higher priority tasks up top.

However, when tasks are sent to projects from the Inbox, they are only added to the bottom. While it would be nice, it is not often practical to follow up each and every task to make sure it is well placed within its respective project, as it is processed from the Inbox. Unfortunately, when we later get to the project itself, there can feel like little rhyme or reason as to the order.

For example, while working on one module of the Zen course, I would have ideas about what to do with other modules, which I would dutifully add to the Inbox or even directly to their corresponding modules. After a while, though, there would be a slew of tasks added throughout, without clarity as to what had priority or what the relationship of tasks might be to each other.

Certainly, review is helpful, but I did not want to review each of these projects every day or even weekly. It would just be too much. Setting them to monthly was useful, but their reviews would easily become staggered.

Instead, a tactic I found useful was to deliberately change the review date of these specific projects to “today” on the day that I felt ready to do a solid review. In other words, using Shift or Command, I would select all of the projects I wanted to address:


then go to the Review section of the Inspector and enter “today” as the next review:


Of course, this works best when I am on top of my reviews so that there is nothing else in the way:


Leveraging the default OmniFocus review system, I could then sit and review each project in my own time:


If I reviewed a few projects and then set it aside, that would be fine.  I could always pick up the process later. Meanwhile, I left the default review frequency for these projects at monthly.


  1. I would like to come up with a term that means large project without using the word “project”, but have not been able to come up one that feels satisfying. I’ve thought of “endeavor” and “craft”, but they don’t feel right. Any suggestions? ↩︎

Quick Entry & Inbox Settings in OmniFocus

An Inbox is integral to any solid task system. Whether we decide to use a piece of paper for a single session of work or a task manager to orchestrate many sessions, we need some way to set thoughts aside while focused.

There are several important properties of an Inbox are that it:

  • Can be called quickly,
  • Will remain until dismissed, and
  • Can be sent away quickly.

When we can call it quickly, ideas can be written without fuss.  When it stays until dismissed, we can better settle with the sense of having addressed the interruption. When we can move it out of the away quickly, we can reduce a tendency to be distracted by whatever we’ve put in it. Together, these properties allow us to field interruptions, whether they come from our own ideas or from outside demands while we maintain a chosen focus.

Problematic Inbox Use

However, we can still use an Inbox problematically by assigning a task more characteristics than are necessary to simply setting a thought aside.

For example, while I work on Project X, an idea comes to mind about checking on a file upload I had started earlier. I might then write, “Check on file upload”, assign it to its own  project “Build Flying Saucer” and also assign it a context “@Laptop”. I then decide if that is enough information for me to see the task when and where it would useful to be seen. Perhaps I add a defer date, due date, or flag, too.

While it may seem that I am saving future Inbox processing time, I am actually creating several avoidable problems such as:

  • Focusing too much on the interrupting idea, while my chosen focus falls to the side. Since I am effectively skipping the Inbox, I will not see the task until I encounter it through the system, so focus on how and when it will appear becomes important.
  • Incorrectly filing the idea, and then really need to derail myself from my current work to address it.
  • Incorrectly filing the idea and not realize I had done so, thereby missing it later.

Simpler Inbox Use

A better way to handle an interruption is to simply add the idea to the Inbox without assigning it any characteristics. That way I can focus on processing it later as its own session. For example, just writing “Check on file upload for flying saucer” in the Inbox is enough. Not assigning a project is particularly important when a default context is assigned to its project, and the clean up process will whisk it away.

Later, when processing the Inbox, I could just take care of a task if it takes 2 minutes or less. If it might take longer, I could now deliberately focus on how I wanted it to show up in my system. The session is dedicated to processing the Inbox.

Experimenting with Quick Entry Settings

I’ve been experimenting with a few settings of both the Quick Entry and Inbox to streamline their use and have listed them below. I should point out that I use not only OmniFocus’ Inbox, but others as well such as a sheet of paper for certain types of sessions.



The Quick Entry guides me to only enter what is necessary for now. The Quick Entry is simply presented, prompting me only for the task’s title and contact.  The project, defer date, due date, flag, and note fields are conspicuously absent.  If I truly need to add a flag, I can use my key combination (Shift-Command-L) or if I need to add a note, I can use (Command-’).

This way, the task will not be automatically whisked off to projects that have a default context assigned. It is deliberately held in the Inbox for later processing as its own session.

To set your own Quick Entry appearance:

  • Open the Quick Entry panel (I use the default key combination Control-Option-Space)
  • Select the Eye icon in the bottom left corner:

Quick-Entry-on-OSX-prefs.png Which reveals the following:


My settings are noted above.

(Addendum 2016-11-10:  After some time, I’ve reverted back to including the Project column in Quick Entry:


Legacy vs Default Behavior

Secondly, I prefer to use the legacy behavior of the Inbox from OmniFocus 1. In OmniFocus 2, the Inbox disappears by typing Return.  However, I often have several ideas at once, and I would like the Quick Entry Inbox to remain until I am done with it.

If you would like to use legacy, OmniFocus 1, behavior, then enter the following code into Safari[1]:


For any setting changed via URL, you can revert to the default value by omitting a value entirely, like this[2]:


In legacy behavior mode, the following entry methods work:

  • (Return) ends task editing. (Return) again creates a new task.
  • (Control-Return) makes a new task immediately below the currently edited one.
  • (Shift-Return) creates a new task above the current one

When done entering tasks,

  • Use the clean up command (Command-k).

Inbox on OS X

When I process the Inbox, I do so as a dedicated session. I would like to have all resources available. Therefore, I use a fuller set of the preferences to show all major components by opening the inspector (Option-Command-i) as well as having more components available inline:


The settings can be accessed via (Shift-Command-v). Here are my own:


Certainly, these are not the only settings possible or potentially useful to you. But the idea remains the same. The Inbox should be:

  • Easy to get to
  • Easy to keep in place until dismissed
  • Easy to remove from sight
  • Easy to process as its own session of work

  1. Note that this sort of coding into Safari is not officially supported by the Omni Group, nor myself.  ↩
  2. I use Keyboard Maestro to hold onto these sorts of codes I’ve gathered:

Quick-Entry-Legacy-KM.png Quick-Entry-Default-KM.png

That way, I just toggle between the modes using the key command Shift-Control-c, and then a number key, as noted above.

A Daily Review Habit

“Falling off the GTD wagon” (or any task system for that matter) can be all too easy and all too disrupting.  Especially, when you’ve grown used to a system, the gradual loss of trust in that system can come with feelings of anxiety, the need for constant damage control, putting out fires, losing follow up tasks, losing communication trails, losing the state of projects, and more.

To keep a system useful, it needs to be reviewed regularly. I often say that I’m not sure a system even exists unless it is reviewed.

Getting Things Done author, David Allen, suggests weekly as an optimal frequency. I used to review my entire system weekly and had done so for several years. At times, the review process would take me about 1-2 hours. I’d often feel quite positive about doing a review as I know how on top of things I can feel.

But, that is a chunk of time.  I can easily see how a person would lose the interest in review especially at times, for example, when things are very heavy or very light. At those times, you may think either, “I have no time” or “Why bother?”, respectively. The problem is that work ebbs and flows, and you can get hit with a whole bunch at once.

Nowadays, I do both a daily and a weekly review, which interestingly saves me time. The Daily Review takes about as long as my coffee takes to brew in the mornings. The Weekly Review is more centered on system blindspots and now takes about 20-30 minutes.

The Daily Review

My Daily Review includes:

  • Clearing the Inbox,
  • Reviewing any projects that are in the Review indicator, and
  • Making sure my flagged projects are appropriate for the day.

Generally, I use the iPhone to do this:

Morning Mini-Review - Before & After

Detailing the process, I:

  • Examine my calendar to review my scheduled meetings and appointments.
  • Acknowledge any tasks that are due soon as noted from the Forecast view.
  • Process the Inbox to “0”
  • Review all projects requesting review, thereby bringing that number to “0”. Note that this is a different method of Review than what I was doing when writing in Creating Flow with OmniFocus. At that time, I was doing the Weekly Review session only. Now, I do this aspect of the review daily.
  • Review the Land & Sea project as needed. I set its review reminder to every other day, so it is examined very regularly as part of this Daily Review.
  • Examine the Dashboard and decide if it supports me for the day.
  • Process the Inbox to “0” again, as needed.

If I want to be more thorough, I may also:

  • Review my Communications perspective
  • Review my Filing perspective

When I can sit with my tasks and calendar with a sense that they will support me and nothing else comes to mind, about my day or otherwise, I can then pause and decide on what to do next.

This can seem like a lot, but when you’re practiced, all of this can take only a few minutes.  Even if you work from a simpler set of lists, maybe only a single todo list, the same applies.  Examining the list and waiting until nothing else about it comes to mind can be a powerful way to help you move through your day smoothly.


My Current OmniFocus Dashboard “Recipe”

My workflow has, in general, shifted towards a session-focused style, as is evident from my recent post.  Essentially, that just means that my dashboard of tasks number only a few (about 5-8, give or take) and each represents a session of work. They are not very specific tasks and are more orchestrating in nature.  This means that my choices of what to do next are simple.

In addition, I tend to work by habit. In other words, I often work on a project over multiple sessions.  Similarly, my routines for maintenance are also a matter of recurring sessions.

As a result, my Dashboard has largely become a series of repeating tasks, using the “Defer Another” function.  Tasks repeat at different frequencies – daily, weekly, monthly, or other.. My current Dashboard “recipe” includes the following:

  • 1-3 “Land & Sea” tasks daily (“Land & Sea” Project)
  • 1 Office Filing task on weekdays, (“Routine : Home & Office” Project)
  • 1 Home Filing task on Fridays, (“Routine : Home & Office” Project)
  • 1 Weekly Review task on Fridays, (“Routine : Home & Office” Project)
  • 1 Family Agenda review everyday, (“Routine : Home & Office” Project)
  • 1 Develop: Music task everyday, (“Music & Artistry : Music & Artistry” Project)
  • 1 Morning Communications on weekdays, (“Routine : Home & Office” Project)
  • 1 Afternoon Communications on weekdays, (“Routine : Home & Office” Project)
  • 1 Financial Maintenance task monthly, (“Routine : Home & Office” Project)
  • Rare odds & ends when they do not fit in the above.

Each task links to a custom perspective or project.

And, of course, there are types of habitual work that do not appear above. For example, I also have the clients I see throughout the day, so I often check on my @Office : Agendas context in the morning.  Clients are scheduled in the calendar.

Also, these tasks are not forced.  For example, a particularly busy day with clients means I may not make it to a Land & Sea project that I thought I could have. If that occurs too often, though, it is likely time for me to re-evaluate my workload. In that way, I use my understanding of how the system is stressed to consider where to make adjustments in my general workflows.

Stats reports for OmniFocus

OmniFocus is very much an app about doing.  It’s not designed with graphical reporting in mind.  Here’s a neat app, though, put together by Thomas Schoffelen, that shows a list of open tasks, and completed tasks from the last 7 days, last 3 months, and completed per weekday.


Omnifocus stats