Ken Blackman

Agreed. Much of the query functionality seems like it naturally could and should be recursive. My use cases:

Find nodes that are CHILD OF a node that contains the word “Related” and is a CHILD OF the target node, ie:

Concept 1
  Related
    @Concept 2
    @Concept 3

Find nodes that are linked to by a node that contains the word Related and is a child of the target node, ie:

Concept 1
  Related: @Concept 2, @Concept 3

And perhaps most usefully, find nodes that are in an instance of >related field in the target node, ie:

Concept 1
  >related::
    @Concept 2
    @Concept 3

@Alexander Schwarz is right— there's a super-easy way Tana could do this. Make the OpenAI base URL a system setting instead of hard-coded. Boom! Now we can point it to our own router.ai setup and use any model we want.

I like Claude better than ChatGPT for many if not most tasks... and increasingly, I would also prefer to financially support Anthropic over OpenAI.

YES! I do all of my best thinking and dictating while driving. I already use Tana Capture but as Jac said it's not only inconvenient, it's unsafe. So yes, please, carplay.

I came here today to suggest exactly this.

Has taken on new significance in recent days (March 2024) with the release of Claude 3, which I'd love to use inside Tana!

I would love to see add link and clear link. Links are actually hard to work with in Tana. You can't edit the text, you can't edit the URL, all you can do is click on it to open it in the browser. The selection toolbar is the perfect place to improve this.

I love it. I'm grateful you decided to include strikethrough and highlighting from the outset, rather than just going mvp. Thank you! Well done.

@Wannes I'm pretty sure @Greg Hadley is referring to the Display option on nodes that are viewed as tables or cards. (See images below.)

I have the same request, here's my use case: when I have a Search, I want to be able to see where the found nodes are located.

For example, if a node says "Don't trust him, he lies about everything," or "Best meal I've had in years," it would be useful to show the node's parent + ancestors. As it is, I have to click through.

Hence adding breadcrumbs as one of the Display options.

(Greg, would you edit your request to give more detail about the problem you're trying to solve, and what the solution would look like? )

I'm partial to Things 3's handling of recurring tasks. You can specify recurrence based strictly on the date, regardless of the state of the previous instantiation, as described above. OR it can be based off the completion date of the existing item—the next day, or 5 days or 3 weeks after the current item is marked done.

I've thought of this before too. If I write #replyto @Joe on @Voxer, and my #replyto supertag has instance fields for #person and #comm-channel, it would be nice if it had the smarts to fill those fields from the text. That workflow comes way more naturally to me, in this use case, than filling out the fields to build the title. (Though there are other use cases where I happily use build title from fields.)