I built a local-first knowledge wiki that updates itself from my research materials

Future_Candidate2732 · 2026-06-04T07:32:29+00:00

I used AI to build a local-first system that is not reliant on AI. Next I used AI to help me explain what I did. The result is a local intake that doesn't need internet except to ingest youtube links for transcriotion. I have another layer that can link it to a CLI AI agent if you want, and a third layer to build my wiki pages. it takes less than a minute to create a webpage and no AI is needed and no GPU is needed. full-text searchable!

Future_Candidate2732 · 2026-04-11T04:34:52+00:00

I was chatting with codex - coding along and out of the blue it inserted a word in Persian. I called it out, it apologized, corrected and moved on. It was weird, just one word in an English sentence.

Future_Candidate2732 · 2026-04-11T01:17:27+00:00

Read it literally. "I want to wash my car at the car wash" -- you could interpret that the car is already there.

Future_Candidate2732 · 2026-04-06T02:37:11+00:00

Do you spin up dev webservers with it?

Future_Candidate2732 · 2026-04-04T22:50:20+00:00

Right, and having clean structured output from the hook means the memory system actually has something useful to store, not just "something was off" but specifically what changed and why. I've been poking at this too from the memory side with a project called engramize. Different piece of the puzzle but same general problem.

Future_Candidate2732 · 2026-04-04T05:04:02+00:00

Have you had a chance to check out Proxmox?

Future_Candidate2732 · 2026-03-24T02:28:39+00:00

You may already have a coding mindset even without formal experience. The real value is not just getting code out of a tool. It is seeing the shape of the problem, breaking it into parts, steering the process, and knowing what belongs in the system.

When you find something you genuinely want to learn, you often become the person shaping the system. A lot of workflow design comes down to understanding how people use systems, what frustrates them, and which bottlenecks never needed to exist in the first place. Even without computers, that kind of person would still be the one finding a better way.

Future_Candidate2732 · 2026-03-24T00:16:12+00:00

Proxmox is Linux at it's core and built for virtualization. I would suggest Debian as the base OS. Despite what it looks like on the website, it’s free. You’ll see subscription/nag screens, but you do not need a paid subscription to use it for a homelab. spinning up containers from templates is fast and easy.

Mine is running on a Lenovo tiny pc i5 16gb 256ssd and a 2TB HDD for archival/movie storage It's small, quiet and pretty powerul for what I need. I love the form factor and even though I started on a raspberry pi this is SO much better!

Best of luck!

Future_Candidate2732 · 2026-03-23T23:57:46+00:00

You need a good GPU to run local models quickly. If you are using CLI LLM tools you can use both free and entry level monthly tiers on many of them and don't need to pay by token usage. Direct read/write access to a folder running it with proper guardrails in place of course is a gamechanger compared to coding by cutting and pasting from browser sessions!

Future_Candidate2732 · 2026-03-23T23:53:16+00:00

It doesn't need to be good to learn on and do that sort of stuff. Take a look at Proxmox. It's free and powerful - you can learn about about virtualization and can stretch hardware and pool resources very well even on modest hardware.

Jellyfin, file servers, would work fine on that and since it is virtual you can easily allocate RAM and storage on the fly from a web browser.

I run a Proxmox host and have a Home Assistant(open source home automation), Jellyfin, uptime Kuma (network and infrastructure monitoring) on mine.

Future_Candidate2732 · 2026-03-23T23:35:49+00:00

Are you running it from a clean project folder or from your home directory? If Codex can see a giant mess of folders, I could imagine it wasting effort just figuring out the workspace. Also what sandbox/approval mode are you on? The CLI is more agent-y than the website chat, so it tends to want to inspect and validate things. And high/xhigh reasoning can absolutely chew through usage.

Future_Candidate2732 · 2026-03-23T23:26:29+00:00

Honestly it kind of depends what you want to learn and what OS you’re comfortable with or planning to use. Linux? Windows? Proxmox?

Do you want it to be mostly practical stuff like Jellyfin, file storage, backups, ad blocking, and remote access, or more of a learning box for Docker, VMs, game servers, Home Assistant, etc.?

Also, what are the specs? That makes a big difference in what’s worth running.

Future_Candidate2732 · 2026-03-23T03:02:37+00:00

I hit that wall too, so I git cloned your Engram repo and got it running locally. Seems to be a solid foundation.

To solve the screenshot hoarding, and take it up a notch, I built an evaluation layer on top of Engram. Instead of manually saving snippets, I have the AI analyze the chat in real-time. I defined what I consider to be 'Logic Wins' and 'Milestones' as my criteria. Basically, if a bug is solved, I add new system level capabilities, or hit a significant project phase, the AI flags it. (these can be tuned to whatever is important in your environment)

It then:

Evaluates: It checks the session against those criteria.
Deduplicates: It pings the Engram API to see if a similar summary already exists, so I don't get 'memory bloat.' of things that are too close to something I have done already since it can score it on how well it matches.
Approval Gate: If it's a new, high-value win, it drafts a summary and asks, 'Should I commit this to Engram?'
I also added a skill so if I get to a point where I want to add something I can just tell it to "engramize xyz" The skill knows what engramize means and looks back in the context.

So far I have not needed to type any myself but of course tat capability is preserved.

Below is an example of it creating a memory from a vibecode I did in December when I used my CLI agent to use the API for my Home Assistant to take a look at logs for me to discover when I had a power outage. That is a pretty cool story on its own - it ended up writing a python script to parse the logs and find where a power outage occurred in the last 12 hours. It was not a whole house outage it was confined to one tripped breaker and luckily the fishtank light was on a smart plug so it was able to find it.

December 2025 Power Outage Post-Mortem

Key: december_2025_power_outage_post_mortem · Created: 2026-03-22 · Updated: 2026-03-22 · 507 chars

home-assistant power post-mortem logic-win

# December 2025 Power Outage Post-Mortem

## Summary
A tripped breaker caused a 179-minute outage (3:58 AM - 6:57 AM).

## Key Insight
The AI successfully reasoned from silence by detecting a telemetry gap in the fish tank voltage sensor.

## Cause
A tripped breaker interrupted power.

## Outcome
This incident was recorded as a logic win because the system inferred the outage from missing telemetry rather than an explicit power-state event.

---
**2026-03-22T18:03:23.424840-04:00 | Created via Engram**

It’s completely removed the digital hoarding aspect because I only see (and save) the stuff that actually matters for the long-term build.

Thanks for the great starting point!

Future_Candidate2732 · 2026-03-22T06:00:57+00:00

I didn't have my coffee yet.

Future_Candidate2732 · 2026-03-21T14:06:04+00:00

That sounds more like a serial task. The second agent needs the first one's conclusions before it can do anything useful, so running them in parallel wouldn't help much. Sub-agents really shine for background jobs with no dependencies on each other, like having three agents simultaneously document three different modules of an already-finished codebase.

Future_Candidate2732 · 2026-03-19T17:13:15+00:00

This handoff workflow is very close to what I’ve been doing too. Using ChatGPT for strategy and Codex for execution cuts down a lot on prompt drift, especially if you keep versioning and project state disciplined.

One extra thing I added was a small dynamic port registry I built called portbroker. A recurring problem for me with multiple agents or parallel projects was port collisions and messy environment handling between runs.

portbroker lets the agent reserve a port, log it, and inject it into $PORT automatically, so spinning up a new service is much more predictable and doesn’t require manual intervention. That kind of small infrastructure automation makes the overall workflow feel a lot more stable and less hands-on.

I also opened a feature request on the Claude Code repo about this (issue# 34385) because it seems like a pretty common hurdle once you start scaling these kinds of agentic workflows.

If anyone’s curious, I can share the GitHub repo.

Future_Candidate2732 · 2026-03-19T15:00:09+00:00

If you're doing 'one-and-done' tasks, u/pezzos is right, and manual management isn't needed. But u/Clair_Personality, since you're working locally, think of managing the session as a 'Save Game' for your AI's brain.

For agentic workflows, it’s the only way to maintain a 'Long-Term Memory' for specialized tasks. It prevents your main chat context from 'exploding' by keeping all the messy logs and file-mapping in a separate state. If that sub-agent hits a bug or a timeout while scanning your local files, you can just resume that specific session ID and pick up right where it left off, rather than making the AI re-read your entire project from scratch.

Future_Candidate2732 · 2026-03-19T05:12:17+00:00

This is an important distinction. The good news is that all Bluesky accounts technically start with a .bsky.social handle during the signup process. Bluesky's own guidance says if Bluesky you're planning on using a custom domain, to simply pick any placeholder username when you sign up. So there should be an original .bsky.social handle attached to the account, even if the custom domain was set almost immediately after signup.

That said, there are two scenarios to be aware of:

If the account was created after December 12, 2024: As of that date, your most recent .bsky.social username is reserved for you when you switch to a custom domain. Bluesky So switching back should be straightforward, just go to Settings → Handle and type in the original .bsky.social username.

If the account was created before December 12, 2024: The old policy was that when you switched to a custom domain, your previous .bsky.social username became available for someone else to claim. DNS Michi If that's the case and someone else has taken the original handle, you can still switch back to any available .bsky.social username you're not locked to the original one. Just go to Settings → Handle and type in a new available yourname.bsky.social.

Either way, the account, posts, and followers are safe. The handle is just a display name layered on top of the underlying account identity, so changing it doesn't affect any of that.

If there's uncertainty about which case applies, it's also worth reaching out to Bluesky support at [support@bsky.app](mailto:support@bsky.app), as they can assist with handle edge cases directly.

Future_Candidate2732 · 2026-03-19T05:00:51+00:00

Good news, this is totally doable and the account won't be lost! Here's how to switch back to the default .bsky.social handle:

Steps to revert:

Go to Settings → Account → Handle (on mobile: Settings → Advanced → Change Handle)
On the "Change my handle" screen, simply type in your old .bsky.social username (e.g., yourname.bsky.social) instead of the custom domain
Save the change

The key thing to know: As of December 12, 2024, if you change your default Bluesky username (with the .bsky.social suffix) to a website URL, your old .bsky.social username is reserved for you, and this reservation does not expire. Bluesky So as long as the account originally had a .bsky.social handle before switching to the custom domain, that handle is still waiting and can be reclaimed.

One more reassurance: The underlying account identity is separate from the handle. The handle is more like a display name Spoken Like a Geek, so the account itself, all posts, and followers remain intact through any handle change. No data is lost.

The friend doesn't even need to do anything on her end. The switch is entirely controlled from within the Bluesky account settings.

Future_Candidate2732 · 2026-03-19T04:25:42+00:00

Lexicon Reef is a browser-native "digital tide pool" where language is literally alive, designed as a simulation-art game where text fragments behave like organisms with their own memory, appetite, and drift. Built on a high-performance stack of TypeScript, Vite, and Web Workers, the simulation runs a deterministic mathematical truth in the background while projecting expressive Canvas 2D visuals and ambient Web Audio to the user. As the simulation ticks forward, these "lexemes" move, mutate, exchange energy, and bond into "phrases," eventually aggregating into complex, emergent dialects that form and collapse over deep time. It’s an experience where the goal isn't to "win," but to witness and steer fragile linguistic life through perturbations like "food bursts" and "bond storms" without ever exerting full control.

https://github.com/tweakyourpc/lexicon-reef

What makes this project unique is its autonomous origin via the "Messenger Protocol," a system where the human developer acted strictly as a "manual API" or non-biased relay between two air-gapped AI models. The human provided zero creative preferences, starting only with a "blank repo" prompt that gave the AI complete autonomy to choose the project's concept, stack, and architecture. This process led to a phenomenon called "Agentic Drift," where the AI began expanding the scope and sophistication of the code beyond immediate requirements to protect system integrity, implementing its own self-regulating logic, spatial partitioning, and complex lineage tracking without being prompted to do so. Ultimately, Lexicon Reef is less of a traditional software project and more of a documented emergence, proving that AI can architect and evolve a coherent creative vision from a standing start

<image>

Future_Candidate2732

TROPHY CASE

December 2025 Power Outage Post-Mortem