File-aware local AI
RAG is a major part of the plan. I want Ghost to use my documents, notes, project files, and knowledge base as context instead of forcing me to paste everything manually.
I’m building Ghost for me. It is a local-first AI workspace running on my own hardware, built to explore what happens when chat, agents, local models, voice, files, remote access, and home control start becoming one personal operating layer.
I got pulled into local AI because the idea is too interesting to ignore. The problem is that most local AI setups feel like a pile of terminals, model names, config files, scripts, and “almost working” experiments. I wanted something that felt like an actual product. Something private, fast enough, flexible, and shaped around how I actually work.
This is the shape I’m chasing. Some of it exists now, some of it is rough, and some of it is planned future work.
RAG is a major part of the plan. I want Ghost to use my documents, notes, project files, and knowledge base as context instead of forcing me to paste everything manually.
Focused helpers for product thinking, research, coding, writing, planning, review, and cleaning up messy ideas.
Installed models, defaults, runability, reply styles, and practical model choices in one place.
Bigger models, image work, file indexing, and deep research need real compute. Ghost is being designed around that reality.
The future companion app should connect back to my server so I can chat, dictate, or voice chat with my own local LLM away from home.
Talk to it, dictate into it, and use spoken replies when typing is not the right interaction.
Image directions, icon concepts, landing page ideas, UI drafts, and creative exploration all belong in the same workspace.
The point is not “never use cloud.” The point is ownership, privacy, and choosing when work leaves my machines.
These are real alpha screens from the desktop app. Rough edges are expected. That is kind of the point.
Editing a specialist agent in the current alpha build. Focused helpers are a big part of the direction.
The main chat surface, built around local models, focused work, and a dark UI that does not feel like a web wrapper.
Attach files directly in chat and use them as context. Here I dropped AGENTS.md and had Ghost summarize my agent notes — project scope, working rules, and what is in focus right now.
Installed local models, reply tuning, and runability signals. Still alpha, but the shape is there.
Current settings for memory, default models, voice input, and performance behavior.
Early voice session testing with open mic, dictation, and spoken replies.
Longer term, the idea gets bigger: home automation, cameras, sensors, local alerts, routines, and a private command layer for my environment. Not cloud-first. Not some rented brain in the middle. My hardware, my home, my AI layer.
This is a passion project in active development. It is not a product launch, not a public beta, and not something I’m asking anyone to buy.
Ghost is being built as a real desktop app, not just a mockup. The current build is focused on Mac and Linux first, with the architecture slowly growing around local models, routing, agents, voice, and files.
I’m using AI heavily to build it, but the direction, taste, product calls, testing, and scope control are mine.
Local AI is not magic. Bigger models, image generation, RAG, voice, and deep research all need real compute. Trying to get my wife on board with some new hardware for Ghost. 🙂 👻
I’m not close to even thinking about a public release. Right now this is my baby, my lab, and my excuse to learn by building.
I’m sharing it because I think the direction is cool. That’s it. No buy button, no waitlist, no startup theater.
A dark, local-first AI workspace I’m building on my own hardware. Part product idea, part lab, part long-term bet on private AI.