Secure every action
your AI agents take.

No. Code scanning runs entirely locally. Only lightweight metadata (issue type, severity, line number, and project history) is synced to the dashboard. Your raw source never leaves your environment.

• Local scanner keeps all source files on your machine
• Dashboard sync: issue type, severity, line number, and history only
• Agent payloads are redacted before any logging
• Permission decisions sync as metadata, not as code

Agent Control is VibeLint's permission layer that decides, in real time, whether an agent action should be allowed, blocked, or escalated for human approval. Without it, AI agents can read, write, or delete sensitive resources with no oversight.

• Define per-agent or per-project permission policies
• Gate any tool call: file writes, API calls, database mutations, shell commands
• Three decision outcomes: Allow, Block, or Require Approval
• Policies take effect immediately without restarting your agent

Policies can be scoped to an individual agent identity, a project, a tool category, or a specific action pattern, giving you precise control without writing custom middleware.

• Identity-level: restrict what a specific agent or workflow is allowed to do
• Tool-level: blanket allow/block for shell, filesystem, network, or database tools
• Pattern-level: block writes to /secrets, /prod, or any path pattern you define
• Pending approvals expire on a policy timeout (default 30 minutes, up to 24 hours)

Safe work continues uninterrupted. Risky work is stopped or paused with a structured decision your team can act on immediately.

• Allow: action proceeds normally with a log entry
• Block: action is denied with a clear reason returned to the agent
• Require Approval: action waits in queue until a human reviews it from the dashboard
• All decisions are timestamped and stored in Agent Logs for audit

Every agent action, permission decision, and code scan result is captured in a structured, searchable audit trail, so you can see exactly what happened, when, and why.

• Action logs: tool call, input summary, outcome, and timestamp per agent
• Decision logs: Allow / Block / Approval result with the matching policy rule
• Code scan logs: file path, issue type, severity, and detector ID
• All logs are correlated by agent identity and session for easy tracing

Yes. The dashboard provides full-text search across all log dimensions. Logs can be filtered by agent, project, time range, or decision outcome and exported for compliance reports or incident reviews.

• Full-text search across action, tool, and outcome fields
• Filter by agent identity, project, severity, or date range
• Export logs as JSON or CSV for your SIEM, audit system, or incident review
• Retention is fixed by plan: 7 days Free, 30 Pro, 90 Max

Standard logs capture system events. VibeLint's agent logs are purpose-built for agentic workflows, capturing intent, action, and governance decision in a single correlated record.

• Agent identity attached to every entry (not just process or IP)
• Permission decision correlated with the exact action that triggered it
• Redacted payloads ensure sensitive data is never stored in logs
• Timeline view reconstructs a full agent session at a glance

VibeLint scans code as agents write or edit it, catching the vulnerability classes most common in AI-generated output before they ever reach your codebase.

• Hardcoded secrets, API keys, and credential leaks
• SQL / NoSQL injection and broken authentication patterns
• Unsafe configuration, open CORS policies, and risky execution paths
• Prompt injection and LLM-output checks on Pro and Max

Scans run before risky writes are committed, acting as a gate. If an issue is found, the write is blocked or flagged for review, not just reported after the fact.

• Pre-write interception via MCP tool-call hook
• Blocking mode: unsafe code is stopped before it lands on disk
• Warning mode: code is written but flagged for immediate review
• Scan results show in the editor on the next check; metadata syncs to the dashboard after signup

VibeLint complements your existing SAST and SCA tools by adding a real-time gate at the AI write layer, the gap most scanners miss because they run after code is already committed.

• Closes the pre-commit gap left by post-commit scanners
• Export agent logs as JSON or CSV from the dashboard
• Works alongside Snyk, SonarQube, Semgrep, and similar tools
• No migration required. Add VibeLint as an extra layer, not a replacement

Most people finish the first MCP connect in a few minutes after signup. VibeLint is built for the AI coding and agent stack you already use, not something new to migrate into.

• IDEs and coding agents via MCP: Cursor, Claude Code, Codex, Windsurf, and similar
• Workflow agents that call an HTTP permission or logging layer
• Runtimes and SDKs: LangGraph, CrewAI, and custom agent loops
• Copy the setup snippet from your dashboard, with no config file to maintain

Free is local code scanning plus a small dashboard sync budget: 1 agent, 100 action logs per month, 1 policy, and no approval queue. Upgrade to Pro when you need permissions, approvals, and full agent logs.

• Free: local MCP scanning, unlimited local protected checks, core detectors, 1 agent, 100 logs, 1 policy, 0 approvals
• Pro: agent identities, action logs, permission policies, approvals, and full detector coverage
• Upgrade only when you need control and visibility across agents and workflows