Google Workspace MCP, Command Line Reference: numbered sign-in steps, plainer prose
Drops the note on the email settings' names before plugins; that history
belongs on the Upgrading page.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop the leading H1 from every page; GitHub already shows the page name
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keryx the service, Lyra the assistant: the wiki follows the rename
Every page says Keryx for the service and the assistant (Lyra by default) for the voice;
links point at wak31415/keryx and src/keryx; Restarting-Jarvis is Restarting-Keryx.
The wake word is still "hey jarvis", the pretrained model's name. Troubleshooting
covers serve refusing until `keryx migrate` has run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: plugins, custom tools, and what landed on main since the last edit
New pages: Custom Tools (writing and checking your own voice tools) and Sharing Custom
Tools (a suggested convention for publishing them; there is no registry). The two worked
examples are rewritten as plugins. Every other page is checked against main: plugins in
place of the retired settings, jarvis plugins / jarvis tools, CLAUDE_CONFIG_DIR, a failed
restart that rings, TRANSCRIPTION_LANGUAGE and CLOCK_FORMAT.
docs: point the remaining paths at the XDG directories
Home, Assumptions, Google, Restarting and the Approval Bridge now name
~/.config/jarvis, JARVIS_HOME for the Google client file, and STATE_DIR
for logs, running-version and the approval socket.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
docs: Google is jarvis auth login gmail and google-workspace, and Codex needs the second
setup-google is gone; the client is set up once from the guide.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
docs: the manual, moved out of the README
The README was 967 lines. The content was good, which was the problem: a front
door that takes twenty minutes to read is not a front door. It keeps what a
reader needs before they decide to install anything — what it is, the
architecture, setup, and how to write your own tools — and everything longer than
that lives here, in full rather than in summary.
Fourteen pages in three groups, which is also how the sidebar reads, grouped by
when you need them rather than by what subsystem they belong to: install and
operate it, decide whether to deploy it, understand one thing deeply.
Two things this wiki deliberately is not. It is not the rulings of record — the
design spec in the repository is, because a wiki is a separate git repository and
none of it arrives with a `git clone`, and the decisions that look like bugs until
you know them have to travel with the code. And it is not a settings reference:
`.env.example` and spec §3.4 already hold that, and a third copy is a third thing
to drift.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JgnEwxB2L2ZqzTgq476MAt