The agentic notebook workspace

Notebooks with an agent at the keyboard.

Ai8 is a Jupyter-compatible workspace with an AI agent built in. Ask for an analysis and the agent reads your project, writes and edits cells, and runs them on your kernel — asking before each change.

Python and RIn the browserStandard .ipynb

Analysts and data scientists

Spend the afternoon on the question, not the plumbing.

Explore, model and report in one place, with an agent that does the legwork you would otherwise type.

Teams and research groups

One workspace, shared projects, limits you set.

Projects, versions and environments in common — and assistant, LLM API and compute spend that stays inside an allowance.

Courses and programmes

Teach with notebooks, and with AI on your terms.

Assignments, timed assessments and grading in the same workspace, with the assistant on or off per assignment.

The agent

It works in your project, not in a chat box beside it.

Most notebook assistants hand you code to paste. The Ai8 agent uses the same files, notebook and kernel you do — and everything it does is written into the conversation, where you can open it.

  1. 01

    Reads before it answers

    It lists, searches and reads your notebooks, scripts and data — and PDFs, Word, PowerPoint and Excel files too. Each read is a line you can expand.

  2. 02

    Edits one cell at a time

    A proposed change arrives as a diff of that cell. Approve it and it lands in the live notebook, the way a collaborator's edit would.

  3. 03

    Runs on your kernel

    It runs cells on your notebook's own kernel, and their outputs are saved under the cell. Quick checks run on a scratch kernel that touches nothing.

  4. 04

    Plans, and remembers

    Longer work gets a checklist you can watch. What you ask it to remember — your conventions, a project's quirks — carries into the next conversation.

Control

Every change is yours to approve.

An agent that can run code needs limits you can see. Ai8 puts them in the conversation, not in a policy document.

  • Approval by default

    A new conversation asks before any edit or run. Allow one change, edits to one file, or every file — and revoke at any time.

  • Auto, when you want it

    Switch a conversation to Auto and tools run without asking. Access rules, allowances and the sandbox still apply.

  • The price before the machine

    Starting a runtime asks first, and names the machine and what it costs per hour. Nothing else the agent does starts one.

  • Your sandbox, not a bigger one

    The agent reaches exactly what a cell of yours can reach — same container, same limits, same restricted internet.

  • Files are data, never instructions

    A file or web page that tells the agent what to do is treated as content to read, not as a command to follow.

The workspace

A real Jupyter workspace, without the setup.

Sign in and your project is there: notebooks, files, a terminal, and a runtime the moment you need one. Nothing to install, nothing to keep in sync.

Opens before anything boots

Notebooks, files and saved outputs are readable as soon as you sign in. A runtime starts only when something needs to run.

Python and R

Standard Jupyter kernels in environments your team defines, with the packages it needs already installed.

Plain .ipynb

Notebooks stay ordinary .ipynb files with their outputs. Download any of them, any time, and open them anywhere.

Terminal and viewers

A terminal in the same runtime, and viewers for CSV, Excel, PDF, Markdown and HTML — next to your notebooks, in tabs you can split.

Completion as you type

Inline code suggestions in every cell. Tab to accept, keep typing to ignore.

Versions

Automatic snapshots, named versions, cell-by-cell compare, and a restore that tells you what it will change first.

Keeps going offline

Editing carries on when the network drops and syncs when you are back. The interface says which state you are in.

Variable explorer

See the dataframes and values in a Python kernel's memory without printing them.

For teams

Share the work. Set the limits.

A workspace for a whole group, run by its admins: who is in, what they can run, which models the agent and the LLM API use, and how much any one person can spend.

Projects you share

Owners, editors, commenters and viewers. Presence shows who is there; one person writes at a time, and hands over on request.

Allowances

Plans set each member's assistant, LLM API and compute limits, on a weekly, monthly or custom reset, with per-person overrides. Members see a percentage, not a bill.

Environments

Admins publish environments from a package list — with a private PostgreSQL inside each runtime when a course or project needs one.

Your choice of model

Admins pick the model the agent runs on from a catalog across the major vendors, and every call is metered to the member who made it.

LLM API access

Call any listed model from your own code — a small Python package or a plain HTTP endpoint — with no keys to manage: each runtime carries its own, and it stops when the runtime does. Included by the plan, and metered in credits against a limit of its own.

For teaching

Courses run in the same workspace.

Ai8 grew up teaching data science to postgraduate cohorts. Courses, assignments and assessments are first-class — and so is deciding when the assistant helps.

Courses and assignments

Rosters, sections, announcements and materials. An assignment is an ordinary project, authored the way you author anything else.

Deadlines the server keeps

Timed assessments start, end and submit on the server — even if a laptop closes or the network drops mid-exam.

AI policy per assignment

On for the group project, off for the exam. While a timed exam is open, the assistant is off for that student everywhere.

Oversight, disclosed

Course staff can read the conversations students had on coursework. Students are told so in every brief — and their own projects stay private.

Grading and gradebook

A grading queue, grades released when you decide, and a gradebook that exports to CSV for your VLE.

Integrity by design

No webcam proctoring, no lockdown browser. Server-kept rules, version history and honest records instead.

Built on the standards you already use.

Jupyter on disk and on the wire

Standard .ipynb with stable cell ids, and the standard kernel protocol. Your notebooks open in any Jupyter tool.

Outputs kept apart

Notebook output renders on its own sandboxed origin, so code you run can never reach your session.

Leaving is easy

Download notebooks and files whenever you like. There is no proprietary format to export from.

Bring your next analysis.

Ai8 is available by invitation. Tell us about your team or course, and we will set up a workspace for you.