> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/design/system/klassapp-handoff-2026-10-08-toshi-mobile.md).

# Toshi on phones and tablets: handoff, 2026-10-08

* `HANDOFF.md`: four PRs, smallest first:

  * **T1** launcher and bottom safe zone;
  * **T2** preview sheet;
  * **T3** setup guide;
  * **T4** assistant (early access).

  **T1 and T2 can ship before 17 October.** It also covers what the current phone experience gets wrong, and open questions.
* `concept/index.html`: every screen and state at 375, 414 and 768. `concept/toshi.html` is the click-through.
* `concept/measure.html`: the automatic check: sideways scroll, 44px targets, the bottom safe zone, the keyboard, focus and Back.
* `design-system/`: the tokens (including the new bottom safe-zone tokens) and the K mark.

**Not browser-measured yet:** run `measure.html` from a local web server and paste its results into T1 and T2. Contrast is calculated from hex.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://klassdocs.gitbook.io/klassapp-documentation/design/system/klassapp-handoff-2026-10-08-toshi-mobile.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.