F-Trigger (Pre-release)

Track coding activity in your workspace and generate AI-powered summaries and social drafts via your own backend (Firebase Functions).

Pre-release notice

• This is a pre-release for testing and feedback.
• Features and APIs may change. Please report issues.

What data is sent when you generate AI summaries

When you run the command F-Trigger: Generate AI Summary, the extension sends the following to your backend:

• Summary statistics (counts of changes, sessions, files modified)
• File names involved in recent activity
• Snippets of code around your recent changes (before/after/changed text, truncated and sanitized)
• A chronological activity narrative assembled locally
• The selected project ID

The extension does NOT send:

• Your tokens, passwords, or credentials
• Full workspace contents
• Hidden dotfiles/config/build artifacts (the tracker skips common non-source files)

You must be signed in (Auth) to submit. You can review the generated report before submission when exporting for AI.

Features

• Tracks edits with timestamps, type (add/delete/modify), basic stats
• Groups edits into coding sessions
• Generates an AI-ready activity report
• Submits to Firebase Functions and displays results in a webview
• Optional auto-submit on commit/push (disabled by default)

Quick start

• Install the extension
• Command: F-Trigger: Sign In (opens auth flow)
• Make some changes in your workspace
• Command: F-Trigger: Generate AI Summary

Settings

• f-trigger.useEmulator (boolean, default: false) - Use Firebase emulator for development
• f-trigger.autoSubmitOnCommit (boolean, default: false)
• f-trigger.autoSubmitOnPush (boolean, default: false)
• f-trigger.autoSubmitProject (string)
• f-trigger.autoSubmitScheduleTime (now | 1hour | 3hours | tomorrow9am)
• f-trigger.appCheckDebugToken (string) - App Check debug token for development/testing (only used when emulator is enabled)

Environment Variables

For development with Firebase emulators, you can set the App Check debug token via:

1. VS Code Settings (Recommended): Set f-trigger.appCheckDebugToken in your VS Code settings
2. System Environment Variable: Set FIREBASE_APP_CHECK_DEBUG_TOKEN as a system environment variable
3. VS Code Launch Configuration: Add to .vscode/launch.json:

   {
     "configurations": [
       {
         "name": "Extension",
         "type": "extensionHost",
         "request": "launch",
         "env": {
           "FIREBASE_APP_CHECK_DEBUG_TOKEN": "your-debug-token-here"
         }
       }
     ]
   }
   

Getting Your App Check Debug Token

1. Go to Firebase Console
2. Select your project: f-trigger
3. Navigate to App Check > Apps
4. Select your app: 1:273389555171:web:f91725703dcf5b308864d6
5. Click on the Debug tokens tab
6. Copy the debug token and use it in one of the methods above

Security and privacy

• Webviews include a strict Content-Security-Policy and escape dynamic content
• No shell commands or unsafe eval are used
• Logs avoid printing sensitive tokens

Release notes

See CHANGELOG.md for version details.

Following extension guidelines

Ensure that you've read through the extensions guidelines and follow the best practices for creating your extension.

• Extension Guidelines

Working with Markdown

You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts:

• Split the editor (Cmd+\ on macOS or Ctrl+\ on Windows and Linux).
• Toggle preview (Shift+Cmd+V on macOS or Shift+Ctrl+V on Windows and Linux).
• Press Ctrl+Space (Windows, Linux, macOS) to see a list of Markdown snippets.

For more information

• Visual Studio Code's Markdown Support
• Markdown Syntax Reference

Enjoy!