Files
ra-h-os/scripts
“BeeRad”andClaude Opus 4.5 0e6bf12ad3 fix: OS release prep - bootstrap script, deps, docs
- Fix bootstrap script (.env.example.local → .env.example)
- Fix @langchain/core version conflict (^1.0.1 → ^0.3.0)
- Add settings:open event listener for LocalKeyGate button
- Pin Next.js to 15.1.3 (was "latest")
- Default runtime to 'local' mode
- Remove desktop app references from UI text
- Rewrite MCP docs for web-only context
- Add SECURITY.md, CODE_OF_CONDUCT.md, CHANGELOG.md
- Add docs/README.md, docs/TROUBLESHOOTING.md
- Update README with platform support table

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-30 12:24:56 +11:00
..

RA-H Scripts

Utility scripts for managing the RA-H knowledge management system.

Directory Structure

scripts/
├── database/           # Database management
│   ├── backup.sh      # Create database backups
│   └── restore.sh     # Restore from backups
├── helpers/           # Helper management (CRITICAL - used by API)
│   ├── duplicate-helper.js  # Create new helpers
│   └── delete-helper.js     # Remove helpers
└── migrations/        # Completed one-time migrations
    └── cleanup-dimensions.sql

Database Scripts

Create a Backup

npm run backup
  • Creates timestamped backup in /backups/ folder
  • Example: rah_backup_20250902_102846.sql
  • Includes all nodes, chunks, edges, dimensions

Restore from Backup

npm run restore backups/rah_backup_20250902_102846.sql
  • ⚠️ WARNING: Replaces entire database
  • Requires confirmation before proceeding
  • Shows verification after restore

List Backups

ls -lt backups/

Helper Scripts

⚠️ CRITICAL: These scripts are used by the API at runtime. DO NOT modify or delete.

Create New Helper

Called automatically by the API when creating helpers through the UI.

node scripts/helpers/duplicate-helper.js "HelperName"

Delete Helper

Called automatically by the API when deleting helpers through the UI.

node scripts/helpers/delete-helper.js "helper-id"

What Gets Backed Up

  • All nodes (42,000+ knowledge items)
  • Content chunks and embeddings
  • Node connections/edges
  • Dimensions and metadata
  • Database schema and indexes

Notes

  • Backups typically ~250MB for 40k+ nodes
  • Store backups safely - they contain your entire knowledge base
  • Helper scripts are integrated with the application - modify with caution