31–40 of 60 posts
It would be fantastic if this supported email and calendar providers that weren't Google. Supporting protocols like IMAP or JMAP alongside CalDav would be a fantastic step, as well as open source note-taking apps like Hyprnote would be neat.
This is cool! A couple of pieces of feedback as I am looking for something in this family of things but haven't found the perfect fit: 1. I have multiple inboxes, and want to have them work on multiple. 2. I would really like to have skills and mcps visible and understandable. Craft Agents does a nice job of segmenting by workspace and making skills and mcps all visible so I can understand what exactly my agent is se…
I think this is a good example of what a good landing page can do.. I can immediately tell what it can do and the visualization makes me want to try it. And I don't think it is particularly refreshing or anything.. it just seems cool.
[dead]
A design choice we made was that each note should be usable by the user too, not just the AI. For example, if someone opens a project note, they should be able to immediately understand its current status. Linking notes and using backlinks became a natural way to surface relationships and references while keeping things human-readable.
Earlier quoted context omitted.
Interesting framing! We’ve mostly been thinking of inconsistencies as signals that something was missed by the system, but treating them as attention points makes sense and could actually help build trust.
This was something that I was working on for a personal solution ( flagging various contradictory threads ). I suspect it is a common use case.
Prompting is a very specialized skill, average users just don't know what to ask for to get the most out of the LLMs.
Ideally the UX should organize and surface information to the user that is important automatically, without needing to be prompted.
The knowledge graph is well done. I think what's missing from all coworking apps is the UX. Prompting is a very specialized skill, average users just don't know what to ask for to get the most out of the LLMs. Ideally the UX should organize and surface information to the user that is important automatically, without needing to be prompted.
Earlier quoted context omitted.
Thanks. Obsidian and Logseq were definitely an inspiration while building this. What we’re trying to explore is pushing that a bit further. Instead of manually curating the graph and then querying it, the system continuously updates the graph as work happens and lets the agent operate directly on that structure. Would love to know what kind of scripts or plugins you’re using in Logseq, and what you’re primarily using…
My point was to say that your idea should work because today's models are capable enough. If I get some time later today, I'll post my scripts.
What are the plans for monetization?
This is a product that just makes sense to me - well done on picking a great problem to solve and communicating it so well. What are the plans for monetization?