← Back to context

Comment by btbuildem

25 days ago

Interesting take! It does seem to address a typical "intermediate" workflow; even though we prefer linear finished products, we often work by completing a hierarchy first. I've been using Gingko [1] for years, I find it eases the struggle of organizing the structure of a problem by both allowing endless expansion of levels, and easily collapsing it into a linear structure.

In your case, do you hold N contexts (N being the number of leaves in the tree)? Are the chats disconnected from each other? How do you propose to transition from an endless/unstructured canvas to some sort of a finished, organized deliverable?

1: https://gingkowriter.com/

Great questions!

> In your case, do you hold N contexts (N being the number of leaves in the tree)?

It depends, contexts are just a form of grouping

> Are the chats disconnected from each other? > How do you propose to transition from an endless/unstructured canvas to some sort of a finished, organized deliverable?

RAG with in-app commands, i'm working on a local RAG solution, it's early but promising. Basically chat with all your data and applying a wide range of command on it.

> How do you propose to transition from an endless/unstructured canvas to some sort of a finished, organized deliverable?

Why would they, though? For me as a potential user of this (and someone who thought about building a tool like this for myself), the tree (or better, a directed graph) is the desired end result.

Slightly OT, but there was a standalone software just like gingko for the Mac. Do you now something about it?

Edit: I think it was an old version of gingko as a desktop app. Still available at https://github.com/gingko/client/releases

> Gingko

A subscription pricing model for software where everything should stay on my machine is a no-go for me