AI AppSec Assistant

Documentation Index

Fetch the complete documentation index at: https://zeropath.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​

Overview

​

Key Capabilities

​

Autonomous Security Operations

• Triage findings — assess true/false positive status, evaluate severity, recommend remediation priority
• Investigate vulnerabilities — clone repos, review code paths, assess reachability
• Create patches — generate fixes, create PRs through the platform’s patch pipeline
• Threat modeling — analyze application architecture and identify attack surfaces
• SCA reachability — determine whether dependency vulnerabilities are actually exploitable in your code

​

Agent Teams

​

Self-Refinement

• Memory — stores and recalls decisions, team preferences, repo-specific knowledge, and investigation results across runs. Before each task, it searches memory for prior decisions on similar issues to stay consistent. After completing work, it saves key outcomes so future runs don’t re-investigate the same issues.
• Natural language rules — when it identifies a recurring pattern (e.g., repeated false positives from a specific code pattern), it can create scanner rules so the platform catches or suppresses similar findings automatically in future scans. This means the assistant’s triage decisions permanently improve the scanner’s accuracy.
• Recurring task context — for scheduled tasks, the assistant automatically receives the results of its last 3 runs. It uses this to track trends, build on prior work, and avoid starting from scratch each time.

​

Event-Driven Automation

• A scan completes → the assistant triages new findings and posts a summary
• A PR is blocked → the assistant reviews the blocking findings and suggests fixes
• A new CVE is discovered → the assistant assesses reachability across your repos
• A scan fails → the assistant investigates the error and notifies the team

​

Persistent Environment

• Recurring task directories — scheduled tasks get a persistent working directory at /data/recurring/<task-name>/. Each run creates a timestamped subdirectory, and the last 3 runs’ results are automatically provided as context to the next run. This lets the assistant track trends over time (e.g., “last week 12 critical findings, this week 8”).
• Cross-run memory — the assistant uses mem0 to store and retrieve organizational knowledge that persists indefinitely across all runs.

​

Controllability

• Global instructions — org-wide directives prepended to every task. Set policies like “always post in Slack before modifying records” or “escalate critical findings to @security-oncall.” Editable from the Settings tab or by the assistant itself via MCP tools.
• Event triggers — configure which platform events (scan complete, new vulnerabilities, etc.) automatically invoke the assistant, with customizable prompts per event type.
• Cron scheduling — the assistant can create and manage its own recurring schedules (e.g., “triage new findings every Monday at 9am”).
• Permissions — three granular permissions control who can view, manage, or run the assistant.

​

Dashboard

• Overview — At-a-glance stats (running jobs, jobs completed today, active schedules, active triggers, connected services), a live view of currently running jobs with real-time duration counters, and a feed of recent actions with AI-generated summaries describing the concrete actions taken (e.g., findings triaged, PRs opened, scans triggered).
• Activity — A searchable list of all conversations with AI-generated titles that summarize each conversation’s purpose. You can filter by source (Chat, Scheduled, Events, Slack) and click any row to open the full conversation thread with real-time streaming.
• Chat — Start new conversations or continue existing ones. The chat view includes a sidebar listing all conversations with search, source filtering (All, Chat, Scheduled, Event, Slack), and status indicators. Conversations from scheduled tasks and event triggers are read-only, while Slack-linked conversations direct you to reply in the original Slack thread. The assistant automatically receives the full conversation history when responding to follow-up messages, so it maintains context across multiple exchanges in the same thread.
• Schedules — Create and manage recurring tasks with cron expressions, templates, and repo/tag scoping.
• Triggers — Configure which platform events invoke the assistant, with per-trigger prompts and repo/tag scoping.
• Playbooks — Browse and manage reusable playbook templates that define multi-step workflows the assistant can execute. Playbooks provide a structured way to codify common security operations (e.g., triage runbooks, incident response procedures) so they can be triggered consistently across your team.
• Memory — View, search, edit, and delete the assistant’s stored organizational knowledge.
• Settings — Enable/disable the agent, configure Slack channel, set global instructions, and restart the assistant.

​

Getting Started

​

Enable the Assistant

1. Navigate to Assistant in the ZeroPath dashboard.
2. Go to the Settings tab.
3. Toggle the agent on.

​

Run Your First Task

1. Click the Ask button in the top right, or go to the Chat tab.
2. Type a message in the input at the bottom of the page to start a new conversation, for example:
   • “List all critical severity findings from the last scan and triage them”
   • “Review the latest PR scan results and flag any true positives”
   • “What are the top 5 most common vulnerability types across our repos?”
3. Watch the results stream in real-time. You can send follow-up messages in the same conversation thread.

​

Set Up Global Instructions

1. Go to the Settings tab.
2. Click “Show example” for a starting template.
3. Write your instructions. For example:

## Escalation & Approval

- Before modifying or deleting any issue, post a summary in Slack
  and wait for confirmation from a team member before proceeding.
- For critical or high severity findings, escalate to @security-oncall
  in #security-alerts with finding details and your recommended action.

## Memory

- At the start of every task, search memory for prior decisions about
  similar findings. Use existing decisions as precedent.
- After completing any triage or investigation, store the key decision
  and reasoning in memory for future reference.

## Pull Requests

- Never auto-merge pull requests. Create the PR, tag the repo owner,
  and post the PR link in Slack for review.

4. Click “Save Instructions”.

​

Event Triggers

​

Configuring Triggers

1. Go to the Triggers tab.
2. Click “Add trigger” on the event type you want, or toggle on an existing trigger:

3. Click “Edit prompt” to customize what the assistant does for each event.
4. Optionally scope each trigger to specific repositories or tags so it only fires for a subset of your codebase.

​

Inbound Webhooks

​

Creating an Inbound Webhook

1. Go to the Triggers tab.
2. Under the Webhooks section, click “Add trigger”.
3. Give the trigger a name and write a prompt template. Use {webhookBody} as a placeholder for the incoming request payload.
4. Click “Save”. ZeroPath generates a unique webhook URL with a secret token.

POST https://zeropath.com/api/agent/webhook/{triggerId}?secret={webhookSecret}

​

Example

A new bug bounty report was submitted. Analyze the report for validity,
check if the described vulnerability exists in our codebase, and post
your assessment to Slack.

Report contents:
{webhookBody}

{
  "title": "Open redirect in /auth/callback",
  "severity": "medium",
  "description": "The redirect_uri parameter is not validated..."
}

​

Scoping

​

Trusted Mode

• Trusted (default) — the assistant has full capabilities: shell access, file read/write, and all MCP tools. Use this for triggers driven by internal platform events (scan complete, new vulnerabilities, etc.) where the prompt content is controlled by your team.
• Untrusted — the assistant runs in a restricted mode with no shell access and no ability to read or modify sensitive configuration files. All MCP tools (ZeroPath platform, Slack, Linear, etc.) continue to work normally. Use this for triggers that process external input, such as inbound webhooks carrying payloads from outside your organization.

​

When to Use Untrusted Mode

• Inbound webhooks receiving payloads from external systems
• Triggers processing bug bounty reports, vendor advisories, or customer-submitted data
• Any trigger where {webhookBody} or other placeholders carry externally-authored text

​

What Changes in Untrusted Mode

​

Prompt Variables

​

Scheduled Tasks

​

Creating Schedules from the UI

1. Go to the Schedules tab and click “New Schedule”.
2. Choose a template to start from (Daily Triage, Weekly Security Digest, or SCA Monitoring), or build one from scratch.
3. Enter a name, select a cron expression (or use one of the built-in presets like “Weekdays at 9am UTC” or “Every hour”), and write the prompt that tells the assistant what to do.
4. Optionally scope the schedule to specific repositories or tags so the assistant only operates on a subset of your codebase.
5. Click Save. You can enable, disable, edit, or trigger any schedule manually from the list.

​

Creating Schedules via Chat

• “Create a weekly triage of all new findings every Monday at 9am”
• “Check for critical SCA vulnerabilities daily at midnight”
• “Run a security posture summary every Friday at 4pm”

​

Recurring Task Context

• Trend tracking — “Last week there were 12 critical findings, this week there are 8. Improvement in repos X and Y.”
• Incremental work — the assistant can pick up where it left off rather than starting from scratch.
• Audit trail — every run’s output is preserved for review.

​

Slack Integration

​

Setup

1. Ensure your organization has a Slack integration connected.
2. In the assistant Settings tab, enter the Slack channel ID where the agent should post.
3. The assistant will respond to @-mentions in channels and direct messages.

​

Talking to the Assistant

@ZeroPath Can you triage the 5 new critical findings from today’s scan?

What’s the current security posture across our repos?

​

Supported Actions

​

Jira & Confluence Integration

• Create remediation tickets linked to ZeroPath findings
• Look up existing tickets for context when triaging
• Search Confluence for architecture documentation to inform threat modeling and reachability analysis

​

Linear Integration

• Create remediation tickets directly from triage results
• Query existing tickets for remediation context

​

Custom MCP Servers

​

Memory

• Triage decisions and reasoning
• Team preferences and security policies
• Repository-specific knowledge (architecture, common patterns, known issues)
• Remediation plans and outcomes

​

Viewing and Managing Memory

• Search memories by keyword to find specific entries.
• Edit any memory entry inline to correct or refine what the assistant has stored.
• Delete individual entries that are no longer relevant.
• Clear all memories to reset the assistant’s organizational knowledge entirely. This action cannot be undone.

​

Best Practices

• The assistant automatically searches memory before each task and stores outcomes after. You don’t need to tell it to remember things explicitly.
• If you want to correct a past decision, tell the assistant directly — it will update its memory.
• Use global instructions to guide memory behavior (e.g., “always check memory for prior decisions on similar CVEs before triaging”).

​

Permissions

​

API Access

• Conversations — create conversations, send messages, list and search conversations, and archive/unarchive them
• Jobs — list, view, and cancel agent jobs with status and trigger filters
• Real-time streaming — subscribe to agent job messages via Server-Sent Events (SSE). You can stream a single job by ID or an entire conversation. In conversation mode, the stream automatically follows new jobs as they are created, sends idle events between jobs, and closes after 30 minutes with a timeout event so your client can reconnect
• Cron Schedules — create, update, delete, and manually trigger recurring schedules, with optional repository and tag scoping
• Event Triggers — create, update, and delete event-driven triggers with customizable prompts and scoping
• Trigger History — list past trigger executions with cursor-based pagination, and retrieve full job details including conversation messages
• Memory — list, edit, delete, and clear the assistant’s stored organizational knowledge
• Configuration — enable/disable the assistant, set the Slack channel, configure max concurrent runs, and manage global instructions