+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-code adds the shell-and-dev-loop layer on top of pikuri-workspace's filesystem tools: a +Pikuri::Code::Bash+ that runs commands via the +Pikuri::Subprocess+ chokepoint with +Confirmer+ gating (optionally wrapped in a +Pikuri::Code::Bash::Sandbox::Bubblewrap+ filesystem sandbox), plus the demo +bin/pikuri-code+ binary that wires file + shell + web tools into an interactive coding agent rooted at the current working directory. The +Pikuri.prompt+ search path picks up this gem's +prompts/coding-system-prompt.txt+ automatically on require.

pikuri-lsp lets a pikuri agent ask a real language server the questions grep cannot answer: where is this defined, who calls it, what does it inherit from. It speaks LSP over a long-lived stdio child (+Pikuri::Lsp::Connection+ owns the JSON-RPC framing, the id demux and the reply to server-initiated requests) and models coordinates once, at the wire boundary, in +Pikuri::Lsp::Position+ / +Range+ / +Location+. Read-only by construction: no formatting, no code actions, no rename, no workspace edits. It reads what the server says and reports it.

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.

pikuri-subagents owns the sub-agent (delegation) feature top to bottom: the +Pikuri::SubAgent::SubAgentTool+ class (exposed to the LLM as the +agent+ tool), the +Persona+ record, the +Extension+ that wires it onto an agent, and the bundled +Pikuri::SubAgent::RESEARCHER+ persona (network-read only). Hosts that want sub-agents add this gem as a runtime dep and call +c.add_extension Pikuri::SubAgent::Extension.new(personas: [...])+ inside their +Agent.new+ block — same opt-in shape as +pikuri-skills+ / +pikuri-mcp+. Also ships +bin/pikuri-minions+ as a fan-out delegation demo.