Skip to content

Artifacts

Transform your AI conversations into a searchable knowledge base. Capture, organize, and retrieve code snippets, documentation, and reports with powerful search and categorization.

Artifacts Management automatically preserves substantial AI-generated content from your conversations, turning scattered outputs into an organized, searchable library. Never lose valuable code snippets or documentation again.

  • Never Lose Content: Auto-capture AI outputs forever
  • Instant Search: Full-text search across all artifacts
  • Smart Organization: Categorize by project, type, and status
  • MCP Integration: AI tools create and access artifacts automatically
  • Beautiful Previews: Markdown rendering with syntax highlighting

Artifacts are substantial pieces of AI-generated content:

  • Code snippets and functions
  • Documentation and guides
  • Data structures and schemas
  • Meeting summaries
  • Analysis reports
  • Technical specifications
  1. Navigate to Artifacts in the sidebar
  2. Click Create New Artifact
  3. Fill in the details:
    • Project: Organizational grouping (e.g., “my-app/backend”)
    • Slug: Unique identifier (auto-generated from title)
    • Title: Descriptive name
    • Description: Brief summary (optional)
    • Type: work_reports, static_contexts, or general
    • Content: Your artifact content (supports Markdown)
    • Status: active or expired
  4. Click Save

When AI tools are connected via MCP, they can automatically create artifacts during conversations:

// AI tools can create artifacts automatically
const artifact = {
project_name: "user/project",
slug: "api-documentation-v1",
title: "REST API Documentation",
content: "# API Endpoints\n\n## Users\n...",
type: "static_contexts",
status: "active"
}

Organize artifacts using project naming:

user/project-name
organization/repository
category/subcategory

Examples:

  • shaharia/vibexp-backend
  • personal/code-snippets
  • work/documentation

work_reports

  • Completed analyses
  • Status reports
  • Summary documents

static_contexts

  • Documentation
  • Code snippets
  • Technical specifications
  • Reference materials

general

  • Meeting notes
  • Brainstorming sessions
  • Miscellaneous content
  • active: Currently relevant artifacts
  • expired: Archived or outdated content

Change status anytime without deleting artifacts.

Search across titles, descriptions, and content:

Search: "authentication implementation"

Finds all artifacts mentioning authentication and implementation.

Filter by:

  • Project: Show artifacts from specific projects
  • Type: work_reports, static_contexts, or general
  • Status: active or expired
  • Creation Date: Date range filtering
  • Metadata: Custom metadata fields
  • Newest First: Recently created artifacts
  • Oldest First: Historical artifacts
  • Alphabetical: By title or slug
  • Most Relevant: Based on search query
  • List View: Quick overview with metadata
  • Detail View: Full content with formatting
  • Markdown Rendering: Beautiful syntax highlighting
  • Code Blocks: Language-specific formatting
  1. Open an artifact
  2. Click Edit
  3. Make your changes
  4. Save to update

Add custom metadata for enhanced organization:

{
"version": "1.0",
"language": "typescript",
"framework": "react",
"author": "team-frontend"
}

Access metadata in search and filtering.

  1. Select multiple artifacts
  2. Click Bulk ActionsDelete
  3. Confirm deletion
  1. Select artifacts
  2. Click Bulk ActionsUpdate Status
  3. Choose new status (active/expired)

Connected AI tools can create artifacts:

// Example: AI creates artifact during conversation
vibexp_io_create_artifact({
project_name: "user/backend-api",
slug: "error-handler",
title: "Error Handler Implementation",
content: "```typescript\n...\n```",
type: "static_contexts"
})

AI tools can search your artifacts:

// Search for specific content
vibexp_io_search_artifacts({
project_name: "user/backend-api",
search: "authentication",
limit: 10
})

Get specific artifacts by slug:

// Retrieve by project and slug
vibexp_io_get_artifact({
project_name: "user/backend-api",
slug: "error-handler"
})

Store reusable code snippets:

Project: personal/code-snippets
Type: static_contexts
Examples:
- "react-custom-hook-example"
- "api-error-handler"
- "database-connection-pool"

Maintain living documentation:

Project: company/main-app
Type: static_contexts
Examples:
- "architecture-overview"
- "deployment-guide"
- "api-reference"

Track completed work:

Project: client/project-x
Type: work_reports
Examples:
- "sprint-15-summary"
- "performance-analysis"
- "security-audit-report"
  • Use consistent slug patterns
  • Include version numbers for evolving content
  • Use descriptive, searchable titles
  • Group related artifacts by project
  • Use hierarchical project names
  • Keep project names short but clear
  • Use Markdown for formatting
  • Include context in descriptions
  • Tag with relevant metadata
  • Regular cleanup of expired artifacts
  • Use descriptive titles and descriptions
  • Include keywords in content
  • Add searchable metadata tags
  • Keep content focused and specific
Terminal window
# List artifacts
GET /api/v1/artifacts?project_name=user/project
# Get specific artifact
GET /api/v1/artifacts/{project_name}/{slug}
# Create artifact
POST /api/v1/artifacts
# Update artifact
PUT /api/v1/artifacts/{project_name}/{slug}
# Delete artifact
DELETE /api/v1/artifacts/{project_name}/{slug}

See API Keys for authentication.

Unlimited. Store as many artifacts as needed to build your knowledge base.

Yes. Export individual artifacts or entire projects in JSON or Markdown format.

Individual artifacts should be under 1MB. For larger content, consider splitting into multiple artifacts.

Not currently, but this feature is planned. For now, artifacts are private to your account.

Artifacts are stored indefinitely until you delete them. Use status “expired” to archive without deleting.