If a user prefers having all the next actions listed on one screen, the user can use the Next Actions screen, and ignore the Focus screen. But it would be useful to be able to toggle Focus off so that the item disappears from the menu.

Thanks a million!

A new desktop version is ready for early access. Here’s the change log.

This version is quite special in that it has substantial architectural changes under the hood to enable better performance, reliability and development speed in the long term. Because of this there could be some bugs in the less frequently used features. Please share if you find any bugs - they will be fixed quickly.

If you are not comfortable rolling back to the previous version, please don’t install this version yet.

In case you need to roll back, the latest stable version can be downloaded from https://everdo.net

Download Links

• Linux (AppImage)
• Linux (Snap edge channel)
• Mac (Universal dmg)
• Windows (portable)
• Windows (installer)

inye:

May be best solution for me is to represent DevOps manager as a context, not as a contact. As i see, only thing that can be done with a contact that can’t be done with a context is the assignment to “waiting for:” field of a task, and i tend not to use that feature much anyway.

What if you renamed your contact to @DevOps manager? Any tag can be a context.

I don’t want to share the entire history of my projects with an LLM

I can absolutely see this! If sharing stuff like this with, say Anthropic, is within your threat model, you can run relatively powerful models locally.

Thanks for sharing the post about copying as markdown, will absolutely start using it for use cases like “also consider this task: …”. I’m coming from use cases more of the style of “please compile a list of todos for today” and “what did I achieve last week?”. The plan then is to have a bunch of MCP servers talking to all kinds of “action artifact stores” like Obsidian, Everdo, sent emails, …

It depends on what you are editing. Something simple like a title of an action is unlikely to go wrong, but something like creating entire items is risky.

I was particularly holding back from those use cases because it might lead to users unknowingly corrupting their database and then you having to deal with bug reports caused by my ignorance about the precise data model :-). LMK if you think some light editing (modify titles for example) should be within scope for my Python bindings and I’m happy to add that. But also fine with me to not have those features in the lib.

Thanks for you description of rationales behind current context and tag navigation options, they are now clear to me and i agree that they are important and useful.

However, my case is as follows. Imagine i have the project “Setup point of presence in new datacenter”. It is sequential and has following tasks:

• Work out new PoP budget with CFO. Context: @office, contact: CFO
• Order hardware for new PoP. Context: @email
• Arrange hardware setup. Context @office, contact: DevOps manager

I have also other tasks associated with contact “DevOps manager” - e.g. “waiting for: get and read reliability report for march”, "discuss migration to PostgreSQL @office” etc. I need some screen where i can see all tasks related to DevOps manager so i can check each task when we meet in office. I don’t want see “Setup point of presence in new datacenter – Arrange hardware setup” in this screen until first two tasks in “Setup point of presence in new datacenter” are complete, because time of this task didn’t come yet. BUT in my opinion it’s nice to be able to associate task “Arrange hardware setup” with DevOps manager during initial planning of the project.

In short, my use case is: view tasks that could be discussed with a contact immediately. For this purpose, non-first next actions in sequential projects are “blocked” by preceding next actions, and can’t be discussed with contact until all preceding tasks are done.

May be best solution for me is to represent DevOps manager as a context, not as a contact. As i see, only thing that can be done with a contact that can’t be done with a context is the assignment to “waiting for:” field of a task, and i tend not to use that feature much anyway. I tend to represent “waiting” state as an “ask about…” task, either as next action (“ask about it next time you’re talking”) or scheduled action (“ask about it after…”)

Any ideas about my use case would be greatly appreciated.

Thanks for your consideration!

There’s no special way to view all tasks for a contact, excluding the non-first next tasks. What is your use case for this?

To give a bit of context on why context vs tag navigation options were originally implemented to have different filtering behavior

When selecting a context list, you want to see actionable tasks that match the context.

When selecting a tag, it’s more like search - you want to see everything that matches. This mode supports contexts as well because they are tags as well.

There’s also “Tags” panel on the left. When user selects a context (or contact, or area) there, Everdo again shows tasks with this tag nicely grouped by their state (Next, Someday)… But now, in the “Next” section, Everdo shows all next tasks with the tag, including non-first next tasks from sequential projects. It’s perfectly OK to my opinion, too: i can see usefulness in the ability to review everything with a tag.

But i can’t find a way to see all tasks for a contact, excluding non-first next tasks from sequential projects. Is there any way to do it? Maybe i’m missing a filter somewhere? Or maybe it’s possible to implement “contacts” panel on the left like existing “contexts” panel, that would provide desired behaviour? Or maybe i’m completely missing the point – i’m new to Everdo, so everything’s possible.

Any help would be greatly appreciated. Sorry for long description, hope i managed to make it clear. Thanks!

P.S.: Thanks for the great app, worth every $.

gsujal:

Hmm why is that so? Asking because I have done minor edits to the db using dBeaver in the past. Took backups of course. Forgot why I did so.

It depends on what you are editing. Something simple like a title of an action is unlikely to go wrong, but something like creating entire items is risky.

1. You don’t know what assumptions the app is making about the data, so you could silently corrupt the data and break the application. I know you are probably careful about this and have backups, but it’s possible to go without noticing a problem until later on when the earlier backups are gone.
2. You update may work correctly today, but end up corrupting the database in a future version of the app that expect different things about the data.
3. None of your edits will reflect in the app until restart, which increases the probability of silently breaking something and only learning about it in a few days when you restart the computer

The button works in other views (Someday, Archive)

Definitely don’t try writing to the database, that will not work well.

Hmm why is that so? Asking because I have done minor edits to the db using dBeaver in the past. Took backups of course. Forgot why I did so.

• I have a StreamDeck and would like to see the current number of items in my Inbox on it (doesn’t need to be real-time). Buttons can just display contents of files so I now have cronjob using my Python library to count the items on inbox and write that number to a text file.
• Especially when it comes to really old tasks “I know I did that thing once, but can only remember that it contained the word apple”, nothing beats grep on the command line.
• On a similar topic: a bit of cut/awk/sort/uniq does wonders when it comes to long-term stats of style “how many tasks did I finish in every month last year?”
• I am currently planning to expose my Everdo list to an LLM via an MCP server.

At some point I noticed that some of these actions should really be done not by me but by a chatbot or an agent. So I naturally started putting in a bit more detail to give AI more context. Then I assign it a tag. I have a tag for coding agent and a tag for chatbot. When on the go, I will often come up with more tasks or pieces of context to give to AI. So I end up writing prompts essentially.

But these are still my tasks - they can’t really be done autonomously, because there will be back and forth between me and the machine. So putting them in Everdo seems like a natural fit to me. Then, when in the appropriate context, I filter by the AI tags and have an entire backlog of prompts to feed agents/chatbots.

This is why I find it useful to have something like this export as markdown feature. It’s one-click and it adds useful context by including project title and tags, so I don’t need to repeat what project the task is for in each action.

Definitely don’t try writing to the database, that will not work well.

Can you share more about your use cases?

finally got around to write some Python bindings for the Everdo SQLite database: GitHub - larsborn/everdo: A read-only zero-dependency Python interface to the Everdo GTD database · GitHub .

I realize that it might break anytime because I basically just guessed what the structure in the database means and it can change anytime. For that reason, I opted for a read-only approach. Then this tool will at least not corrupt databases and make Everdo maintenance harder than it needs to be.

That being said, I just really needed some very basic features for myself (counting current number of inbox items). LMK what you think and if you find it useful. Also bug reports, feature requests, and contributions are very welcome on Github!

Cheers
Lars

Seems I only noticed the issue today because it gets partially obscured in the rare case of the task title being at least 3 lines long, the task type being inbox/next/someday, and the description having a lot of text (enough to take up its max height). Cannot scroll to make it fully visible in this case.

Added a dummy task screenshot below.

Since it’s partially shown and better than before, I’m fine with how it is. Though I do wonder if the reminder button might get fully obscured on smaller height devices or if it becomes scrollable.

I appreciate this would complicate the feature quite some bit. But the dream I have is that I would type :p <some letter> and Everdo would begin to auto-complete (with a drop down appearing).

There’s no rule, but I don’t think this forum has enough Russian-speaking people for a discussion. You can privately message me in Russian.

This is indeed a bug with the android app. Sync works correctly in this case - your data is on the device, but the done section is simply not showing up in Scheduled.

I will have it fixed in the next android app update.

I’m having a problem with the Android app.

In the Windows app, in the Scheduled section, there’s an option for completed tasks marked as “Done”.

However, in the Android app, “Done” doesn’t appear in Scheduled.

I’ve already forced synchronization, but the problem persists.

Can you please help me?

Thank you very much.

Cristian Regazzo

I downloaded Everdo from Edge on my windows vm, and it gave me a message telling me that the everdo installer was a potential risk. After telling it to keep the file, I had the opportunity to give feedback, and one of the questions was if I was the owner/developer of the software. Not sure if you went through the process already, but I think it could help. Anyway I’m giving feedback to see if it’s approved.

I do often enter duplicates like this, but they usually don’t cause any issues during a review - I just hit the delete shortcut and it’s gone.

I think it would be quite challenging to detect a duplicate task reliably since you might word it slightly differently.

The additionally functionality Jensodeg mentioned by saving the webpage as a note in the inbox would also be nice too. - Perhaps this would be possible to implement by just clicking on the extension icon?
Much like how many other things like OneNote webclipper or Todoist One-Click works. That would make it faster than having to always spot the everdo icon in the right click context menu.

This is a “nice to have” feature. Not essential.

To make things easier, one thing I’m testing out is a menu option to export an item as markdown. This way I can write in Everdo and export with one click. I use it all the time now.

The “Copy as markdown” formats the item as a markdown document with front matter metadata and puts it into the clipboard. Great for LLMs to consume.

---
project: Project Name Goes Here
tags: [claude, Work]
---

# Task title goes here

Task description

I find this format works really well to give a lot of context to the agent/chatbot. I use it all the time now. But it can still be improved.

So I’m wondering if this is useful for more users.

When adding to inbox (if there was an inline command) → Stay in inbox
When processing inbox → Add to next

I could give this a try but I still think it’s something to keep behind a setting to avoid breaking the existing behavior for users who might depend on it.

When adding to inbox (if there was an inline command) → Stay in inbox

When processing inbox → Add to next

mercury:

Right now I usually put the project in the inbox item title. For example lets say I create an inbox item like “Develop dark mode feature for ProjectX”. Ideally I could just quick capture it like “Develop dark mode feature :pp ProjectX”. Well there’s no :pp inline command for adding a parent/project, but ideally there would be! Anyway, I can capture that context in the title yes but it’s more work later when I need to both fix the title and also assign the item to the project through the GUI.

How do you capture this item? Is it via the global shortcut or i in the app?

I actually tried disabling the forced Next transition in the editor and found it annoying that now you’d have to move every item to Next manually in addition to assigning a project.

So maybe this can be workflow-dependent. I think if there was a way to specify a project in Quick Capture, then this absolutely should not move the task to Next. But when you edit an existing one in Inbox, then I think it should move it to Next unless you manually set another status.