Claude Code with a calendar, and a memory that outlasts the session

Checked against Claude Code and Nuto on 2026-10-10.

Claude Code is good at the work in front of it. What you settle with it along the way — the follow-up for tomorrow, the release on Friday, the decision to stay on pnpm — lives in that session. Nuto gives Claude Code a planner and a memory outside the session: follow-ups become tasks on your calendar, progress is written down as the work moves, and the next session starts where the last one stopped.

What changes

Follow-ups land on your calendar. When something needs doing later, Claude Code files it as a task. A task without a date goes into the earliest free 30-minute slot between 9:00 and 18:00 over the next seven days, on a quarter-hour, and not over time already booked for something that can't overlap. If the week is full, the task stays unscheduled and Claude Code tells you so. A task you give a date keeps it.

Plans with dates stay dated. Ask it to plan the release week and every item becomes its own task on its own day, with the dates worked out in your time zone.

Progress is recorded at milestones. When work starts, gets blocked, ships or is finished, Claude Code updates the task with a short note and its status. You can see where things stand on the web or on your phone without asking.

The next session knows. Facts worth keeping — "this repository uses pnpm; npm rewrites the lockfile", "releases go out on Thursdays" — are saved as memories, one fact each, after a check for duplicates. On the first prompt of every session, Claude Code is handed your open tasks, your standing preferences and the memories that fit what you asked.

How it compares with what Claude Code has built in

Claude Code already carries some things across sessions. Nuto adds the parts that are about time and about more than one machine.

Keep instructions in CLAUDE.md: Nuto doesn't replace it. Claude Code's Projects, in beta on some plans, keep a memory across the cloud threads of one project; they don't put work on a calendar or share it beyond Claude.

Set it up

You need a Nuto account (you can start for free) and Claude Code on your own computer: in the terminal, an editor or the desktop app.

The quick way: let Claude Code do it

1. Open Connect your agent and copy the setup prompt.
2. Paste it into Claude Code. It asks before it installs anything, then installs the nuto command and the skill, and ends its reply with a pairing code.
3. Approve the code in your browser or in the Nuto app. Your password never passes through Claude Code.

By hand

Install the command line. On macOS or Linux:

curl -fsSL https://nuto.sqmem.top/install.sh | sh

On Windows, in PowerShell:

irm https://nuto.sqmem.top/install.ps1 | iex

Open a new terminal, then sign in, install the skill with its hooks, and check:

nuto auth login
nuto skill install --hooks
nuto doctor

nuto auth login prints a pairing code and a link; approve it there or in the Nuto app. Restart Claude Code so it picks up the skill and the hooks.

What gets installed

• The Nuto skill, in ~/.claude/skills/squirrel: when to read your context, when to file a task, when to record progress, what is worth remembering.

• A /checkpoint command, in ~/.claude/commands, for recording a milestone when you want it recorded now. It takes over the name /checkpoint, which Claude Code otherwise keeps as an alias of /rewind; /rewind and /undo still rewind.

• Three hooks in ~/.claude/settings.json:

  • On the first prompt of a session, it fetches your context (about 1,200 tokens) and adds it to the conversation. The first 300 characters of that prompt are used to pick the relevant memories.
  • When Claude Code compacts a long conversation, that context is summarized away with the rest. After each compaction, it adds the context again, picked for the session's first prompt.
  • When a long session ends without anything recorded, it reminds Claude Code once to record its progress, or to finish if nothing is worth keeping.

  All three stay silent when Nuto can't be reached.

To keep the hooks to one project, run nuto skill install without --hooks, then nuto skill install --dir .claude --hooks-only in that project.

A session, start to finish

You: Billing has to ship on Friday. Before that I need the rounding fix, the migration and a docs update.

Claude Code: I've added the release as a task on Friday, and the three steps as tasks in your free time this week.

You see four tasks on the calendar on your phone. The next morning, in a new session:

You: Let's do the migration.

Claude Code: Picking up the billing release: the migration now, then the docs…

When the migration is written, Claude Code marks its task done with a note on what changed, and saves the gotcha it ran into as a memory for next time.

Your data, your call

• You approve access in your browser or the app; Claude Code never sees your password.
• By default it can read and write your tasks and memories. You can narrow that when you approve, and revoke the device at any time in Settings → Devices.
• Nuto doesn't read your files. It keeps what Claude Code writes to it — tasks, notes, memories — and receives the start of each session's first prompt to find relevant memories. The privacy policy has the details.
• Without a connection, writes wait and are sent when you're back online.
• nuto uninstall revokes this machine's credential and removes the skill, the hooks and everything else Nuto wrote on it.

Limits worth knowing

• Tasks are scheduled between 9:00 and 18:00 in your time zone, seven days ahead, weekends included. Working days and hours of your own can't be set yet.
• Claude Code follows the skill's rules: it records at milestones, not after every message, and it can miss one. Use /checkpoint when you want something recorded now.
• The hooks work only in an agent that runs them, as Claude Code does. An agent without them reads your context when its own rules tell it to.

Questions

Do I still need CLAUDE.md? Yes. Instructions belong there. Nuto keeps what changes as you work: tasks, progress and the facts you pick up along the way.

Does it work with Claude Code in the cloud? Not yet. It needs the nuto command on the computer Claude Code runs on.

What does it cost? You can start for free. Subscriptions add room for more workspaces, members and attachments.