Mirror of the public Nokido wiki (source of truth: https://github.com/Nokido-labs/nokido/wiki/16-FAQ). Edits belong there.
Updated: 2026-08-21
Frequently asked questions. Also see docs/FAQ.md (github.com) for the
original short FAQ shipped with the codebase.
An Autonomous, Local-First AI Operating System with Neuro-Symbolic
Governance. It orchestrates many specialized brains (LLMs, embedders,
SNN, GOAP, AMI planner), owns its memory (persistent RAG), filters
every cloud call (Semantic Firewall + Sovereign Membrane), and stays
local-first by default.
Short version : a high-tech hospital where every brain has a
specialty, every exchange is filtered, and the whole thing remembers
everything 24/7 on your machine. See MANIFESTO.md (github.com)
for the full philosophy.
It forges things β code, plans, decisions. Also a nod to Geordi La Forge
(Star Trek TNG) β the chief engineer who makes the impossible work with
local resources.
user (@user). Solo project, open to
contributors.
AGPLv3-or-later. If you host Nokido as a service over the network,
you must publish your modifications. Read CONTRIBUTING.md (github.com)
for the rationale.
It's alpha. The alpha branch is active development, beta is
release-prep, main will track stable releases. Pin to a tag for
production-like usage.
Minimum :
Recommended :
ml extras with torch).Tested on an AMD Ryzen 7 8700G + Radeon 780M iGPU (consumer APU). All
benchmarks in the README come from that setup.
Several reasons :
X | None, dict[K, V]).tomllib in stdlib.faiss-cpu wheels target 3.12.Python 3.13 and 3.14 also work β pyproject.toml lists all three.
No. The Docker setup gets you running in 5 minutes. You interact via
your MCP client (Claude Code, Gemini CLI, Codex CLI, Cline) or via the
TUI (nokido-cli).
To extend Nokido (new modules, custom skills), yes β Python is the
primary language.
Ollama is a local LLM runtime β one process, one or more model
files, an OpenAI-compatible API. Nokido uses Ollama as one of its
29 LLM providers.
Nokido adds :
Think of Ollama as the gas station and Nokido as the car.
The big inversion : in Nokido the hub is the orchestrator, the LLM
is a transient worker. LangChain / AutoGPT make the LLM the
orchestrator (which re-sends the full chain-of-thought each turn).
Measured outcome : Nokido consumes 5-15Γ fewer tokens for the same
end result. See MANIFESTO Β§3.5.
Nokido also has things they don't : Semantic Firewall, Sovereign
Membrane, AMI cognitive stack, 6-ring RBAC, neuro-symbolic verdict
path. The closest comparison is OpenHands (formerly OpenDevin), but
even there Nokido differs : sovereignty + memory + governance.
For most tasks, auto routing : the cascade picks for you (local
first, free cloud next, paid only if you've enabled it). To force :
qwen2.5-coder:32b via Ollama (local), or groq (freegemini_pro (free tier 1k/month), orcohere_command_r_plus.gemini_flash (1M context, free).gemini_flash again, or cohere_command_r_plusllamacpp_local (qwen2.5-coder + --jinja), orollama.No. The local tier (Ollama, llama.cpp, LM Studio, brain_worker)
covers most workflows. Cloud is a quality boost when local isn't
enough.
Two layers automatically applied :
The cloud provider sees [host:xxx] and [path:yyy], not your real
data. The hub restores aliases in the response transparently.
You can also disable cloud entirely : delete the API keys from the
vault, and the cascade will only use local providers.
See 05 β LLM providers Β§ Adding a custom provider.
The most likely cause is quota. Check :
http://127.0.0.1:8766/admin/providers
If the percentage is red, the provider is skipped by the cascade until
the quota resets (start of next month/day).
In a machine-wide OS-encrypted vault :
CRYPTPROTECT_LOCAL_MACHINE.The vault file (data/machine_vault.dat) is encrypted with the machine
key. A network attacker who pulls the file cannot decrypt it without
local access.
If they have local access (e.g. compromised user account), they have
the same threat profile as a .env on disk. The vault helps against
passive leak (backups, git push, file sync), not against active
compromise.
Don't. The hub binds 127.0.0.1 by default. To access from another
machine, use Tailscale or WireGuard. Do not change the bind to
0.0.0.0.
Private disclosure : Security tab β Report a vulnerability. See
SECURITY.md (github.com). We aim for 72-hour acknowledgement.
No. The code is AGPLv3 β fully readable, fully auditable. The hub
binds localhost, has no telemetry, no "phone home" pings. Pre-commit
hooks (Gitleaks + forge_secret_guard) prevent accidental secret
inclusion.
If you want extra paranoia : build locally, audit app/forge_*.py,
inspect network_log for outbound calls.
Default fresh install : ~3k chunks (seed data β lessons, configs, ADRs).
After a few weeks of active use : 50-100k. The reference dev setup is
~531k chunks (warm tier).
Yes :
rm RAG/embeddings.db
python tools/forge_db_bootstrap.py # re-import baseline
You lose all learned lessons and indexed content.
Three ways :
rag tool with action=search, topic=<query>.http://127.0.0.1:8766/forge/rag.query tool with FTS5 syntax.Yes. tools/forge_db_seed_export.py dumps tables to JSONL with
schema. Useful for backups and cross-machine sync.
The Model Context Protocol β Anthropic's open standard (2024) for
client-LLM tool interaction. Nokido implements MCP 2025-03-26.
Tested : Claude Desktop, Claude Code, Gemini CLI, Codex CLI, Cline (VS
Code), MCP Inspector, custom HTTP clients. Any MCP-compatible client
should work β see 04 β MCP clients setup.
Yes. Speak JSON-RPC 2.0 over HTTP or STDIO with the schema from
06 β Hub API reference. 25 tools available.
cd Nokido
git pull
# Docker
docker compose -f docker/nokido/docker-compose.yml build
# Native
EXTRAS=$YOUR_PROFILE bash install.sh
Critical paths to back up :
RAG/embeddings.db β the memory.data/machine_vault.dat β vault (Windows).Nokido.env β config (no secrets).seed/*.jsonl β bootstrap data.logs/lessons_learned.md β human-readable lessons trace.tar czf laforge-backup-$(date +%F).tar.gz \
RAG/embeddings.db data/machine_vault.dat \
Nokido.env seed/ logs/lessons_learned.md
The cascade is designed to keep cost minimal β local first, free next.
Yes. Don't launch the TUI ; just run laforge-hub (or the Docker
compose). All functionality is available via HTTP MCP.
Yes β change the port mapping. The hub takes LAFORGE_HUB_PORT env
var. Each instance needs its own RAG/, data/, logs/, sandbox/
directories.
app/forge_mcp_registry.py::ToolRegistry.tools/hub_middleware.py::_ALLOWED_TOOLS.pytest tests/test_forge_mcp_registry.py.See docs/skills/nokido/SKILL.md (github.com). Skills are
markdown files describing capabilities. The skill MCP tool loads them
into the RAG and exposes them to agents.
pytest tests/ # all
pytest tests/ -m unit # fast tests only
pytest tests/ -m security # security suite
pytest tests/test_forge_scorecard.py # one file
CI matrix : Ubuntu + macOS + Windows. See
.github/workflows/ci.yml.
GitHub : https://github.com/Nokido-labs/nokido/issues. Use the Bug
report or Feature request template. For security : private email
(see above).
See MANIFESTO Β§9 and
13 β Hardware roadmap. Summary :
Not in the foreseeable future. The whole point of Nokido is local
sovereignty. A SaaS Nokido would be self-contradictory.
Apple Silicon : already works (M1/M2/M3) β CoreML backend for
brain_worker, Metal for torch. Windows ARM : not tested ; PRs welcome.
Yes : bash install.sh on macOS works natively. See 01 β Installation
Β§ macOS.
Yes β but vendor-neutrally, via litellm. If litellm supports it,
Nokido does (add the spec in forge_provider_specs.py). If a provider
needs a custom client (Anthropic SDK, mistral_commonβ¦), file an issue.
Public release will set up GitHub Sponsors. Until then, contributing
PRs is the best way to support the project.
@software{nokido_2026,
author = {user},
title = {Nokido: An Autonomous, Local-First AI Operating System
with Neuro-Symbolic Governance},
year = 2026,
url = {https://github.com/Nokido-labs/nokido}
}
Replace the URL with the canonical citation URL once a release is
tagged.
Wiki: 04-MCP-Clients-Setup
Wiki: 06-Hub-API-Reference
Wiki: 08-Vault-and-Secrets
Wiki: 13-Hardware-Roadmap