Using SaveSlot
Extensions
An extension is a ready-made starting point for one use case. It brings:
- official tables with fixed columns, so every agent and page reads the same structure;
- skills: short instructions that tell your agent when and how to use those tables;
- the data sources that can fill them;
- default pages that work as soon as data arrives.
Install extensions from Extensions in the console, into a new slot or an existing one. A new slot counts toward your plan's slot limit.
Fitness Log
Sleep, activity, workouts, weight and meals in one place your agent can read and write. For people who already talk to ChatGPT or Claude about food, training and weight.
Tables
| Table | Columns | Written by |
|---|---|---|
| Daily summary | Date, Steps, Resting HR, Active energy | Computed from the day's readings |
| Sleep | Date, Duration, Fell asleep, Note | Data source |
| Workouts | Date, Type, Duration, Distance | Data source; your agent can add one you tell it about |
| Weight | Date, Weight, Body fat, Note | Data source; your agent can add one you tell it about |
| Meals | Time, What, Calories, Note | Your agent, from conversation |
Skills
- Log a meal from a sentence. When you mention what you ate, it writes one row to Meals. Calories it works out itself are marked Inferred; a figure from a label is Confirmed.
- Read sleep and recovery before training. Before it talks about training, it reads the last 14 days of Sleep and Daily summary, and says which days the figures come from.
- Build a health dashboard page. When you ask for a chart, it publishes a page that reads the official tables instead of pasting numbers into the chat.
Data sources: Apple Health, Garmin, file import. Default page: Sleep and recovery.
What it does not do
- No diagnosis and no treatment advice. It records and shows; what the numbers mean for your health is for you and your doctor.
- No calorie recognition from photos. Calories come from what you say or from a label.
- Not a replacement for your training app. Plans, classes and coaching stay where they are.
- Daily and per-workout summaries only. Minute-by-minute readings stay in the source.
Project Keeper
Decisions, tasks and handoffs that every coding agent on the project reads before it starts. For solo developers who switch between Claude Code, Codex and other local agents on the same project.
Tables
| Table | Columns | Written by |
|---|---|---|
| Decisions | Project, Decision, Why, Status | Your coding agents |
| Tasks | Project, Task, Owner, State | Your coding agents |
| Handoffs | Project, When, Handoff, From | Your coding agents |
| Run events | When, Event, Host | Your coding agents |
Skills
- Record a decision and what it replaces. The decision goes into Decisions with its reason, and the decision it replaces is marked as no longer in force.
- Read the current state before starting. Each session starts by reading decisions in force, open tasks and the latest handoff.
- Write a handoff at the end of a session. What was done, what is left, what to watch for.
- Flag tasks that contradict a decision. When a decision changes, open tasks that no longer fit are flagged instead of quietly done.
No data source: your agents write it. Default page: Project notebook, with a folder per project.
What it does not do
- Not a task board for a team. It is one person's projects across their own agents.
- It does not read your code or your repository. It keeps what the agents write down.
Blank slot
No official tables. Tell your agent what you want to keep, and it proposes tables as you go. Use it for anything no extension covers yet.