The toolkit

All your AI tools. In one place.

Skills, harnesses, models, agent building and tracing, MCP access and guardrails that work inside Claude Code, Codex, Cursor and Copilot. One install, one contract.

Engineer home page showing monthly budget, new and retiring models, recent sessions and the skills catching on at the company. Demo data.
01 / Skills

On day one your team gets shared skills and sees which ones ship code.

Your best engineers are creating useful skills. Add their most helpful skills, hooks and agents to starter packs to help the rest of the team or make them optionally available. Codiedev helps keep them versioned, and shows which ones actually get used and lead to merged code.

Skills marketplace showing each team's skill usage and skills from other teams to adopt or fork. Demo data.
  • Starter packs. Bundle skills, hooks and agents for a role or team: new-engineer onboarding, ticket writing, PR review, test writing, QA. One install into Claude Code, Codex, Cursor, Copilot or Codie, with stable and beta channels.
  • Versioned registry. Every push is versioned. Teams that fork a skill see when the original moves on.
  • Curated marketplace. Vetted skills from reputable authors, cached in your own registry. Fork popular skills from other teams in one click.
  • Governance ladder. Promote skills from experimental to team standard to company standard, based on evidence instead of opinion.
  • Proof they ship. See which skills ran in the sessions that became merged PRs, including review and test skills on each PR.
02 / Harnesses

Keep your favorite harness or use ours.

Nothing changes for the engineer. Codiedev adds skills, capture and guardrails to the tools you already pay for, and fills the gaps those tools leave.

  • Claude Code
  • Cursor
  • Codex
  • GitHub Copilot
  • OpenCode
  • Pi

The tools you already pay for. Claude Code, Codex, Cursor and Copilot. Codiedev adds skills, session capture and security hooks behind the scenes.

Codie, our managed harness. Built on OpenCode. Every launch pulls your company's approved models and prices, so new models appear with no setup. Only have an Anthropic deal? Your engineers still get OpenAI and open models in Codie.

Any harness. pi, OpenCode, Crush and Grok CLI, locked to your approved models, with analytics to track adoption.

03 / Models and policy

Every new AI model, available the day it clears your security policy.

Set your rules once. We test new models daily against them, and admins get a weekly digest of the ones ready to switch on. Engineers only ever see what's approved.

Model catalog plotting approved models by price and context window, with new and retiring models. Demo data.
  • Failover. Requests reroute across approved providers on rate limits and outages, with daily route health.
  • Lifecycle. When a model retires, engineers get a suggested replacement and switch with one click.
  • Your keys, ours, or both. Connect your own AWS Bedrock, Vertex or Azure accounts and keep burning down those commits, then fill the gaps with models from Codiedev's vendor contracts and keys. No token markup either way.
04 / Agent building and tracing

Build reliable & cost efficient agents.

Your teams are building agents for code review, triage and more. Point them at Codiedev and the same policies, budgets and failover apply to them as to your engineers, with a full trace of every run.

Agent trace showing execution steps, detected failures, and the option to save a test case. Demo data.

Build agents

  • OpenAI-compatible LLM API. Swap the base URL in any OpenAI SDK. Streaming and tool calls included.
  • Direct to inference providers. Open models from Fireworks, Baseten and Together; closed models through Bedrock, Vertex and Azure.
  • Service keys for agents. Per-key model allowlist, monthly budget, rate limit, expiry and rotation.

Trace every run

  • Spend per agent and run. Cost, tokens and errors for every run, by workload and environment.
  • Run timelines. Step-by-step runs, prompts and failure detection.
  • Cheaper-model suggestions. See when another approved model would do the same work for less.
05 / MCP gateway Early access

MCP access and cost controls eliminate surprises.

Every developer's agents reach your business tools through one gateway, so you decide who can connect to what and how much they can spend.

MCP controls showing connector calls, cost per active person and oversized calls blocked. Demo data.
  • Team access. Turn each connector on per team. Everyone else can request access.
  • Spend guards. Monthly limits per person, a warning at 90%, and oversized calls blocked.
  • Cost visibility. Cost per active person and your heaviest users, with call sizes logged for audit.
What each engineer sees

Engineers see their own numbers, and a cheaper model that does the same work.

Every engineer gets a personal view of their sessions, limits, token use and merged work, plus what their teammates' most effective skills and models are. It's a coaching tool, not a scoreboard.

Developer model usage showing personal costs, tokens and model usage shares. Demonstration data.

Get a demo to see the full toolkit live.

We'll set up starter packs, approved models and guardrails for a pilot team, and show you what ships.

See Governance