- Reactivity: how cells track their dependencies and re-run.
- SQL and Python: querying connections and using results as dataframes.
- Outputs and charts: tables, charts, and widgets.
- Environment and kernel: packages, the kernel, and compute.
Create a notebook
Notebooks live in a workspace, and their kernel runs on the workspace’s machine. Like any workspace file, a notebook is saved in Files and copied onto the machine while the workspace is awake. See Where workspace files live.- Ask the agent. In any chat, ask for a notebook: “Build a notebook that tracks weekly signups by channel.” The agent creates it, adds cells, and runs them.
- Create one yourself. Open the workspace’s files and click New notebook. It opens with one empty cell.
Cells
A notebook is a list of cells. Each cell is one of:- Python: any Python code.
- SQL: a query against a connection, or DuckDB over the notebook’s own data. See SQL and Python.
- Markdown: text, headings, and notes.
- Click Add a cell at the end of the notebook.
- Open a cell’s ⋯ menu and choose Insert cell above, Insert cell below, or one of the Insert Markdown and Insert SQL items.
- Select a cell and press A to insert above or B to insert below.
Build it with the agent
The agent has full control of notebooks through its notebook tools. It can:- Create notebooks, and add, edit, move, and delete cells.
- Run a cell, the whole notebook, the stale cells, or everything upstream or downstream of a cell.
- Read outputs, variables, and dataframes, and follow the dependency graph.
- Install packages and change notebook settings.
- Show any cell’s output, such as a table or chart, right in the chat.
Work together
Notebooks are edited live by everyone in them, including the agent.- Avatars in the toolbar show who is in the notebook. Each cell shows who is editing it, and the agent appears as Alkera.
- Typing from several people in one cell merges as they type.
- Everyone shares one kernel, so everyone sees the same outputs. Each run records who ran it, such as “by Alkera agent for Alice”.
- A cell is not re-run automatically while someone is editing it.
The file format
A notebook is a plain Python file ending in.alknb.py. It builds on marimo’s file format: each cell is a function, so the notebook is readable Python, diffs cleanly in git, and runs in marimo with the alkera package installed.
alkera module for SQL, charts, Markdown, and widgets. Outputs are saved next to the notebook, not in the file.
View and download
In Files, a notebook previews read-only with its saved outputs. Previewing never starts a kernel. Download saves the.alknb.py file. Individual outputs can be downloaded as images or copied as CSV.
In this section
Reactivity
The dependency graph, stale cells, and run modes.
SQL and Python
SQL cells, connections, and dataframes.
Outputs and charts
Tables, charts, widgets, and more.
Environment and kernel
Packages, the kernel, and compute.
Keyboard shortcuts
Every notebook shortcut.
Dashboards
Coming soon: share a notebook as an interactive dashboard.