One file defines your
AI context boundary

Audit the repo. Keep sensitive files out of AI context.
Let agents work with the rest.

curl -fsSL https://install.offsend.io/cli | bash
Your project flows through .offsend.yml into AI Context, with sensitive files blocked

Supported tools

  • Cursor
  • Codex
  • Windsurf
  • Claude Code

Runtime gatesCursor, Codex, Windsurf, Claude Code

Ignore-file supportGitHub Copilot, Continue, Gemini, LLM, Aider, Cline, Roo, Zed, Cody

AI context enters through more than prompts

Coding agents can read workspace files, follow file references, run shell commands, call tools, spawn subagents, and retain local transcripts.

Offsend sits between folders, files, shell, tools, history, and prompts that feed AI context

A repository needs boundaries across all of these paths — not only for committed files.

Check a repository

A context policy that belongs to the repository

.offsend.yml keeps AI-context rules visible, reviewable, and versioned with the project.

Project tree with .offsend.yml at the repository root

Audit, protect, gate, and verify — all from the local CLI.

curl -fsSL https://install.offsend.io/cli | bash

after install — quick start

1.offsend show# shows which sensitive paths may enter AI context
2.offsend init# creates repository policy
3.offsend protect# adds missing context boundaries
4.offsend hook install# installs runtime gates
Read the CLI docs

FAQ

What does Offsend protect?

Offsend is an open-source, local-first boundary layer for AI coding agents. One .offsend.yml file defines which sensitive paths should stay out of AI context, and supported runtime gates check prompts, file reads, shell commands, MCP arguments, and local transcripts.

Is Offsend a secret scanner?

Offsend includes content scanning (offsend check) for keys, tokens, and similar patterns in files, staged diffs, and stdin. Its primary job is still the AI context boundary — path policy, AI ignore sync, and runtime gates — not full git-history leak forensics or a cloud sandbox. Use it alongside Gitleaks, TruffleHog, or GitHub secret scanning when you need deep history coverage.

Does Offsend upload my code?

No. CLI checks run locally. Repository policies stay in the repo. Local history is audited locally. No cloud scanning is required.

Does one .offsend.yml guarantee that AI cannot read a file?

No. Offsend is defense-in-depth, not a guarantee. AI ignore rules remain the primary workspace exclusion, runtime gates cover supported paths, and some agent or tool paths may remain outside individual hooks.

Where should I start?

Install the CLI with curl -fsSL https://install.offsend.io/cli | bash, then run offsend show, offsend init, and offsend protect. If you want a quick look without installing, use Check on a public GitHub repo.

What is Radar?

Radar researches AI-context risk signals across public repositories without reading file contents. Visit radar.offsend.io for the latest report.

Surfaces

CLI for repos. macOS, extension, and GitHub Action for the other paths.

Offsend CLI terminal icon

CLI

Audit paths, write .offsend.yml, install local hooks.

Install CLI
Offsend app icon in the macOS Dock

Desktop

Check files, folders, and clipboard text before sharing them with AI tools.

Download for macOS
Offsend browser extension toolbar icon

Browser Extension

Detect and mask sensitive values before browser prompts or attached files are sent.

Install extension
GitHub Actions icon for Offsend CI checks

GitHub Action

Run the same offsend check in CI before code lands.

Add to CI
Checklist graphic for Offsend online repository check

Check

Run a fast repository audit without installing the CLI.

Check repository
Radar graphic for Offsend AI-context research

Radar

Research showing AI-context risk signals across public repositories.

Read latest report