- LLM Settings — covered in this guide.
- AI Coding Tool Settings — covered separately.
LLM Settings
This sub-tab lets you configure, per LLM provider, how much that provider’s tokens cost and how they compare to the cost of a human doing the same work manually. G360 uses these figures to calculate the ROI of your LLM usage.Understanding the table
Adding a new LLM setting
Click + Add LLM Setting in the top right to open the Add LLM Settings form. All fields sit under LLM Information:Together, these fields let G360 compare what it costs to run a task through this LLM (Input/Output Token Price × tokens used) against what it would have cost to do that work manually (Human Processing Speed × Developer Hourly Cost) — which is how the ROI figures elsewhere in the dashboard are calculated.
AI Coding Tool Settings
Switch to the AI Coding Tool Settings sub-tab to configure the same kind of cost and ROI parameters, but for AI coding assistants rather than raw LLM providers. Within this sub-tab, a row of tool tabs — GitHub Copilot, Cursor, Claude Code — lets you switch between the tools you’ve connected. Selecting a tool updates the page heading (for example, “GitHub Copilot Settings”, “Cursor Settings”, “Claude Code Settings”) and shows that tool’s configuration below.Understanding the table
G360 uses Hours Saved / User / Day together with Dev. Hourly Cost to estimate the dollar value this tool returns per user per day, and compares that against Per Seat Cost to calculate the tool’s ROI — the same logic used for LLM Settings, just measured in hours saved rather than tokens processed.

