segmenta

7 ms·

1. 31.▲
   by segmenta 3mo ago

   That is great to know! We heard of others pointing Claude to the knowledge graph. It made us double down on building a Claude desktop alternative, so we could couple them deeply. For instance, there are places you could provide feedback on
2. 32.▲
   by segmenta 3mo ago

   Yes, that's mostly right. Surfaces are the primary artifact for collaborating with the assistant - each one attaches an app to a workflow and gives both you and the agent a structured place to work, instead of everything flowing throug
3. 33.▲
   by segmenta 3mo ago

   Thanks, would love your feedback after trying it.
4. 34.▲
   by segmenta 3mo ago

   I would like to be on the beach. But seems like people are working more and not less with AI. Somebody needs to care enough.
5. 35.▲
   by segmenta 3mo ago

   Thanks! Would love to hear what you think, after you get a chance to try it.
6. 36.▲
   by segmenta 3mo ago

   Fair point. But our goal with Rowboat is to do the opposite, to distill down only the parts you care about. For instance, you are not expected to read meeting notes, the important parts from it are added to your knowledge graph. That way ne
7. 37.▲
   Show HN: Rowboat – Open-source, local-first alternative to Claude Desktop(github.com)

   219 points by segmenta 3mo ago|99 comments
8. 38.▲
   New IronWorm malware hits 36 packages in NPM supply-chain attack(bleepingcomputer.com)

   5 points by segmenta 4mo ago|0 comments
9. 39.▲
   TeamPCP's Mini Shai-Hulud Is Back(stepsecurity.io)

   1 points by segmenta 5mo ago|0 comments
10. 40.▲
    Making LLM Training Faster with Unsloth and NVIDIA(unsloth.ai)

    129 points by segmenta 5mo ago|25 comments
11. 41.▲
    by segmenta 8mo ago

    Great, looking forward to it.
12. 42.▲
    by segmenta 8mo ago

    Yep - if you just want the assistant to access your Obsidian vault, you can point it to the vault during chat. If you’d like it to show up in the UI as well, or don't want to point to it on every chat, you can copy the vault to a folde
13. 43.▲
    by segmenta 8mo ago

    Thanks! 1. We chose Markdown deliberately so each node is human-readable and editable. The idea is that a project or person note represents the current state of that entity, so you can just open it and understand what’s going on. That also
14. 44.▲
    by segmenta 8mo ago

    Appreciate that. We think having a transparent and fully local option really matters.
15. 45.▲
    by segmenta 8mo ago

    That’s great to hear! Would love to hear your feedback once you’ve had a chance to try it.
16. 46.▲
    by segmenta 8mo ago

    Thanks! Appreciate it.
17. 47.▲
    by segmenta 8mo ago

    This was a really interesting read. Thanks for the detailed breakdown and the office references. The multi-persona approach is interesting, almost like a mixture of experts. The corporate email contradiction use case is not something we had
18. 48.▲
    by segmenta 8mo ago

    Thanks for the kind words. We plan to offer an account-based option for users that want zero setup, with managed integrations and a choice of LLMs.
19. 49.▲
    by segmenta 8mo ago

    Thanks, completely agree. UX is probably the hardest part here. Prompting should not be a prerequisite for getting value. We have been thinking about making the system more proactive, for example surfacing relevant notes ahead of meetings o
20. 50.▲
    by segmenta 8mo ago

    That’s interesting. Would be curious to know what types of contradictions you were looking at and how you approached flagging them.
21. 51.▲
    by segmenta 8mo ago

    Nice, that sounds like an interesting approach. We did try simpler setups first, including giving the model direct access to raw emails and meeting notes. It works to some extent, but it’s harder to maintain a clear notion of “current state
22. 52.▲
    by segmenta 8mo ago

    Really appreciate that. Glad the visualizations made sense.
23. 53.▲
    by segmenta 8mo ago

    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.
24. 54.▲
    by segmenta 8mo ago

    The graph building agent processes the raw files (like emails) in a batch. It gets two things: a lightweight index of the entire knowledge graph, and the raw source files for the current batch being processed. Before each batch, we rebuild
25. 55.▲
    by segmenta 8mo ago

    We use a two-layer approach. The raw sync layer (Gmail, calendar, transcripts, etc.) is idempotent and file-based. Each thread, event, or transcript is stored as its own Markdown file keyed by the source ID, and we track sync state to avoid
26. 56.▲
    by segmenta 8mo ago

    Really appreciate the detailed feedback. There are bunch of great features that you are pointing out that are on our roadmap (will add whats missing). The agent can setup tasks on schedule and help manage them. You can try a prompt like &#x
27. 57.▲
    by segmenta 8mo ago

    Good question. We don’t pass the entire graph into the model. The graph acts as an index over structured notes. The assistant retrieves only the relevant notes by following the graph. That keeps context size bounded and avoids dumping raw h
28. 58.▲
    by segmenta 8mo ago

    Graphiti is primarily focused on extracting and organizing structured facts into a knowledge graph. Rowboat is more focused on day-to-day work. We organize the graph around people, projects, organizations, and topics. One design choice we m
29. 59.▲
    by segmenta 8mo ago

    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 gra
30. 60.▲
    by segmenta 8mo ago

    Thanks! Agent capabilities are getting commoditized fast. The differentiator is context. If you had a human assistant, you'd want them sitting in on all your meetings and reading your emails before they could actually be useful. That&#