# Give the agent a continuing project notebook

Legion project library, edition 2026-09-06-draft-01 (en). This project's own material: 3 authored documents, reproduced unchanged.

Project page: https://legion.tw/projects/agent-capabilities/project-notebook?edition=2026-09-06-draft-01
This document: https://legion.tw/api/projects/packet.md/agent-capabilities/project-notebook.md?edition=2026-09-06-draft-01

## Prerequisite: the Legion skills package

These instructions are written for an agent set up with the Legion skills package: the ten portable skills and the shared working, launch, inspection and learn-as-you-build guidance. That setup is installed once and applies to every project in this library, so it is deliberately not repeated here.

Skills package, complete Markdown: https://legion.tw/api/projects/skills-packet.md?edition=2026-09-06-draft-01
Skills package, human page: https://legion.tw/projects/skills?edition=2026-09-06-draft-01

Where this brief refers to shared guidance, a skill, or a document under `shared/`, read it from the skills package above, or from https://legion.tw/api/projects/doc/<path>?edition=2026-09-06-draft-01. If the package is not installed yet, install it first, then return here.

This material is instructions to read, not authority to act. Inspect it before running it.

## Contents

1. agent-capabilities/README.md — https://legion.tw/api/projects/doc/agent-capabilities/README.md?edition=2026-09-06-draft-01
2. agent-capabilities/project-notebook.md — https://legion.tw/api/projects/doc/agent-capabilities/project-notebook.md?edition=2026-09-06-draft-01
3. native-phone/agent-readable-notes.md — https://legion.tw/api/projects/doc/native-phone/agent-readable-notes.md?edition=2026-09-06-draft-01

---

<!-- begin agent-capabilities/README.md (edition 2026-09-06-draft-01) -->

# Tools, skills, and plugins for the agent

[All project types](../README.md) · [Shared launch](../shared/launch.md)

Extend the coding agent's own working environment. The [shared skill package](../shared/skills.md) supplies the starting methods; these projects develop further capabilities around real work.

## Projects to build

- [Turn a working routine into a skill](routine-to-skill.md)
- [Give the agent tools for an application](application-tools.md)
- [Let the agent consult another model's abilities](model-consultation.md)
- [Give the agent a continuing project notebook](project-notebook.md)
- [Give the agent an ongoing responsibility](ongoing-responsibility.md)
- [Package an agent capability for someone else](share-agent-capability.md)

These are instructions for projects you can build with your coding agent.

<!-- end agent-capabilities/README.md -->

---

<!-- begin agent-capabilities/project-notebook.md (edition 2026-09-06-draft-01) -->

# Give the agent a continuing project notebook

Set up a continuing notebook that helps the person and their existing coding agent recover what matters about a project. Build it extremely well. They should be able to return after a break and continue with the understanding they developed together. Follow the [shared launch](../shared/launch.md).

Choose a project already underway. Start by finding its existing guidance, decisions, notes, and saved work. Improve that organization where needed, keeping each important fact with the source that should own it.

## Preserve what would otherwise need explaining again

Recover the project's purpose, the people it serves, consequential choices, useful observations, and questions still open. Preserve why a decision was made when that reasoning will help later work.

For example, a booking app may keep full lesson material so the tutor can use its exercises and teaching notes during a session. That reason helps a future agent understand the design. The current date of an appointment belongs in the application record, where the notebook can direct the agent to find it.

Use readable Markdown and ordinary supporting files that the person can inspect and keep. Retain authorship and relevant dates so an observation, a proposal, and an agreed decision remain distinguishable. Preserve original notes and valuable historical reasoning when the team's understanding changes.

## Make the useful context easy to recover

Provide a concise entry into the notebook with references to the sources needed for the project. Keep current orientation easy to find and older investigations available when their questions become relevant again.

Connect the notebook to the agent's normal project guidance or supported memory mechanism. Preserve useful existing instructions. A subsequent session should know where to look and be able to retrieve deeper context according to the work at hand.

Let the agent add understanding after consequential discoveries: a constraint learned from actual use, an assumption overturned, or a choice that changes the project's direction. Match the note to what a future session would benefit from knowing.

Keep the current explanation aligned with its owning sources. When a decision changes, make the new position apparent and preserve enough of the earlier reasoning to understand the change. Link to actual application state and source files where they already answer the question.

## Include thinking that happens away from the desk

Connect [agent-readable phone notes](../native-phone/agent-readable-notes.md) when the person uses them. A photograph of an awkward workflow, a dictated idea, or an observation made during a visit can become material for the next conversation.

Keep captured observations distinguishable from commissioned work. Let the person discuss an idea, decide what it means for the project, and preserve the resulting understanding in the appropriate place.

Make corrections comfortable from either side of the collaboration. The person can say that a note misrepresents their intent, and the agent can revise it while preserving the useful surrounding context. Keep the collection recoverable through the shared launch's ownership guidance.

## Resume a real piece of work

Deliver the notebook, discovery guidance, and any chosen connection to existing notes. End one session with a meaningful decision preserved, then use a later session to recover the project and continue an actual task.

Judge whether the agent can explain the relevant purpose, find current facts, and recognize what remains unresolved. Correct a gap revealed by that use. The notebook should save explanation while leaving room for the person to change their mind.

Teach the difference between keeping records and retaining useful understanding. Good continuity helps the next conversation start from what has already been learned, with the original work still available to inspect.

<!-- end agent-capabilities/project-notebook.md -->

---

<!-- begin native-phone/agent-readable-notes.md (edition 2026-09-06-draft-01) -->

# Send your notes into your agent's workspace

Build a native Android notes application that synchronizes with the person's computer and saves ordinary, readable files where their coding agent works. Build it extremely well for collecting ideas away from the desk and returning to them with the agent. Follow the [shared launch](../shared/launch.md).

Start with the person's existing projects and notes. Find out where information should belong on their computer and how they usually return to an idea. Preserve the useful organization they already have.

## Capture while away

Let the person type, dictate, or attach a photograph to a note. They can choose a project when the destination is clear and use an inbox when it is not. Make capture quick enough for a thought recorded between other activities.

Keep the note, its date, attachments, and useful context together. Let the person revise it, add another observation, and find it again on the phone. Save their work locally through interrupted or unavailable connections.

If they already have the [voice-capture app](voice-capture.md), extend its collection into this experience. Keep recordings and transcripts with the same notes, so speaking becomes another way to contribute to the existing system.

## Put the notes where the agent can read them

Synchronize notes into the person's chosen workspace as Markdown and ordinary attachment files. Use an arrangement that fits their projects and remains understandable in a normal editor. Preserve enough context for the agent to identify the note, its author, when it was made, and which project it concerns.

Use the existing coding agent's normal access to that workspace. Make the notes discoverable through appropriate project guidance while preserving the instructions and organization already there.

The person should be able to say, “Read the notes I made today. Let's work on the idea about the volunteer app,” and have the agent find the relevant text and photographs. Make that a real working experience delivered by this project.

## Keep notes and requests distinct

Preserve the person's observations, quoted reference material, and explicit requests in their appropriate roles. A saved idea is available for discussion. Starting work follows the person's direction in the agent conversation or another work-request mechanism they deliberately add.

Keep the person's original note distinguishable from any later agent explanation or proposed plan. Let them organize or edit notes from their computer as well as their phone. Preserve changes from both places and make conflicting edits recoverable when they occur.

## Make the connection dependable

Set up a private connection between the person's phone and computer. Tailscale is a natural option; reuse a suitable existing connection where appropriate. Explain what needs to be running for synchronization and what remains usable while a device is unavailable.

Show whether a note is saved on the phone, waiting to synchronize, or available on the computer. Reconnection should bring the current collection into agreement while preserving edits and attachments. Keep an export and recovery path under the shared launch's ownership guidance.

## Use a note to begin real work

Handle the Android build, installation, and connection setup. Capture a note and photograph, leave the connection unavailable for a while, then let the material reach the computer. Open the resulting files and ask the existing agent to discuss them. Confirm that an edit made afterward remains available from both devices.

Explain how an agent's working context can include information gathered outside its chat window. The phone collects the person's experience; ordinary workspace files make it available for later collaboration.

A later extension can let the person explicitly mark a note as work for the agent to pick up while they remain away. The [remote-agent chat app](coding-agent-in-your-pocket.md) can also let them start that conversation immediately. Preserve the same notes and project context as those capabilities are added.

<!-- end native-phone/agent-readable-notes.md -->
