Kotoba

Where to start

What Kotoba isWho she is and where she runs, in one page
InstallingOne package, two commands
First runA key, a model, her first words
The approval gateHow she asks before she acts
The two voice modesLocal voice, or the agent tunnel
The soul fileChange who she is
RoadmapWhat grows next, and what was cut on purpose

Or a section

↑↓ move openesc close124 pages

Documentation

13 sections and 124 pages, from the first install to the architecture underneath. Start at the top if she is new to you, or press Ctrl K anywhere and asktap the search leaf above and ask. What comes next is drawn as a branch on the roadmap.

1Start

  1. What Kotoba is
  2. Requirements
  3. Installing
  4. First run
  5. kotoba doctor
  6. Installing from a clone
  7. Troubleshooting the first hour

2The agent

  1. The two modes
  2. How a turn works
  3. Every tool she has
  4. Core tools
  5. Web: search and reading a page
  6. Memory
  7. Files
  8. Terminal and code
  9. Reminders
  10. Reports
  11. Subagents
  12. The browser, and typing a password into it
  13. Skills
  14. MCP servers
  15. Discord tools

3Voice and avatar

  1. What the voice costs
  2. The two voice modes
  3. The two speaking engines
  4. Audio tags, and the face they pick
  5. The voice socket
  6. What she never says aloud
  7. The Live2D model
  8. Expressions: how an emotion becomes a face
  9. Lip sync, and finding her face

4Security

  1. The security model
  2. The approval gate
  3. Dangerous commands
  4. The sandbox setting
  5. execute_code
  6. Secrets
  7. The web gate
  8. What leaves your machine
  9. Fetching and third-party content
  10. Reporting a vulnerability

5Discord

  1. Kotoba on Discord
  2. Setting her up on Discord
  3. Installing, the token, and the settings
  4. When she answers, and what she writes
  5. The permission model
  6. Changing the server
  7. Voice in a room
  8. What she remembers about people
  9. Honest limits
  10. When she does not answer

6Configuration and operations

  1. The settings reference
  2. Environment variables
  3. Providers, models and keys
  4. Where everything lives
  5. The files library
  6. Running it for real
  7. Backups, and moving to another machine
  8. Upgrading
  9. Logs and diagnosis

7The web app

  1. First run in the browser
  2. Signing in
  3. The main screen
  4. The transcript
  5. The approval card
  6. Files
  7. The Terminal panel
  8. Reports
  9. Settings
  10. The plan and the helpers
  11. Sessions and history
  12. The wardrobe

8Her character

  1. The soul file
  2. Changing who she is — a worked example
  3. Language
  4. Tool voice patterns
  5. Emotion and the face
  6. Skills
  7. What she remembers about you
  8. What is enforced, and what is only asked

9Terminal and platforms

  1. The terminal
  2. Reading the header
  3. The nineteen slash commands
  4. Keys
  5. The approval card
  6. Work mode from the terminal
  7. The spinner, the phrase and the bar
  8. kotoba --once — one question, one answer
  9. Platform support
  10. Windows today

10Contributing and reference

  1. A development environment
  2. Running the tests
  3. House rules
  4. Adding a tool
  5. Adding a skill
  6. The build pipeline
  7. Continuous integration
  8. Licence
  9. Roadmap, and what is deliberately not planned
  10. Versioning, the changelog, and how a release is meant to work
  11. FAQ
  12. Getting help, and reporting a problem

11Vision

  1. What she can see
  2. Session captures — what she saw while working
  3. Visual memory — what she chose to keep
  4. The three tools
  5. Privacy and deletion

12Plugins

  1. Plugins: your own tools, without touching the repository
  2. Your first plugin
  3. The tool module contract
  4. Installing a plugin, and shipping one
  5. How the loader works
  6. The security position, stated plainly
  7. Testing your plugin

13Architecture

  1. One engine, several front doors
  2. A turn, end to end
  3. Register, channel, transport — three axes, and the two that get confused
  4. Events and cards — being listened to is not being drawn
  5. Inline versus deferred execution
  6. The data layer
  7. The packaged frontend
  8. Rate limiting and back-pressure
  9. Untrusted text — content, not a request
  10. What is deliberately not in the architecture