+pikuri+ is the convenience bundle for the pikuri AI-assistant toolkit. It ships no Ruby code of its own beyond a tiny entry file that +require+'s each sibling gem; +gem install pikuri+ pulls in pikuri-core, pikuri-extractors, pikuri-pdf, pikuri-skills, pikuri-tasks, pikuri-memory, pikuri-workspace, pikuri-code, pikuri-lsp, pikuri-mcp, pikuri-subagents, pikuri-vectordb, pikuri-assistant, and pikuri-os in one shot, and +require 'pikuri'+ boots all of them. Privacy-conscious users who want a minimal dependency tree to audit should install +pikuri-core+ directly and opt into the extension gems they actually need — same +bundle add+ pattern Rails users have always had. See each pikuri-* gem's README for its individual surface.

pikuri-os is the OS-integration layer for pikuri and the home of the +bin/pikuri-os+ demo: a single, local, network-severed agent that understands and operates the host OS (answer questions about the machine, find and open files, read logs and explain errors, advise on configuration). It is the federation's privacy- first +@os+ member shipped standalone — no egress, no MCP, no cloud. The gem holds the OS-specific surface (a localsearch-backed content-search tool, a single-file +MACHINE.md+ resident memory, and boot-time machine grounding) on top of pikuri-core's Agent + Tool framework, pikuri-workspace's file tools, and pikuri-code's Bash + sandbox. It deliberately does NOT depend on pikuri-mcp/-memory/-vectordb: severing those keeps the no-egress, "small enough to audit" posture honest. See +ideas/pikuri-os.md+ in the repo for the full design.