NOTEGEN.Let Agent edit notes safely
Give a bounded task, limit available tools, and review every proposed change before writing.
Agent can use NoteGen tools to read and modify files, records, tags, and memories, along with enabled MCP servers and Skills. It has more authority than ordinary Chat, so define the scope before running it.
Take it slow along the Seine
A slow walk from Île Saint-Louis past the Louvre to the Tuileries
Musée d’Orsay reservations and hours
Reservation, opening hours, and travel information
A Paris bistro for dinner
Remember to book a table in advance
Le Marais galleries and shops map
Le Marais galleries and shops map
Weekend Paris Route
3 nodes · Just now
Seine Walk
4 nodes · Today
Restaurants and Coffee
5 nodes · Yesterday
Rainy-day Alternative
4 nodes · Yesterday
Weekend in Paris
Focus the two days on the Seine, Le Marais, and Montmartre, leaving more time for walks, meals, and spontaneous stops.
Choose one main route each day. If a place feels right, stay a little longer.
Itinerary overview
- Saturday: the Seine, the Louvre courtyard, Le Marais, and a Paris bistro
- Sunday: Montmartre, Musée d’Orsay, and gifts before departure
| Day | Main route | Walking |
|---|---|---|
| Sat | Île Saint-Louis → Le Marais | About 8 km |
| Sun | Montmartre → Musée d’Orsay | About 7 km |
Saturday · The Seine and Le Marais
09:00—12:00 Seine walk
Start on Île Saint-Louis and walk past the Louvre courtyard to the Tuileries, leaving time for unplanned stops.
12:15—13:30 Lunch
Have a simple lunch near the Palais Royal and save the classic Paris bistro for dinner.
15:00—17:30 Le Marais
Explore the architecture and public spaces, with time for coffee before leaving.
Before departure
Before starting
- Open the target note or name its path explicitly.
- Enable only the knowledge base, MCP servers, and Skills required for the task.
- Copy important files or create a local ZIP backup.
- State the goal, forbidden changes, and acceptance criteria.
For example:
Reorganize the level-two headings in the current note. Preserve all facts and links, and do not add unsupported conclusions. Summarize the changes afterward.
Review the run
- Reading, searching, and drafting normally do not change files directly.
- Write, move, and delete operations request confirmation according to the active permission policy.
- Editor changes appear as a Diff. Check deleted text, links, code blocks, and image paths before accepting.
- For multi-file work, review each file rather than approving from the summary alone.
Reduce risk
- Split the task into analysis, proposal, and modification stages.
- Ask Agent to list the files it intends to change first.
- Do not enable unrelated filesystem or remote MCP tools.
- Require source-note or web citations for factual claims.
- You can add instructions while a long Agent task is queued; stop it immediately if it is heading in the wrong direction.
If the result is wrong, reject the Diff or use editor undo. Recover completed cross-file operations from a backup, sync history, or Git history. See AI Chat and Agent for capability boundaries.