Is it safe to use AI agents on your project with Byoi
Boundaries, secrets, and guarantees that make the Bring Your Own model trustworthy for managing an AI project.
updated 2026-07-10
Security in Byoi starts with clear boundaries: identity separate from Git, content separate from the administrative database, secrets separate from the repository, and AI always traceable.
Mental model
Byoi separates identity, Git access, project content, and AI keys. Login confirms who you are. Git installation defines which repositories can be accessed. Content lives in Git. Secrets stay encrypted in the administrative database.
Git access
Every Git integration goes through a provider interface. Product logic should not depend directly on GitHub SDKs, URLs, or internal shapes. This reduces coupling and makes auditing easier.
Repository writes
Every relevant write uses an expected SHA to detect conflict. If a file changed outside Byoi, the product should treat it as a conflict, not silently overwrite it.
Database/repo boundary
The administrative database does not become a project copy. That separation reduces breach impact, makes auditing easier, and keeps exit simple: useful content is already in the user repository.
Secrets
AI keys, tokens, and credentials should not appear in repository files. Keys added to Byoi are encrypted and always selected with user and project scope.
AI with trace
Every AI output is a proposal. The human presses the button. The product should show the model, key, or provider used and visually mark AI-touched content with the --ai color.
Frequently asked questions
Can an AI agent write to my repository without my approval
No. Every AI output in Byoi is treated as a proposal. Relevant repository writes require an explicit user action, and every write uses the file's expected SHA to detect conflict instead of silently overwriting it.
How does Byoi isolate my Git access from other users
Every Git integration goes through a single provider interface, without GitHub SDKs or internal URLs scattered across the product. That reduces coupling and makes it easier to audit who can access which repository.