whybook 0.2.0__tar.gz

whybook-0.2.0/.copier-answers.yml

@@ -0,0 +1,16 @@
+# Changes here will be overwritten by Copier; NEVER EDIT MANUALLY
+_commit: v4.6.5
+_src_path: https://github.com/jupyterlab/extension-template
+advanced: false
+author_email: ''
+author_name: Michal Krassowski
+has_ai_rules: false
+has_binder: false
+has_settings: true
+kind: frontend-and-server
+labextension_name: future
+project_short_description: A future of data analysis
+python_name: future
+repository: ''
+test: true
+

whybook-0.2.0/.gitignore

@@ -0,0 +1,131 @@
+*.bundle.*
+lib/
+node_modules/
+*.log
+.eslintcache
+.stylelintcache
+*.egg-info/
+.ipynb_checkpoints
+*.tsbuildinfo
+whybook/labextension
+# Version file is handled by hatchling
+whybook/_version.py
+
+# Integration tests
+ui-tests/test-results/
+ui-tests/playwright-report/
+
+# Created by https://www.gitignore.io/api/python
+# Edit at https://www.gitignore.io/?templates=python
+
+### Python ###
+# Virtual environments
+.venv
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage/
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# pyenv
+.python-version
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# Mr Developer
+.mr.developer.cfg
+.project
+.pydevproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# End of https://www.gitignore.io/api/python
+
+# OSX files
+.DS_Store
+
+# Yarn cache
+.yarn/
+
+# Screenshots of ui-tests/smoke.js
+ui-tests/smoke-shots/

whybook-0.2.0/.prettierignore

@@ -0,0 +1,12 @@
+node_modules
+**/node_modules
+**/lib
+**/package.json
+!/package.json
+whybook
+epi
+eslint.config.mjs
+.venv
+src/kernelCode.ts
+# Markdown is written by hand and not checked
+**/*.md

whybook-0.2.0/.yarnrc.yml

@@ -0,0 +1,2 @@
+nodeLinker: node-modules
+enableScripts: false

whybook-0.2.0/CHANGELOG.md

@@ -0,0 +1,5 @@
+# Changelog
+
+<!-- <START NEW CHANGELOG ENTRY> -->
+
+<!-- <END NEW CHANGELOG ENTRY> -->

whybook-0.2.0/LICENSE

@@ -0,0 +1,203 @@
+Copyright (c) 2026, Michal Krassowski
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

whybook-0.2.0/PKG-INFO

@@ -0,0 +1,145 @@
+Metadata-Version: 2.5
+Name: whybook
+Version: 0.2.0
+Summary: Whybook: a question-driven view of Jupyter notebooks
+Project-URL: Homepage, https://github.com/openteams-ai/whybook
+Project-URL: Bug Tracker, https://github.com/openteams-ai/whybook/issues
+Project-URL: Repository, https://github.com/openteams-ai/whybook.git
+Author: Michal Krassowski
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: whybook/sandbox/codex/LICENSE
+License-File: whybook/sandbox/codex/NOTICE
+Keywords: jupyter,jupyterlab,jupyterlab-extension
+Classifier: Framework :: Jupyter
+Classifier: Framework :: Jupyter :: JupyterLab
+Classifier: Framework :: Jupyter :: JupyterLab :: 4
+Classifier: Framework :: Jupyter :: JupyterLab :: Extensions
+Classifier: Framework :: Jupyter :: JupyterLab :: Extensions :: Prebuilt
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Python: >=3.10
+Requires-Dist: jupyter-server<3,>=2.13.0
+Requires-Dist: jupyterlab-unfold>=0.3.4
+Requires-Dist: jupyterlab<5,>=4.4.0
+Provides-Extra: claude
+Requires-Dist: claude-agent-sdk>=0.2.157; extra == 'claude'
+Provides-Extra: demo
+Requires-Dist: numpy; extra == 'demo'
+Requires-Dist: pandas; extra == 'demo'
+Requires-Dist: pyarrow; extra == 'demo'
+Requires-Dist: statsmodels; extra == 'demo'
+Provides-Extra: dev
+Requires-Dist: jupyter-builder>=1.2.0; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: jupyter-book<3,>=2.1; extra == 'docs'
+Provides-Extra: kernel
+Requires-Dist: narwhals>=2; extra == 'kernel'
+Provides-Extra: local
+Requires-Dist: huggingface-hub; extra == 'local'
+Requires-Dist: llama-cpp-python>=0.3.35; extra == 'local'
+Provides-Extra: models
+Requires-Dist: pydantic-ai-slim[anthropic,google,mistral,openrouter]<3,>=2.51; extra == 'models'
+Provides-Extra: plots
+Requires-Dist: ipywidgets>=8; extra == 'plots'
+Requires-Dist: plotly>=6; extra == 'plots'
+Requires-Dist: tqdm; extra == 'plots'
+Provides-Extra: speech
+Requires-Dist: moonshine-voice<0.2,>=0.1.5; extra == 'speech'
+Provides-Extra: test
+Requires-Dist: coverage; extra == 'test'
+Requires-Dist: narwhals>=2; extra == 'test'
+Requires-Dist: pandas; extra == 'test'
+Requires-Dist: pytest; extra == 'test'
+Requires-Dist: pytest-asyncio; extra == 'test'
+Requires-Dist: pytest-cov; extra == 'test'
+Requires-Dist: pytest-jupyter[server]>=0.6.0; extra == 'test'
+Description-Content-Type: text/markdown
+
+# Whybook
+
+> [!WARNING]
+> **Research prototype.** Whybook is a research prototype for the future of Jupyter interfaces, and the text below is its pitch. Its features, settings and notebook metadata can change between releases without deprecation.
+
+## You ask the questions. Agents write the code.
+
+Whybook is a view of a Jupyter notebook for data analysis with AI. It has no chat box. The analyst drags a column onto a cell and picks one of the questions it offers, or types one of their own. The view writes the cell, places it and runs it. Every constant, default and choice behind the result is shown on the cell, where the analyst can question it.
+
+- Any `.ipynb` opens in the view, next to the classic notebook.
+- The first question offered usually runs from a template, with no model call.
+- Branches run in parallel in kernel subshells.
+
+![The Whybook view of the demo notebook in JupyterLab after Run all. Cell [4] carries the chips MIN_DAYS 14, inner join, ci bootstrap and n_boot 1000, and the Exploration panel counts the questions asked by type.](screenshots/bench.png)
+
+## A notebook view built around questions
+
+Whybook opens any `.ipynb` file as a second view, next to the classic notebook. Both views share one notebook model and one kernel, so an edit in one shows in the other. Agents do most of the work, under one rule: the result is an ordinary notebook, and the questions, choices and assumptions go into its metadata. The analyst chooses how deep to go on each cell: its question, the choices on its chips, or its code.
+
+- **Ask by pointing at the data.** Anything in the Variables and Contents panels can be dragged onto a cell, a variable or a column, and so can files and database tables. The view lists up to eight ranked questions of five types, each with a place in the notebook. Most questions run code from a template at once, with no model call. For those marked needs AI, an AI writes the code.
+- **Every choice in plain sight.** After a cell runs, the view reads its code against the live kernel and lists the values that the result depends on. Each value becomes a short chip, its name and its value, such as `MIN_DAYS 14`, or `inner join ×2` for two merges that keep pandas' default. Constants defined in imported files are shown on the cell that uses them.
+- **Question the result.** Every mark of a plot drawn by the view's helpers maps to rows of its data frame. The view counts the rows behind a selection, reports what differs there and offers questions about it.
+- **Branch in parallel, keep one line of cells.** Shift+drop turns any question into a branch, and Alt+drop starts several branches at once. Each branch runs in its own kernel subshell (JEP 91, ipykernel 7), so branches run in parallel on the same data without copying it. The notebook stays a single list of cells, and there is no reactive execution.
+- **One question, as many cells as it needs.** When a question needs AI, an agent answers it in the notebook. It adds and runs the cells that the question needs, and it ends with an answer of a few sentences that links the cells that show it. Each cell is marked as written by AI, and one click removes the cells of a run.
+
+![A selection of weeks 14 to 24 on the plot of cell [4]. The view counts 2,050 rows and 262 patients behind it, reports that A minus B is +1.86 there and +1.33 elsewhere, and offers three questions, each with its place in the notebook.](screenshots/plot-selection.png)
+
+The data in the screenshots is synthetic: the demo cohort of `examples/pain_diary`.
+
+## Requirements
+
+- JupyterLab 4.4 or later, in the 4.x series. On 4.6 and later, the sections of the Whybook panel can also move to the file browser.
+
+## Install
+
+```bash
+pip install "whybook[claude,kernel,demo,local,models,speach]"
+jupyter lab
+```
+
+`local` builds llama-cpp-python for the local models, with the system's C++ compiler, in about 4 minutes: without a compiler, leave it out of the list. To open a notebook in the view, right-click it in the file browser and choose Open With, Whybook. The demo notebook, `pain_diary_demo.ipynb`, is in this repository, with its data in `examples/pain_diary/`.
+
+Once you connect a remote AI model, the view sends it each table that it shows as a tile, to get a label, and asks it for more questions at each drop or click. With the setting "Keep data on this machine", no values, tables or pictures leave the machine.
+
+The extension is one Python package, `whybook`: the helpers a notebook imports (`import whybook`), the server extension (`whybook.server`) and the frontend extension of the same name. The view still reads the `epi` metadata and output types of notebooks from before 25 September 2026.
+
+## Development
+
+From a clone of this repository:
+
+```bash
+pip install --editable ".[dev,test,claude,kernel,demo, speach]"
+jupyter-builder develop . --overwrite
+jupyter server extension enable whybook
+jlpm build
+```
+
+Run `jlpm build` again after each change to the TypeScript source, or keep `jlpm watch` running beside `jupyter lab`. The Python tests run with `pytest whybook/server/tests`, and the Jest tests with `jlpm test`. The integration tests are in `ui-tests/`, whose README has their commands.
+
+## Uninstall
+
+```bash
+pip uninstall whybook
+```
+
+## Troubleshoot
+
+If you are seeing the frontend extension, but it is not working, check that the server extension is enabled:
+
+```bash
+jupyter server extension list
+```
+
+If the server extension is installed and enabled, but you are not seeing the frontend extension, check the frontend extension is installed:
+
+```bash
+jupyter labextension list
+```
+
+## License
+
+Whybook is under the Apache License 2.0: see [LICENSE](LICENSE). The Seatbelt profiles in `whybook/sandbox/codex/` come from OpenAI Codex, under the same licence, with its LICENSE and NOTICE.

whybook-0.2.0/README.md

@@ -0,0 +1,82 @@
+# Whybook
+
+> [!WARNING]
+> **Research prototype.** Whybook is a research prototype for the future of Jupyter interfaces, and the text below is its pitch. Its features, settings and notebook metadata can change between releases without deprecation.
+
+## You ask the questions. Agents write the code.
+
+Whybook is a view of a Jupyter notebook for data analysis with AI. It has no chat box. The analyst drags a column onto a cell and picks one of the questions it offers, or types one of their own. The view writes the cell, places it and runs it. Every constant, default and choice behind the result is shown on the cell, where the analyst can question it.
+
+- Any `.ipynb` opens in the view, next to the classic notebook.
+- The first question offered usually runs from a template, with no model call.
+- Branches run in parallel in kernel subshells.
+
+![The Whybook view of the demo notebook in JupyterLab after Run all. Cell [4] carries the chips MIN_DAYS 14, inner join, ci bootstrap and n_boot 1000, and the Exploration panel counts the questions asked by type.](screenshots/bench.png)
+
+## A notebook view built around questions
+
+Whybook opens any `.ipynb` file as a second view, next to the classic notebook. Both views share one notebook model and one kernel, so an edit in one shows in the other. Agents do most of the work, under one rule: the result is an ordinary notebook, and the questions, choices and assumptions go into its metadata. The analyst chooses how deep to go on each cell: its question, the choices on its chips, or its code.
+
+- **Ask by pointing at the data.** Anything in the Variables and Contents panels can be dragged onto a cell, a variable or a column, and so can files and database tables. The view lists up to eight ranked questions of five types, each with a place in the notebook. Most questions run code from a template at once, with no model call. For those marked needs AI, an AI writes the code.
+- **Every choice in plain sight.** After a cell runs, the view reads its code against the live kernel and lists the values that the result depends on. Each value becomes a short chip, its name and its value, such as `MIN_DAYS 14`, or `inner join ×2` for two merges that keep pandas' default. Constants defined in imported files are shown on the cell that uses them.
+- **Question the result.** Every mark of a plot drawn by the view's helpers maps to rows of its data frame. The view counts the rows behind a selection, reports what differs there and offers questions about it.
+- **Branch in parallel, keep one line of cells.** Shift+drop turns any question into a branch, and Alt+drop starts several branches at once. Each branch runs in its own kernel subshell (JEP 91, ipykernel 7), so branches run in parallel on the same data without copying it. The notebook stays a single list of cells, and there is no reactive execution.
+- **One question, as many cells as it needs.** When a question needs AI, an agent answers it in the notebook. It adds and runs the cells that the question needs, and it ends with an answer of a few sentences that links the cells that show it. Each cell is marked as written by AI, and one click removes the cells of a run.
+
+![A selection of weeks 14 to 24 on the plot of cell [4]. The view counts 2,050 rows and 262 patients behind it, reports that A minus B is +1.86 there and +1.33 elsewhere, and offers three questions, each with its place in the notebook.](screenshots/plot-selection.png)
+
+The data in the screenshots is synthetic: the demo cohort of `examples/pain_diary`.
+
+## Requirements
+
+- JupyterLab 4.4 or later, in the 4.x series. On 4.6 and later, the sections of the Whybook panel can also move to the file browser.
+
+## Install
+
+```bash
+pip install "whybook[claude,kernel,demo,local,models,speach]"
+jupyter lab
+```
+
+`local` builds llama-cpp-python for the local models, with the system's C++ compiler, in about 4 minutes: without a compiler, leave it out of the list. To open a notebook in the view, right-click it in the file browser and choose Open With, Whybook. The demo notebook, `pain_diary_demo.ipynb`, is in this repository, with its data in `examples/pain_diary/`.
+
+Once you connect a remote AI model, the view sends it each table that it shows as a tile, to get a label, and asks it for more questions at each drop or click. With the setting "Keep data on this machine", no values, tables or pictures leave the machine.
+
+The extension is one Python package, `whybook`: the helpers a notebook imports (`import whybook`), the server extension (`whybook.server`) and the frontend extension of the same name. The view still reads the `epi` metadata and output types of notebooks from before 25 September 2026.
+
+## Development
+
+From a clone of this repository:
+
+```bash
+pip install --editable ".[dev,test,claude,kernel,demo, speach]"
+jupyter-builder develop . --overwrite
+jupyter server extension enable whybook
+jlpm build
+```
+
+Run `jlpm build` again after each change to the TypeScript source, or keep `jlpm watch` running beside `jupyter lab`. The Python tests run with `pytest whybook/server/tests`, and the Jest tests with `jlpm test`. The integration tests are in `ui-tests/`, whose README has their commands.
+
+## Uninstall
+
+```bash
+pip uninstall whybook
+```
+
+## Troubleshoot
+
+If you are seeing the frontend extension, but it is not working, check that the server extension is enabled:
+
+```bash
+jupyter server extension list
+```
+
+If the server extension is installed and enabled, but you are not seeing the frontend extension, check the frontend extension is installed:
+
+```bash
+jupyter labextension list
+```
+
+## License
+
+Whybook is under the Apache License 2.0: see [LICENSE](LICENSE). The Seatbelt profiles in `whybook/sandbox/codex/` come from OpenAI Codex, under the same licence, with its LICENSE and NOTICE.