Skip to main content
The AI Coding Tool Settings tab is where you configure the analytics assumptions G360 uses when analyzing usage of your AI coding tools — things like expected savings from cost-optimization features, and the thresholds used to flag waste. This tab lives under Administration → Settings → AI Coding Tool Settings.
This is a different tab from the AI Coding Tool Settings sub-tab found under ROI Settings. That sub-tab configures per-seat cost and hours-saved figures for ROI; this tab configures the deeper analytics parameters (downgrade savings, waste thresholds, score weights) behind those numbers.
Underneath this tab, a row of tool tabs lets you switch between AI coding tools — currently Claude Settings is available.

​
Claude Settings

Claude Code Analytics Settings shows when it was last updated (for example, “11 Aug 2026, 07:45”) and is organized into several sections.

​
Model Downgrade

Controls when G360 considers a request eligible for automatic model downgrading (switching to a cheaper model) and how much that’s expected to save.

​
Savings Rates

Configures the expected cost savings from two specific cost-optimization behaviors.

​
High Waste Thresholds

Sets the cutoff percentiles G360 uses to flag usage as high-waste.

​
Score Weights

Configures how much weight different usage signals carry when G360 calculates an overall efficiency/usage score. Fields visible include:
The Score Weights section continues below what’s captured here — additional weight fields may appear further down the page. Scroll down within this section to see and configure all of them.
Once you’ve made your changes, click Save Settings in the top right to apply them, or Reset to revert all fields back to their last saved values.