RinaWarp Terminal Pro docs

Installation

Linux (available now)

1. Download .deb or AppImage from the download page.
2. Verify SHA256 using SHASUMS256.txt before install.
3. .deb: Install on Debian/Ubuntu. Updates are manual .deb reinstalls unless you switch paths.
4. AppImage: Portable build with in-app update checks when configured.
5. Launch Terminal Pro and open your repository folder.

macOS/Windows (unsigned beta preview)

Important: These beta builds may be unsigned and require OS security bypass steps. Production builds will be signed and notarized.

• Download the unsigned .dmg or .exe installer from the download page.
• macOS: Right-click the app and select "Open" to bypass Gatekeeper on first launch.
• Windows: Click "More info" → "Run anyway" if SmartScreen blocks the installer.
• These builds are for validation testing only — production builds will be signed.

Requirements

• 4 GB RAM minimum; 8 GB+ recommended for large monorepos
• Node.js 18+ and npm/pnpm in PATH for JavaScript/TypeScript projects
• Git recommended so you can review diffs and roll back
• Outbound network for package registries during repairs

First proof workflow

1. Open the repo. Select the project root folder.
2. Ask Rina. Describe what's broken. Rina follows the Observe → Plan → Approve → Execute → Proof workflow.
3. Review the plan. Read proposed file changes and the command plan.
4. Approve when prompted. High-impact steps pause until you confirm.
5. Verify proof. Confirm build, test, or boot checks show exit code 0.

If verification fails, read the failing command in the terminal and run another proof workflow pass with a narrower scope or after fixing network/registry access.

First repair (step by step)

1. Open the repo. Select the project root folder.
2. Ask Rina. Describe what's broken or what you want to change. Rina follows the Observe → Plan → Approve → Execute → Proof workflow.
3. Review the plan. Read proposed file changes and the command plan.
4. Approve when prompted. High-impact steps pause until you confirm.
5. Verify proof. Confirm build, test, or boot checks show exit code 0.

If verification fails, read the failing command output and run the proof workflow again with a narrower scope or after fixing network/registry access.

Supported frameworks

Best results on JavaScript/TypeScript stacks with standard npm tooling:

Other stacks may work when they use conventional build commands; unsupported cases should fail visibly rather than silently.

Permissions

What files can Rina modify?

Files inside the opened project and paths required to fix it (lockfiles, config, generated types). Rina should not modify arbitrary paths outside the project.

What commands can it run?

Package managers, compilers, test runners, and diagnostics relevant to the proof workflow (npm, pnpm, tsc, vite build, docker compose build, etc.).

Approval workflow

Safe changes can auto-apply on paid tiers. High-impact actions (mass deletes, publish, deploy hooks) require explicit approval in the UI.

Security model

• Local-first execution — The proof workflow runs against your disk unless a feature is explicitly labeled cloud.
• Command allowlisting — Proof workflow uses project-scoped tooling; unexpected system-wide commands should surface for approval.
• Rollback — Use git to revert bad changes; the proof report lists files touched so rollback is explicit.
• No secret exfiltration by default — .env values are not uploaded as part of the default proof workflow path; see privacy for telemetry scope.

Troubleshooting

Build failures after proof

Read the failing command in the terminal. Often one env var, flaky test, or remaining type error needs a second proof workflow pass.

Permission errors

Ensure the project is writable and package managers are not blocked by sandboxed directories. On Linux, avoid running as root inside the project tree.

Broken install

Re-verify checksums, try the other Linux artifact (.deb vs AppImage), or install missing GUI libraries on minimal images.

API/reference

Use these references when you need exact command, permission, or verification behavior instead of sales copy.

Problem-specific fix guides