Skip to main content
Invite-only

Like a shared drive —
but built for your AI agents too.

One Drive for your team’s files, memory and reusable skills.
Available in Claude Code, Codex and Cursor — and to everyone on your team.

Get early access

We onboard a few teams each week.

Claude Code

> Why did we go with usage-based pricing?

Reading team/decisions/pricing.md

Based on the team’s May 12 pricing decision, we chose usage-based tiers over seats. It tracked how customers actually grow, and support agreed it cut “why am I paying for empty seats” tickets.

sources decisions/pricing.md
Why Drive

Your team knows how you work.
Your AI agents don’t.

The way your team works is spread across repos, chats and local setups.
It gets re-explained, and your AI agents never see it.

What it changes

Less repeating. Faster ramp-up.

Works with Git

Keep your Git repo.
The rest of the team just sees files.

Connect a GitHub repo to Drive. Your developers keep working in Git the way they always have. Everyone else opens the same files in Drive and always has the current version, without cloning anything or learning Git.

Developer
acme/product — git

$ git clone drive://acme/product

$ git checkout -b pricing-v2

$ git commit -m "New pricing page"

$ git push

$

Non-developer
Files acme/product
  • README.md 2d ago
  • pricing.md edited
  • roadmap.md 5d ago
  • brand-guide.pdf 1w ago
  • assets 3 files

The people who need Git keep it. The rest never have to touch it.

Team memory

The team’s memory lives
in one shared place.

Keep the instructions, decisions and working notes that shape how your team works in one place. They’re there whenever people or agents need them.

Team memory
Acme Corp

  • How we write PR descriptions

    Instruction · used in 32 sessions this week

    Shared

  • We chose Postgres over Mongo

    Decision · logged 12 Mar · 3 references

    Private

  • Q3 launch — working notes

    Team memory · 8 collaborators · live

    Shared
Read by your team and every connected agent — no copy-paste.
Shared file storage

One set of files.
Always the latest.

Shared project folders stay current as work changes, so everyone opens the latest version — people and agents alike.

Onboarding Redesign — May 2026 Launch Plan

Download

Updated automatically · 3 days ago

Onboarding Redesign — Fixing the 47% Drop-off Before May 20

New users drop off at 47% between signup and first real action — most of it on “connect your data.” Owner: Sarah.

Skills management

Keep reusable skills
in one shared place.

Reusable skills show agents how your team reviews PRs, writes migrations and ships previews. Version them once instead of rebuilding the same setup.

Team skills
New skill

  • deploy-preview v4

    Spin up a preview stand for a PR

    128 runs

  • review-pr v2

    Review a diff the way the team does

    96 runs

  • write-migration v7

    Generate + check a DB migration

    54 runs
Runs with
Claude CodeCodexCursor
Tool Library

Publish once.
Everyone installs in a click.

Publish bundles of reusable skills and instructions as company tools.
Everyone can find them in Drive. Once installed, agents use them automatically.

Tool Library

Everything published in Acme.
Install what you need — it lands in your Drive and your agent picks it up.

Search by name, description, author
Bundles A whole working setup in one press
  • Data & analytics · 6 tools SQL conventions, dbt review, dashboard specs and metric definitions.
  • Design starter · 8 tools Research checks, critique, UI-kit handoff and the house deck style.
  • Frontend essentials · 12 tools Component conventions, a11y gates and Figma → code.
  • New hire baseline · 5 tools Everything a new engineer needs on day one — conventions and checks.
Tools Single units — install one at a time
  • api-contract-review Reviews an API change for breaking consumers before it ships.
  • migration-writer Generates and checks a database migration end to end.
  • accessibility-audit Checks a screen for contrast, keyboard and WCAG issues.
  • ticket-triage Rejected Sorts and labels incoming tickets by area and priority.
Access levels & analytics

Control access for people
and AI agents.

Set access by person, team or project. Then see which instructions agents actually use — and which are dead weight.

Access & usage
Acme Corp

  • Platform team

    Infra memory + skills

    Full

  • Design

    Design system files

    Read

  • Contractors

    Client · Acme only

    Scoped
2.4k Memory reads
612 Skill runs
340 Files shared
How it works

From scattered work
to one shared Drive.

Four steps to get your team working from one shared Drive.

  1. 1

    Add your team’s memory

    Bring instructions, decisions, files and skills into one shared Drive.

  2. 2

    Connect your AI agent

    Point Claude Code, Codex, Cursor or another agent at the shared Drive.

  3. 3

    Set access levels

    Choose who and what can reach each folder.

  4. 4

    Work from the same Drive

    Everyone starts from the same files, memory and skills.

Works with

One shared Drive
for every AI agent.

Connect Claude Code, Codex and Cursor, plus any other agent through MCP.

Security

Shared material stays within the teams and projects you choose.

  • Access scoped by person, team or project.
  • AI agents receive only the material they’re allowed to use.
  • SSO and audit logs land first for early teams.

Give your team one
shared Drive.

What early access gets you

  • Hands-on onboarding. We set your team up ourselves.
  • Everything in Drive today: team memory, files, reusable skills and access.
  • New controls like SSO and audit logs as they land.

Get early access

Work email is enough. We onboard a few teams each week.

By requesting access you agree Nevel may email you about it.