Snapshots Skill — AI-Configured Bug Capture

Snapshot configuration involves choosing between recording and streaming modes, setting up QA workflows, and managing sessions across builds. The snapshots skill gives your AI assistant the knowledge to configure the right mode for your team's workflow and environment.

What the skill does

When you ask your AI about snapshot configuration, it:

  1. Recommends the correct snapshot mode based on your use case (offline dev, real-time collaboration, device testing)
  2. Explains session management and status transitions
  3. Guides QA workflow setup (who captures, who views, how to share)
  4. Configures web console integration for team access

Example prompts

"Set up snapshots so QA testers can capture bugs and share them with developers"

"Should I use Recording or Streaming mode for our remote team?"

"Configure snapshot streaming for device testing but keep editor sessions local"

"How do I set up Jahro so my QA team can capture bugs on Android?"

Snapshot mode recommendations

The skill selects the mode based on your described workflow:

ScenarioRecommended modeWhy
Solo developer, testing locallyRecordingLogs stay on device until you decide to upload
Remote QA team, real-time collaborationStreaming (All)Logs appear in web console within ~5 seconds
Device testing with private editor sessionsStreaming (Except Editor)Streams from devices, records locally in Editor
Privacy-sensitive project, limited networkRecordingNo data leaves the device until explicitly uploaded

QA workflow the AI configures

When you describe a team testing scenario, the AI walks through:

  1. Capture — QA opens the Jahro console on device, taps Start Snapshot, reproduces the issue, taps Stop
  2. Share — QA copies the snapshot URL and shares it (Slack, Jira, email)
  3. Review — Developer opens the URL in the web console, sees logs, screenshots, and device context
  4. No install required for reviewers — the web console works in any browser

The skill also covers session naming conventions (so QA tags sessions with bug IDs or descriptions) and the 10-session local retention limit.

Web console integration

The skill explains how snapshots flow from device to web console:

  • Streaming mode sends data every ~5 seconds in chunks
  • Recording mode requires manual upload from the in-game Snapshots tab
  • Uploaded sessions appear at console.jahro.io under the configured project
  • Sessions are accessible to all team members with project access

Verification

After configuring snapshots:

  1. Open Tools → Jahro Settings and verify the snapshot mode matches your choice
  2. Start a snapshot from the in-game console on a test build
  3. If streaming: open the web console and verify logs appear within seconds
  4. If recording: stop the session, upload, and verify it appears in the web console
  5. Copy the session URL and open it in a different browser — confirm it loads

Frequently Asked Questions

Which snapshot mode should I start with? If you work solo or offline, start with Recording. If you have a QA team or remote collaborators, use Streaming (All) — it eliminates the manual upload step and gives near-real-time visibility.

Can the AI help set up a QA workflow from scratch? Yes. Describe your team structure and the AI will recommend a mode, explain the capture-share-review workflow, and configure session naming conventions.

Does the skill help with snapshot troubleshooting? For capture and upload issues, use the troubleshooting skill instead. The snapshots skill focuses on configuration and workflow, not diagnostics.

Last updated: April 2, 2026