FAQ

Questions we hear.

Straight answers for compliance, leadership and engineering teams.

Compliance & security

For the people who answer to auditors.

Rules & compliance →
Is SightLine SOC 2 certified?

No. SightLine produces evidence for your own SOC 2 or ISO 27001 audit: change history, content-access logs, alerts and rule changes.

Does SightLine store our code?

It stores the text of agent edits and a short excerpt of each tool result, with known secrets scrubbed, for 30 days by default. It never stores the AI’s replies or your commit diffs; commits keep their metadata, subject line and who wrote each line, never the line text.

Who can see prompts and code?

Admins can open stored content, and every view of someone else’s content is logged.

How long is data kept?

Stored content is purged after 30 days by default (daily backups are kept up to 7 days more). Metadata such as sessions, commands and attribution stays for reporting.

Where is it hosted?

A single-tenant instance, hosted by Omega (US by default) or installed by Omega in any cloud environment you run.

Can we export evidence for auditors?

Yes. Admins can export CSV or JSON, including the access log and rule changes, without any prompts or code.

Leadership

For the people who need to know what AI is doing, and how much.

See the product →
What does SightLine measure?

Active developers, sessions, tool calls, files edited, blocked actions, and the share of every commit written by AI, by AI then edited, by people, or carried over, by developer, repo and model.

How is the AI share calculated?

SightLine classifies every committed line as written by AI, by AI then edited by a person, by people, or carried over from earlier work, and rolls it up by developer, repo and model. The AI share counts only lines an agent wrote exactly; lines written by AI and then edited are shown separately.

Which agents does it cover?

The Claude Code CLI and Codex, with the full code features. Any AI agent your company runs can also run through SightLine for the same record, rules and audit trail. Not Cursor or GitHub Copilot today.

How long does a rollout take?

Omega sets up capture once, for the whole team. Developers keep working as usual, and the record starts with their next session.

Does it slow developers down?

Developers work as usual; there’s no new tool to learn and no step added to their workflow.

Engineering

For the people who own the code and the developer workflow.

Rules reference →
What happens when a rule blocks something?

The agent’s action is stopped on the developer’s machine before it runs, and the agent sees a message such as “Blocked by SightLine policy: .env.production is a protected path.” The alert appears on the Alerts page.

What if SightLine is down?

Rules fail safe: machines keep their last rules and never block by mistake. Omega monitors hosted instances and can switch capture off in one step while service is restored.

Does it work in IDE extensions, Cursor or Copilot?

SightLine covers the Claude Code CLI and Codex today. IDE extensions, Cursor and Copilot aren’t covered.

How are developers identified?

By their Claude or Codex account email, falling back to git. Admins can merge identities, and sessions that can’t be matched are flagged.

Will developers see this as surveillance?

Admins’ views of developers’ content are logged. The point is a shared record of what agents did, not keystrokes or screens.