| Prompt-level session capture | Reads local Cursor and Claude Code session files directly via the Tetriz Desktop App, and scores six prompt-quality dimensions. | The AI Impact view consolidates vendor-API spend, usage, and GitHub/Jira work data, with no IDE-level or prompt-level capture. |
| Session-to-outcome attribution | A four-signal cascade linking specific sessions to specific pull requests, with confidence scores. | Work metrics connect cost to initiatives and pull requests, not to the session that produced the code. |
| Harness setup visibility | Inventories installed skills, sub-agents, and hooks per engineer, and flags silent conflicts. | No public documentation of IDE-side AI-configuration inventory. Its AI and MCP surface queries existing metrics rather than a harness inventory. |
| Weekly coaching loop | The Session Quality Score refreshes weekly and returns directly to the engineer who ran the session, aimed at compounding better prompting habits week over week. | Deliberately team-level only, by design. Rollups don't return an individual, consent-based coaching signal to the engineer. |