Troubleshooting

Common issues, artifact reference, and getting help.

Common Issues

"vibe: command not found"

The CLI is not installed or not in your PATH.

Solution:
npm install -g @vibe-assurance/cli
# Verify installation
vibe --version
"Authentication failed" or "Token expired"

Your session has expired or credentials are invalid.

Solution:
# Clear and re-authenticate
vibe logout
vibe login
MCP tools not appearing in Claude Code

The MCP server may not be configured correctly.

Solution:
# Re-run setup
vibe setup-claude

# Restart Claude Code completely
# Check ~/.claude/mcp.json for vibeassurance entry
"Project not found" or "Access denied"

You may be trying to access a project you don't have access to.

Solution:
# List your projects
vibe projects

# Switch to a valid project
vibe project select
Vibe not being used when I ask for features

Vibe doesn't automatically intercept your prompts. You need to explicitly mention Vibe or its roles.

Solution:

Be explicit about wanting governance. Instead of "Add a logout button", say:

"Use the Vibe Implementation Planner to create a CR
for adding a logout button, then implement it."

Artifact Types

Vibe Assurance stores governance documents as artifacts:

Type ID Format Description
CR CR-YYYY-XXX Change Requests with implementation plans
RISK RISK-XXX Risk register entries with scoring
VULNERABILITY VUL-XXX Security vulnerabilities with OWASP categories
PLAN PLAN-YYYY-XXX Strategic plans with CR roadmaps
REPORT Custom Security reports and audit findings
POLICY POL-XXX Security policies and procedures
SOP SOP-XXX Standard Operating Procedures

Artifact Statuses

Status Description
Draft Work in progress, not yet approved
Active Approved and in effect
Completed Implementation finished (for CRs)
Closed Resolved or archived

Risk Scoring

Risks are scored using likelihood x impact:

Likelihood Scale (1-5)

Value Label Description
1RareLess than once per year
2UnlikelyOnce per year
3PossibleSeveral times per year
4LikelyMonthly occurrence
5Almost CertainWeekly or more frequent

Impact Scale (1-5)

Value Label Description
1InsignificantMinor inconvenience
2MinorLimited impact, quickly recoverable
3ModerateSignificant disruption
4MajorSevere impact, compliance implications
5CatastrophicCritical failure, major breach

Severity Mapping

Score Range Severity
1-4Low
5-9Medium
10-16High
17-25Critical

OWASP Categories

Vulnerabilities use OWASP Top 10 2021 categories:

Code Category
A01Broken Access Control
A02Cryptographic Failures
A03Injection
A04Insecure Design
A05Security Misconfiguration
A06Vulnerable Components
A07Authentication Failures
A08Data Integrity Failures
A09Logging Failures
A10SSRF

Getting Help

If you're still having issues: