+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-mcp, pikuri-subagents, pikuri-vectordb, and pikuri-assistant 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-assistant ships the demo +bin/pikuri-assistant+ binary on top of pikuri-core + pikuri-skills + pikuri-mcp: an interactive chat agent the user hand-edits to declare a +Pikuri::Mcp::Registry+ of MCP servers. The +Pikuri.prompt+ search path picks up this gem's +prompts/pikuri-assistant.txt+ automatically on require — same multi-gem prompt-dir pattern as pikuri-code.

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-extractors plugs additional document formats into pikuri-core's +Pikuri::Extractor+ registry. The bundled +Pikuri::Extractors::DOCUMENTS+ extractor converts office documents (DOCX, ODT, XLSX, legacy XLS, PPTX, EPUB, RTF) to Markdown by piping the bytes through pandoc / markitdown — preferably inside a one-shot, networkless, locally-built docker container (the untrusted bytes never touch the host filesystem or network), falling back to a host-installed pandoc / markitdown CLI when docker is absent. Registration is explicit — +Pikuri::Extractors::DOCUMENTS.register+ — so requiring the gem changes nothing by itself; the host script picks which extractors it wires in.

pikuri-mcp adds Model Context Protocol support to pikuri-core agents: a +Pikuri::Mcp::Registry+ for declaring stdio + HTTP MCP servers, the +Pikuri::Mcp::Servers+ runtime that spawns them, a +Pikuri::Mcp::Synthesizer+ that LLM-fills missing server descriptions, a +Pikuri::Mcp::Verifier+ that screens server surfaces for prompt-injection patterns before any tool is advertised to the LLM, and a +Pikuri::Mcp::Extension+ that wires everything into a +Pikuri::Agent+ via +c.add_extension(...)+ in the +Agent.new+ block.

pikuri-memory gives a pikuri-core agent durable, long-lived memory: facts about the user and their work that persist across conversations. It wires a +recall+ tool plus an automatic per-turn prefetch onto an agent via +c.add_extension Pikuri::Memory::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-vectordb+. Recall is automatic and synchronous (embed + vector search, milliseconds); capture is automatic and asynchronous (an off-the-interaction-path extraction queue), so a turn never blocks on "what should I remember?". Storage is mem0 (https://github.com/mem0ai/mem0) reached over a thin Faraday HTTP client — the append-only +add+ / read-time +search+ model. Only the *user's own words* are fed to extraction (a write-side hygiene rule that structurally drops system/assistant/tool-sourced junk), and recalled context enters the chat as a +:system+ message so it is provenance-tagged and excluded from the next extraction pass. This release ships the Ruby client + extension + tool against a *bring-your-own* mem0 endpoint; a self-managed mem0 sidecar supervisor (the +ChromaServer+-style docker pattern) is a follow-on.

pikuri-pdf plugs PDF → text extraction into pikuri-core's +Pikuri::Extractor+ registry. The bundled +Pikuri::Extractors::PDF+ extractor wraps the pure-Ruby pdf-reader gem and extracts lazily: paged reads (the +read+ tool's windows) parse only the pages the window needs, so the first page of a 500-page PDF never pays for the other 499. Shipped separately from pikuri-core so the core's dependency tree stays minimal and auditable: pdf-reader and its transitive deps (Ascii85, afm, hashery, ruby-rc4, ttfunk) ride along only for hosts that opt into PDF support. Registration is explicit — +Pikuri::Extractors::PDF.register+ — so requiring the gem changes nothing by itself; the host script picks which extractors it wires in. One registration extends the +read+ tool, +web_scrape+, and the pikuri-vectordb indexer simultaneously.

pikuri-skills implements the Agent Skills standard (agentskills.io) for pikuri-core agents: a +Pikuri::Skill::Catalog+ that discovers skill folders under .pikuri/skills, .claude/skills, and .agents/skills; a +Pikuri::Skill::SkillTool+ that loads a skill's body on demand; and a +Pikuri::Skill::Extension+ that wires both into a +Pikuri::Agent+ via +c.add_extension(...)+ in the +Agent.new+ block.

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.

pikuri-tasks gives a pikuri-core agent an in-memory task list it can use to plan and track multi-step work. A +Pikuri::Tasks::List+ holds the per-Agent state; four tools (+task_create+, +task_in_progress+, +task_completed+, +task_delete+) mutate it via content-as-identifier (no item IDs to hallucinate). +Pikuri::Tasks::Extension+ wires the list and tools onto an +Pikuri::Agent+ via +c.add_extension(...)+ inside the +Agent.new+ block. The list lives in process memory only — nothing is written to disk. Sub-agents do not inherit the parent's list (consistent with the "sub-agents do not inherit extensions" rule).

pikuri-vectordb gives a pikuri-core agent a +vectordb_search+ tool over a local document corpus — agentic search, the agent decides when to retrieve. Ships a swappable backend (a pure-Ruby +Backend::InMemory+ for teaching, plus thin +Backend::Qdrant+ / +Backend::Chroma+ HTTP clients for persistence — Qdrant recommended), a chunker, an embedder wrapper over +RubyLLM.embed+, and an optional +Reranker::LlamaServer+ that speaks +/v1/rerank+ against a cross-encoder model. Text extraction goes through +Pikuri::FileType.read_as_text+ in pikuri-core, which handles plain text / Markdown / PDF; HTML extraction is a deferred follow-up. Hosts wire the feature via +c.add_extension Pikuri::VectorDb::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-skills+. The bundled +Pikuri::VectorDb::LIBRARIAN+ persona is the privilege-separated sub-agent counterpart for hosts that want recall to flow through a child rather than the parent's context. Three model endpoints in the full setup — chat (via ruby_llm), an embedder (via +RubyLLM.embed+), and an optional reranker (HTTP +/v1/rerank+). A single +llama-server+ in router mode serves all three by default, loading each cached GGUF on demand; see the gem's README for details.

pikuri-workspace adds "operate on a directory tree" to pikuri-core agents: the +Pikuri::Workspace::Filesystem+ class that scopes filesystem access to an anchor + explicit readable / writable prefix lists (with optional ephemeral temp playground), the +Pikuri::Workspace::Confirmer+ seam (+AUTO_APPROVE+ + +TERMINAL+) for user-state mutations, and five tools wired to those seams: +Pikuri::Workspace::Read+, +Pikuri::Workspace::Write+, +Pikuri::Workspace::Edit+, +Pikuri::Workspace::Grep+, and +Pikuri::Workspace::Glob+. Self-contained — no shell execution; +Pikuri::Code::Bash+ ships in pikuri-code on top of these.