u/Turbulent_Ad6290

Our LLM wiki extension just got a solid reliability release — the interesting bit is the bug we found while reviewing our own toast feature.

Quick context: LLM Wiki is a pi extension that keeps a Markdown vault of everything an agent learns — sources, entities, concepts — with automatic metadata and recall injected into future sessions.

v0.11.3 has the usual stuff (MCP bootstrap for MCP-only clients, layered recall over MCP, gap-snapshot persistence fix), but the one I want to talk about is the stale session context race:

We shipped an "instant completion toast" for background actions. The code read ctx.hasUI/ctx.ui after an await inside the background task. If the user switched sessions or reloaded pi while a long lint was running, that ctx is a stale proxy — property access throws. The catch block then fired a false "task failed" warning and skipped the real success report entirely. Worst case of the exact thing toasts were supposed to fix.

The surrounding code already had a comment warning about this exact hazard in the sibling function — we just didn't mirror it. One-line fix (capture before await), plus a regression test where the ctx getters throw once work is in flight. Test fails on the old code, passes on the new. That's the kind of bug that's invisible in unit tests against fresh ctx objects and only shows up in the real session lifecycle.

Repo: https://github.com/zosmaai/pi-llm-wiki

Anyone else hit stale-context issues with extension APIs that hand you proxied context objects?

Last week I shipped Zosma Router.

Zosma router gives access to Deepseek v4 flash 0731, mimo v2.5, GPT 5.6 Luna & Terra models.

1 month free trial with 100 requests per day.

It’s the primary router for Cowork now. But Ofcourse you can choose any other provider or local AI like I do.

In coming says will add better useful features.

https://github.com/zosmaai/zosma-cowork

pi-llm-wiki v0.11.0 now supports native Open Knowledge Format v0.2.

Highlights:

• Canonical OKF documents for new vaults
• Standard Markdown links and stable citations
• Deterministic indexes and logs
• Legacy and OKF dual-read compatibility
• Shared Pi/MCP knowledge model
• Safer vault-layout migration with no-clobber moves and recovery journals

Install:

  pi install npm:@zosmaai/pi-llm-wiki@0.11.0

For an old .wiki/ layout, preview first:

  node node_modules/@zosmaai/pi-llm-wiki/scripts/migrate-llm-wiki.js \
    /path/to/vault --dry-run

Apply after reviewing:

  node node_modules/@zosmaai/pi-llm-wiki/scripts/migrate-llm-wiki.js \
    /path/to/vault --force

This migrates the directory layout, not legacy page content. Full OKF adoption is incremental: create an OKF vault, re-ingest source material, and explicitly port selected pages. Existing legacy pages remain readable alongside OKF pages.

Always back up first.

GitHub Link -> https://github.com/zosmaai/pi-llm-wiki

Pi Package Link -> https://pi.dev/packages/@zosmaai/pi-llm-wiki

Thanks to everyone who has encouraged me to maintain this project.

As an upgrade, I was planning to introduce the OKF v0.2.

Let me know your thoughts in comments.

Thank you community for all your support so far.

https://github.com/zosmaai/pi-llm-wiki

Powerful AI shouldn't be locked away just for engineers.

That's why we built Zosma Cowork — a desktop AI coworker for knowledge workers, built on top of Pi.

You can ask Zosma Cowork to build a feature for itself. Need a custom Marketing workflow? It writes its own extension and skill, then uses it for your exact task. Software that reshapes itself around how you work.

For a lot of jobs, it replaces pieces of Perplexity, ChatGPT, Claude Code, Claude Cowork, and more — rolled into one tool that runs where your files actually live.

I won't pretend it's a complete replacement for all of them. But now you have a choice: download a free, open-source app, plug in your own models and tools, and keep your data on your machine.

In the age of AI, if you actually care about private AI, this is step one.

⚠️ We're early (beta), so you may hit rough edges. If you do, tell us — report it on our Discord or open a bug/improvement ticket on GitHub. Every report makes it better.

Free. Open-source (MIT). Yours.

https://github.com/zosmaai/zosma-cowork

Discord Server: https://discord.gg/c5vadsv9

What's the first thing you'd hand off to an AI coworker?

First of all I would like to thank the Reddit communication of subReddit PiCodingAgent.

Your feedback helped me make this llm-wiki better.

It was broken for a while and honest feedback from this community gave me the motivation to fix those issues.

It’s working good for me as well.

I’ve shipped few updates on how the wiki recall, retro and observations happen.

Let me know your throughs.

Here is the repo link.

https://github.com/zosmaai/pi-llm-wiki.

https://pi.dev/packages/@zosmaai/pi-llm-wiki

You can also checkout other OpenSource projects we are working on.

Why Zosma Cowork?

🌟 Built on pi

Zosma Cowork is a desktop application built on pi — the minimal, language-agnostic coding agent harness. pi's philosophy of simplicity and composability carries directly into your desktop experience. Every pi extension works out of the box, with zero wrappers or adapters.

🆓 Free & Open Source

Zosma Cowork is 100% free and open-source (MIT). Bring your own API key, use an existing subscription (Claude, ChatGPT, Copilot), or run local models — you stay in control.

🧩 Full pi Extension Ecosystem

The pi ecosystem includes hundreds of extensions, skills, tools, prompts, and themes — all compatible with Zosma Cowork. Plug them into your ~/.zosmaai/cowork/ directory and they just work. No wrapping, no porting, no lock-in.

link: https://www.zosma.ai/zosma-cowork

Features

• Node.js agent sidecar — The pi-mono TypeScript SDK runs in a managed sidecar process for full agent capabilities (extensions, tools, providers)
• Thin Tauri relay — The Rust layer is a minimal IPC bridge between React and the sidecar, keeping the native desktop shell lightweight
• pi extension ecosystem — Compatible with pi extensions via DefaultResourceLoader — skills, tools, and prompts auto-discovered from ~/.zosmaai/cowork/
• Multi-turn sessions — Full conversation continuity with persistent session history
• Streaming responses — See the agent think, write, and call tools in real-time
• Thinking blocks — Expandable reasoning from the model
• Tool call timeline — Live bash/edit/write tool calls with args and results
• Session management — Persistent chat sessions saved to ~/.zosmaai/cowork/
• Light & dark mode — Warm cream light mode, warm charcoal dark mode
• Keyboard shortcuts — Cmd/Ctrl+Shift+K to focus, Cmd/Ctrl+N for new session
• Abort & steering — Stop a running agent mid-turn, send follow-up steering messages
• Claude-inspired UI — 3-column layout with sidebar, workspace, and info panel

Recenly I started using this pi extention for maintaining the knowledge for personal and project specific Obsedian compatible wiki. I also use memex and pi-observational-memory.

So far I've found this useful. What other extensions have you guys tried?

https://github.com/zosmaai/pi-llm-wiki

https://pi.dev/packages/@zosmaai/pi-llm-wiki

This is built by the same people that build the Zosma Cowork. I was talking about the other day.

I found this desktop gui on top of pi coding agent

https://github.com/zosmaai/zosma-cowork

Has anyone tried this?

So far it’s working ok for me.

I want to recommend this to my colleague. Anyone else using it?