[Feature]: Project-scoped scratchpad shared across threads

[burnmandont]

Problem or use case

I often need to keep short-lived project context—commands to run, temporary TODOs, review reminders, and handoff notes—where it is visible from every thread in a project.

Thread drafts are tied to one conversation, while files such as AGENTS.md are durable repository instructions and may be committed. An external notes app loses the project association and is unavailable from connected T3 Code clients.

Smallest useful scope

Would a small project-scoped scratchpad be in scope?

• One plain-text note per project
• Accessible from the chat header
• Shared by every thread in that project
• Persisted by the project's T3 server
• Synchronized to connected web, desktop, and mobile clients
• Autosaved with bounded update frequency and an explicit size limit
• Last-write-wins if two clients edit it concurrently

The note would be user-facing only. It would not be included in agent prompts.

Non-goals

• Rich text or formatting controls
• Multiple notes
• Note history or collaborative cursor merging
• Agent read/write access
• Automatic prompt injection
• Global or per-thread notes

Related proposal

#2396 proposes session-scoped notes, including an agent-shared region injected into prompts. It also mentions project-scoped private notes as a possible sibling proposal. This idea is that narrower sibling: project-scoped, private to the T3 UI, and never sent to the model.

Implementation direction

A focused implementation could reuse the existing project metadata command/event/projection path and add one field to the project projection. We have a working version in our fork, but would reimplement it cleanly against current main with focused persistence, synchronization, web, and mobile tests.

Is this feature in scope, and would maintainers consider a focused PR? If so, is project metadata the preferred persistence model?

[benz16107]

+1, this is exactly what I want.

How I would use it: I usually have several threads open in one project, and I keep notes that are for me, not for the agent. Things to check later, an idea for the next thread, a command I need again, what is left to review. Right now those notes either go into the composer and get deleted before I send, or into a separate notes app that has no link to the project.

A panel I can open beside the thread, with one note per project that is still there when I switch threads or come back the next day, would cover it. User-only is right for me, I do not need the agent to read it.

[Winds-AI]

Just an HTML UI mockup for the notes sidebar.

notes-ui-mockup.mp4

[djgilcrease]

NOTE: This comment was left by gpt-6.1-sol high on behalf of Dj Gilcrease.

A working external Private Project Notes plugin is now released as v0.1.0. The exact plugin announcement in #23574 includes installation instructions, pinned host requirements, evidence and limits.

This extends this proposal's single scratchpad at Dj's request: Notes in thread information opens a searchable dropdown of all notes for the project, across threads. Users can create/edit text, checklist or image notes; checklists have toggle/reorder controls. These remain private user notes: no agent commands, automatic prompt injection or connection to agent-accessible Shared Project Memory.

Notes live as ordinary Markdown and local image assets in a project-selected directory, defaulting exactly to ~/.t3/notes/<local_project_id> on the owning environment. External editor changes, renames and deletions import on open/Refresh, including changes made while T3 was stopped. Changing directories preserves the old files.

Every participating machine persists its synchronized files. Users explicitly link an empty destination project with a shared identity, then initiate bounded, bidirectional sync through a connected client. Offline copies survive restart; concurrent edits remain visible as conflict versions and deletions carry tombstones. Project IDs or matching repository names do not silently combine unrelated notes.

This requires the prototype host fork and does not imply upstream approval. Install https://github.com/digitalxero/t3-project-notes through Settings → Plugins on djgilcrease/t3code's t3/create-plugin-system. The pinned host requirement is a3e3291a18864ca85347fffa2373f04160f91f75; installation/lifecycle and normal packaged loading were also verified on integrated host f67f7c462527aa1c2e2d436d5812cefe3ef8834e. Host PR #4 adds generic portable UI/project-settings boundaries. Product storage and sync policy stay in the external plugin; there is no upstream implementation PR.

Required plugin CI, actual repository-URL install/disable/enable/removal, Markdown retention, denied agent access, packaged-worker restart, public download checksums, and Linux web create/open/edit verification passed. Release receipts and captures distinguish the two-environment sync harness from live remote-machine proof.

Actual limits: explicit sync and project linking, no continuous cloud sync or filesystem watcher; 200 note IDs including tombstones, 16 KiB bodies and 64 KiB raster images. Native Electron/mobile devices, live remote/tunnel sync and SEA were not exercised. Dj merged the host PRs with hosted host checks unresolved, so local evidence is not a claim of green full-host CI. The linked announcement records the remaining bounds and data-retention behavior.