I made github.com/Inkami-app/c.... It’s a simple
server which (re)spawns Claude code instances with remote control running. I leave it running on my desktop when I’m stepping away from it.
Hope someone else finds it useful, because the sheer unreliability of remote control was driving me crazy.
I think Inkami is v1 complete feature wise. I just need to get it locked down. Extensive bug testing, documentation, videos, stress testing and then marketing.
Oh, and now you can import your #obsidian and #notion work into Inkami.
inkami.app
#buildInPublic
I realise I’ve been radio silent for a while now but LOTs of stuff done during this time
Well. Maybe not as much on the surface 😅
The biggest thing has been collaboration! Now you can share inkami documents privately and even allow other collaborators to come edit your document with you.
#update
I was tired of building the same features and screenshot grids. Thought I’d try something different. What do you all think?
#buildinpublic
I *need* to make demo videos, and I *need* to update the landing page, *need* to market. Yet, I mess around with smooth transitions of all the things 🙈
#buildinpublic #badEngineerHabits
Most of the week, I spent on tracking down a weird data-loss bug 😮💨 . Ended up:
- Overhauling the reconnection and data connection pipeline
- Building a document history panel
This was a hairy bug
Having to resort to pushing to git manually like a plebeian because my Claude code weekly limit is approaching 100% and I still want it to finish wiring up the latest feature
It’s easy to ignore the importance of having a good optimistic cache on the frontend. Inkami was simple where each ‘smart feature’ extracted from documents (agenda, tasks etc) required a round trip to the backend. That meant delays causing confusions for users. Now it’s instantaneous yet consistent.
Spent my time on inkami today making the reconnection logic solid. The problem with using Automerge is that if you’re not careful, you can end up with empty documents. The data isn’t ‘lost’ but for users it looks like that. Which is scary and erodes trust.
I’m really impressed by how well Plus Jakarta Sans works for writing. I had never used it before but now it’s become indispensable within Inkami. I was thinking about switching to Inter once, but it seems wrong somehow.
It all starts with a question and a quest.
Question: if I write and share my thoughts across my devices, do I always have to store it with someone else?
Quest: To build a writing platform that builds on some of the best ideas in productivity writing.
Inkami.app
So with these, Inkami is becoming a proper personal productivity tool that’s also focused on data security and #privacy.
Still not polished enough to be released to the public yet and there’s still a way to go but if you’re interested, please follow and sign up for the waitlist on Inkami.app
All tasks from across your documents are collected in the tasks view which shows as a Kanban board.
The circles represent tasks with multiple states. For now states are limited to Todo -> In progress -> Done. But eventually you would be able to add any state flow you want for your entire workspace, or even a specific document.
I’m really excited about this agenda view. Inkami now has a concept of time and each block can be associated with a date. Once that’s done, it shows up in the agenda view.
I’ve been busy these last couple of weeks building out some #productivity features.
Namely journals, tasks, and agendas. I’ll make a proper video explaining them all but here is a quick intro 🧵
#buildinpublic
A small demo with a bit of redesigning and showing how BYOM (bring your own models) works within Inkami. Also demoing the first pass at building preferences and a bit of a hint of kinds of publishing inkami allows.
Sometimes building stuff is just fixing older code. This weekend, I ended up just doing things like:
- Finding and fixing a rare race condition where a document data is lost
- Making selections better
- Making mouse clicks do what you expect them
- Refactoring lots!
#buildinpublic
Publishing 404 page design. A dead end is sometimes lonely and sad. #notfound #buildinpublic
Hard to say exactly where. It’s not one thing usually. Some fail because they are slow or bloated (notion), others because they’re clunky to use (obsidian), or because while they’re well designed, their users outgrow them (iA writer for me). Also what makes it hard to build for this sector.
I have a pretty decent list actually but it’s still evolving. Will post as they start materialising.
What are you using to write and what’s important to you in such a platform?
I built inkami to have a solid data privacy and data portability architecture. I think inkami is doing a pretty good job on that front right now, but it’s a really simple writing platform.
Time to build features that make Inkami into a daily driver.
#buildInPublic
I have an idea, but it’s a trade off between unreliable kuras (non-negotiable) and central server. So, central server it is. However, if it touches our servers, it needs e2e encryption.
Answer: asymmetric crypto. Kuras keep keys (if self hosted) server stores encrypted edits for offline.
Sharing documents across independent kuras is an interesting problem.
How do you do that reliably without storing information on a central server? Couple that with unreliable clients (self-hosted Kuras on, say, laptops). Then, add collaborative editing on top.
Oh! And also, a basic publishing framework is done!
The first post is: writ.inkami.app/@inkami/welc...
#buildinpublic #privacy
5/5 Kura is not just a self-hosting piece. If you host with us instead of self-hosting, we run your workspaces as Kuras.
Inkami.app is still in private beta but we’re excited to launch soon! Please sign up for our wait list if it interests you.
#buildinpublic #privacy #selfhosting
4/5 Using AI? On the Kura.
Whether you use a local LLM or one of the AI services like Claude, OpenAI or Gemini. You can just add an API token and it’s stored on your Kura.
Generating text in your doc? Goes through your Kura.
3/5 Searching your workspace? On the Kura.
We use SQLite’s full text search to index your words on the Kura. When you search your workspace, the request goes directly to your Kura.
2/5 Storing your documents? On the Kura.
Documents are stored both as CRDT binary files and markdown files. It’s duplication, but you always have access to your data whenever you want.
Heck, Kura even comes with a built in server that serves all your markdown files. Just run ‘kura browse’.
One of the main innovations in inkami is its data storage architecture.
Kura is a rust app that uses SQLite and file system to store your workspace. Inkami just routes the browser directly to your Kura. Everything you do on your workspace is done on your Kura.
What does that mean?
1/5
