engomez

4 ms·

31.
by engomez 3mo ago
Yup, taking a look at it. Expect it integrated within next week.
32.
by engomez 3mo ago
Two key pieces: 1. True WYSIWYG UI 2. MCPs and skills support showing the OpenKnowledge web UI within the Desktop apps, as well as things like agentic search with embeddings and other goodies. We also add AI affordances into the UI, includ
33.
by engomez 3mo ago
Give us a follow on X: @openknowledgeai, we'll post updates there. Or feel free to dm me at @nickgomez and I'll reach out when available.
34.
by engomez 3mo ago
We support most things except bases at the moment. Let us know if you see any gaps that are important for you.
35.
by engomez 3mo ago
CLI is cross-platform, works on Linux/Windows. We've tested it but the environments can vary, so definitely let me know if see any issues. Re:front-matter, we do optimistic parsing of it, haven't seen any issues with it. If w
36.
by engomez 3mo ago
Got it, we'll investigate.
37.
by engomez 3mo ago
Could you share more on what's important for you there?
38.
by engomez 3mo ago
Ack, thanks for feedback ! We're definitely looking at a more integrated experience.
39.
by engomez 3mo ago
The external agents can open the open knowledge web viewer within their own embedded web UIs. Within the OpenKnowledge app itself, right now we do support the Claude terminal embedded inside - try that out. We're looking at adding more
40.
by engomez 3mo ago
Appreciate it. Editor should already be pretty "Notion-grade", more to do though. What functionality is most important to you re:Notion?
41.
by engomez 3mo ago
Haven't tried it, will take a look. High level general purpose "IDE" for document editing (think Google Docs, Notion), that also exposes MCP/Skills for LLM wiki/second-brain scenarios. Seems Rowboat is more focused
42.
by engomez 3mo ago
Keeping the MCPs/skills cross-compatible across the different harnesses, and also getting non-eng folks familiar with git.
43.
by engomez 3mo ago
We wanted to make our own editor experience, allows us to do things like proper WYSWIG editing (Notion-like editor). MCP/AI integrations were one piece.
44.
by engomez 3mo ago
Our bar was "Notion-grade", i.e. drag and drop blocks, slash commands, select to highlight/bold, etc. I don't think I'd seen an extension that does that. It was a technically very hard problem, rich text editors usu
45.
by engomez 3mo ago
Got it, investigating.
46.
by engomez 3mo ago
(We're same team behind Inkeep -- already have a healthy biz).
47.
by engomez 3mo ago
Don't ask our VCs. Kidding -- we're taking a look at what would make sense for a cloud solution. E.g. richer team collaboration, etc.
48.
by engomez 3mo ago
Got it, makes sense. And neat ideas for the virtualization, will take a look.
49.
by engomez 3mo ago
Yup, we're working on it, should have integration eod or tomorrow.
50.
by engomez 3mo ago
Ack ! re: Web app do you mean local web UI, or web hosted?
51.
by engomez 3mo ago
Integration with local models/harnesses is top the queue. What IDE or Harness do you use? We're looking at OpenCode/Zed next but open to input.
52.
by engomez 3mo ago
OpenCode is next on the queue. Each has it's quirks, just working through quality testing each.
53.
by engomez 3mo ago
Looks very relevant, will take a look. Definitely looking at built-in-chat-ui, thinking about how to integrate with the harnesses.
54.
by engomez 3mo ago
Appreciate it !
55.
by engomez 3mo ago
Gotcha. We're optimizing for the same scenarios, may be worth a look at our implementation in case transferable to yours. See: #1 - the "autosync" and GitHub integrations do exactly this. #2 - The app auto-instals skills&#x2F
56.
by engomez 3mo ago
It would make a repo in your own GitHub account. You can choose whether that repo is in your personal GitHub or your GitHub org. We'll make that clearer in the UX. Feel free to ping me any additional feedback any time (here or @nickgom
57.
by engomez 3mo ago
The skills should be pretty progressive disclosure optimized but we'll do an audit.
58.
by engomez 3mo ago
Skills / MCPs are not hard requirement, they're tailored for the desktop agents to be able to leverage built in tools we make available for e.g. agentic search over the content and manipulating the open knowledge web viewer and ed
59.
by engomez 3mo ago
That was our exact stated goal -- felt a lot of the same pain. Feel free to drop me any feedback here or @nickgomez on X.
60.
by engomez 3mo ago
Right on. We did a lot of the same and then had to deal with coaching everyone on the team how to do also set it up. Large inspiration for OpenKnowledge was providing these flows out of the box. We'll prioritize Hermes/OpenClaw gu

More ›