Onboarding guide: your Optimize trial

This is the one guide to follow when your team starts its 21-day Optimize trial. An admin creates the organization and opens it to the team (Parts 1 and 2), then every developer installs the CLI and runs cdlx init (Parts 3 through 5). Nothing here changes how anyone works: your team keeps using the same coding tools they use today.

Budget about 5 minutes per developer, and five minutes up front for the admin steps.

Before you start

Have these ready and the whole thing goes smoothly:

• An org admin available for Parts 1 and 2 (five minutes, once).
• macOS or Linux with Homebrew on each developer machine.
• At least one supported coding tool installed per developer: Claude Code, Codex, and Cursor.
• Company email addresses. Signing in with a work email is what routes everyone into the same organization.

Part 1: Create the organization (admin, once)

Go to codelexica.com/auth/signup and sign up with Google or a magic link. You'll be asked for your name and an organization name; use your company name, since teammates will see it when they join.

Next, the "Let your team join automatically" screen offers to whitelist your company's email domain. Say yes. This is what lets teammates join by simply signing in with their work email, with no invites to send or track. (If you skip it, you can turn it on later; see Part 2.)

Finally, the plan picker. Click Start Optimizing. Your 21-day trial starts immediately, no credit card, and you'll land on the Savings dashboard with a banner counting down the days.

Part 2: Open the door for your team (admin)

In the dashboard, open Organization Settings and find the Allowed Email Domains card. Confirm your company domain is listed and auto-join is on. From then on, teammates sign in at the normal login page with their company email and land in your organization automatically.

Two things to know about auto-join:

• Public email providers (gmail.com, outlook.com, and the like) can't be whitelisted; it's for company domains only.
• Auto-join activates once at least one member with a verified email on that domain exists. As the admin who signed up with your work email, that's normally you.

Part 3: Install the CLI (every developer)

One command in a terminal:

• brew install codelexica/tap/cdlx

Part 4: Run cdlx init (every developer)

cdlx init is interactive and takes a couple of minutes. Here's the whole flow, in order:

• 1. Sign in. Your browser opens to confirm the device; if it doesn't, the terminal prints a URL and a short code to enter instead. Use your company email so auto-join places you in the right organization.
• 2. Approve the repository scan. The CLI looks for git repositories on your machine so it can suggest what to track. Nothing is tracked yet; this only builds the list.
• 3. Pick directories to track. You'll get a checklist, with your organization's repositories and anything with recent AI-tool activity surfaced first. Tracking a directory means Track meters the coding-agent sessions that run in it.
• 4. Connect Cursor (Cursor users only). If Cursor is detected you'll be prompted once to connect it. Claude Code and Codex need no extra step.
• 5. Say yes to Optimize. The last step offers to enable the Optimize sidecar: the part that actually cuts your spend. Say yes, then choose which of your tracked directories it should run in (all of them is a fine default).

What leaves each machine

Usage metadata only: token counts, model identifiers, tool-call names and result status, session timings, and repository fingerprints. Prompt text, tool arguments, and file contents never leave the machine; the tracking schema structurally can't carry them.

Part 5: Verify it's working

Three ways to confirm, from fastest to most thorough:

• cdlx doctor: the end-to-end health check. It verifies your login, watched directories, and sidecar wiring in one pass.
• cdlx watch status lists what's being tracked on this machine; cdlx sidecar status shows where the sidecar is active.
• The dashboard: live sessions appear on the LLM Usage page within a few minutes, and your usage history backfills with a progress indicator. On the Savings page, the rollout tracker counts up as each developer enables the sidecar.

Part 6: Prove it in week one

Don't wait until day 20 to look at results. In the first week, have one engineer run a paired A/B test on a real task from your backlog:

• cdlx ab-test run --task "Fix the flaky retry logic in the payments worker"

During the trial, and after

The Savings dashboard banner counts down the 21 days and tracks measured savings against your own baseline. Weekly briefings land by email and in the dashboard as your history builds.

When the trial ends, your organization reverts to free Track automatically: no charge, nothing to cancel, and your usage history and dashboard stay. If the numbers made the case, talk to us. Optimize is priced against measured savings, and if we don't save you money, you don't pay.

If something's stuck

• No usage after 15 minutes: run cdlx doctor, then start a fresh session in your coding tool.
• A teammate landed in the wrong organization or accidentally created a new one: they probably signed in with a personal email. Have them sign in again with their company email (see Part 2).
• The Optimize step never appeared in cdlx init: confirm the trial is active (the Savings page banner) and a supported tool is installed, then run cdlx sidecar enable.
• Anything else: email support@codelexica.com. A real person responds, usually within a few hours on business days.