Standup Notes Generator

WHAT IT DOES

Provides a structured tool for generating and organizing daily standup meeting notes. The script displays a form with dedicated sections for "What I did yesterday", "What I'll do today", "Blockers/Impediments", "Achievements", and "Learnings". Each entry is automatically timestamped, and you can add custom sections, tags for categorization, and track progress over time. The summary view shows how many sections are filled and displays any tags applied. You can export notes as formatted text or JSON for sharing in standup meetings, archiving, or integrating with other tools. Per-user, per-day notes are saved by user identifier and date.

WHERE IT RUNS

Works on all websites (match pattern *://*/*), making it perfect for remote work, distributed teams, or anyone who wants to keep organized daily notes. Each user and date combination gets its own independent note set, allowing multiple team members to use the tool on shared devices without mixing notes. The notes are saved per user identifier and session date, ensuring continuity across sessions and page reloads.

HOW TO USE

Install the script and the standup notes generator appears in the panel. Enter your name or user identifier and the date to load or create notes for that day. Fill in the sections with your standup updates. Add tags to categorize your notes (e.g., "frontend", "api", "blocked"). Add custom sections to match your team's specific standup format. The summary shows which sections are filled and any tags applied. Use the export buttons to copy your notes as text or JSON to share in your standup channel or for personal records. The script saves your progress automatically as you work.

REAL MECHANISM: USER-DATE KEYED PERSISTENCE WITH DYNAMIC SECTION MANAGEMENT

This script uses a user-date-based storage architecture where each user and date combination gets its own isolated note set. The getUserId() function retrieves the current user identifier from GM_setValue or generates a new one, while getTodayString() returns the current date in YYYY-MM-DD format. Data is stored using GM_setValue with a key format of "standup_notes_" plus the user ID and date, ensuring data isolation between users and days. The data structure includes an entries object where keys are section IDs and values are the note text, plus tags array, createdAt timestamp, userId, and date. The sections system allows users to add and remove custom sections via the "Manage Sections" controls, with section data stored globally using the key "standup_sections". When a section is added, the script creates a new entry in the entries object and saves it immediately. The renderStandupNotes() function iterates through all sections, displays the content, and calculates the number of filled sections by filtering entries values with trim() length > 0. The summary updates in real-time showing completion status and any tags. Timestamps are formatted using toLocaleString() for human-readable display. The export functions generate formatted text with section headers and content, or JSON with the full data structure including sections. All operations are reactive, with automatic persistence through saveStandupNotes() and re-render.

THE PANEL

Drag the panel anywhere on screen by clicking and holding the header. It snaps to screen edges when released. Collapse it to a small bubble by clicking the minimize button, and expand it back by clicking the bubble. Resize the panel from any corner. Press Escape to close the configuration panel. Your position and size preferences are saved automatically per site.

PLEASE NOTE

This script requires the free BotGentz browser extension which provides the BGPanel framework and storage APIs. All data (notes, tags, sections, and user identifiers) is stored locally in your browser using GM_setValue and never sent anywhere. No analytics, no tracking, no external calls. The script only reads the current user identifier and date to isolate notes and never accesses user data, passwords, or sensitive information. Notes are saved per user and date, so ensure each team member enters their own identifier.