AI Feature Tracker

Community-maintained tracker of AI feature availability across subscription tiers.

🔗 View the Dashboard


What is this?

A single source of truth for answering questions like:

Built for fellow AI facilitators, educators, designers, and anyone who needs accurate, current information about AI tool availability.

Platforms Covered

PlatformVendorFeatures Tracked
ChatGPTOpenAIAgent Mode, Custom GPTs, Voice, Atlas, DALL-E, Deep Research, Codex
ClaudeAnthropicCode, Cowork, Projects, Artifacts, Extended Thinking, Vision
CopilotMicrosoftOffice Integration, Designer, Vision, Voice
GeminiGoogleAdvanced, NotebookLM, AI Studio, Deep Research, Gems, Workspace, Imagen, Live
PerplexityPerplexity AIComet, Agent Mode, Pro Search, Focus, Collections, Voice
GrokxAIChat, Aurora (images), DeepSearch, Think Mode, Voice
Local ModelsVariousLlama, Mistral, DeepSeek, Qwen, Codestral

Features

Accessibility

This site is designed to meet WCAG 2.1 AA standards:

How to Contribute

Found outdated info? Want to add a feature? See CONTRIBUTING.md.

Quick version:

1. Edit the relevant file in data/platforms/

2. Include a source link

3. Submit a PR

Automated Verification

This project includes an automated feature verification system that uses multiple AI models to cross-reference all feature data.

What gets verified

How it works

1. Multi-model cascade — Queries Gemini, Perplexity, Grok (X/Twitter), and Claude

2. Bias prevention — Skips same-provider models (e.g., won't ask Gemini about Google features)

3. Consensus required — Needs 3 models to confirm a change before flagging

4. Auto-changelog — Confirmed changes are logged to each feature's changelog

5. Human review — Creates issues/PRs for review, never auto-merges

Running verification

# Verify all features

node scripts/verify-features.js

Verify a specific platform

node scripts/verify-features.js --platform claude

Check only stale features (>30 days since last check)

node scripts/verify-features.js --stale-only

Dry run (no issues created)

node scripts/verify-features.js --dry-run

Link checking

Two link checkers serve different purposes:

CI checker (check-links.js) — runs in GitHub Actions weekly. Uses canonical categories from the collaboration protocol:

The checker fails CI on actionable problems (broken, timeout) while keeping soft-blocked/rate-limited as non-actionable signals.

node scripts/check-links.js              # Check all links

node scripts/check-links.js --broken-only # Show only broken links

Browser checker (check-links-browser.js) — runs locally through a real Chrome browser via Chrome DevTools Protocol. Bypasses all bot protection, captures page titles for content verification, and shows redirects. Zero external dependencies.
# Terminal 1: Start Chrome with remote debugging

(--user-data-dir avoids conflicts with your normal browser session)

macOS (Chrome)

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \

--remote-debugging-port=9222 --user-data-dir=/tmp/chrome-link-check

macOS (Brave, Edge, or any Chromium browser also works)

Linux

google-chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-link-check

Terminal 2: Run the checker

node scripts/check-links-browser.js # All platforms

node scripts/check-links-browser.js -p claude # One platform

node scripts/check-links-browser.js --help # All options

Requires API keys (verification only): GEMINI_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, ANTHROPIC_API_KEY

See VERIFICATION.md for full documentation.

Data Format

Platform data is stored in simple markdown files. Example:

## Feature Name

PropertyValue
Categoryagent
Statusga

Availability

PlanAvailableLimitsNotes
FreeNot available
Plus40/monthMessage limit

Talking Point

"Your presenter-ready sentence with key details bolded."

Sources

See data/_schema.md for the full specification.

Deployment

The site auto-deploys via GitHub Actions when changes are pushed to main.

How it works

1. Build job (.github/workflows/build.yml)

- Runs node scripts/build.js to regenerate docs/index.html and docs/about.html

- If output changed, commits it back to main with [skip ci] to prevent loops

- Runs on both pushes and PRs (PRs only validate the build, no commit)

2. Deploy job (same workflow)

- Uploads docs/ folder to GitHub Pages

- Only runs on pushes to main, not PRs

3. FTP deploy (.github/workflows/deploy-ftp.yml)

- Parallel deployment to snapsynapse.com via locked ftp

- Requires FTP_HOST, FTP_USER, FTP_PASS secrets

GitHub Pages setup

To enable GitHub Pages on a fork:

1. Go to Settings → Pages

2. Under "Build and deployment", select GitHub Actions

3. The workflow will deploy to https://.github.io/ai-feature-tracker/

Manual build

node scripts/build.js

Output files:

License

MIT - see LICENSE

Credits

Created by SnapSynapse for the AI training community.

With help from Claude Code, of course.


Found an error? Open an issue or submit a PR!