# Investigate a rebooting iPhone from its panic logs

ID: discovery-bdeba0e44e192ef915572868
Category: Work & life admin
Reported agent: Claude
Evidence: User-reported
Source: [Reddit r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/comments/1xrevbv/claude_saved_my_old_iphone_from_becoming_ewaste)
Last reviewed: 2026-11-12

A user reports Claude identifying a light-sensor-related fault from an iPhone SE panic log. Physical inspection then revealed water damage at a connector.

Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.

## Prerequisites

- An accessible panic log from your own iPhone, model and repair history

## Connections and alternatives

- Paste the complete panic text with device details.
- Attach an existing log file that Claude can read.

## Workflow steps

- Read the panic and device history; separate observed messages from inferred causes.
- Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
- Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

## Expected result

A traceable fault hypothesis to investigate before replacing parts.

## Limitations

One user report, not independently tested. The author's custom patch left the phone tethered; it is not a general repair recipe.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Starter request

TASK: Investigate a rebooting iPhone from its panic logs

MY SETUP
- An accessible panic log from your own iPhone, model and repair history

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Read the panic and device history; separate observed messages from inferred causes.
2. Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
3. Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

EXPECTED RESULT
A traceable fault hypothesis to investigate before replacing parts.

LIMITATIONS
One user report, not independently tested. The author's custom patch left the phone tethered; it is not a general repair recipe.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Source notes

One user report, not independently tested. The author's custom patch left the phone tethered; it is not a general repair recipe. Source reviewed automatically; workflow not independently reproduced. Connection options require verification in your own agent.

## Stored structured recipe

{
  "goal": "Investigate a rebooting iPhone from its panic logs",
  "sources": [
    "Paste the complete panic text with device details.",
    "Attach an existing log file that Claude can read."
  ],
  "access": "An accessible panic log from your own iPhone, model and repair history",
  "trigger": "On demand",
  "steps": [
    "Read the panic and device history; separate observed messages from inferred causes.",
    "Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.",
    "Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes."
  ],
  "output": "A traceable fault hypothesis to investigate before replacing parts.",
  "guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
  "sourceNotes": "A user reports Claude identifying a light-sensor-related fault from an iPhone SE panic log. Physical inspection then revealed water damage at a connector.",
  "sourceStatus": "user-reported",
  "generated": true
}

## Agent adaptations

Available IDs: dots, grok-bot, instinct, muse

### ChatGPT Dots (dots)

Status: Needs verification
Tested: false

## Requirements

- An accessible panic log from your own iPhone, model and repair history

## Connections

- Paste the complete panic text with device details.
- Attach an existing log file that Claude can read.

## Steps

- Read the panic and device history; separate observed messages from inferred causes.
- Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
- Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

## Starter request

TASK: Investigate a rebooting iPhone from its panic logs

MY SETUP
- An accessible panic log from your own iPhone, model and repair history

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Read the panic and device history; separate observed messages from inferred causes.
2. Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
3. Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

EXPECTED RESULT
A traceable fault hypothesis to investigate before replacing parts.

LIMITATIONS
One user report, not independently tested. The author's custom patch left the phone tethered; it is not a general repair recipe.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Grok Bot (grok-bot)

Status: Needs verification
Tested: false

## Requirements

- An accessible panic log from your own iPhone, model and repair history

## Connections

- Paste the complete panic text with device details.
- Attach an existing log file that Claude can read.

## Steps

- Read the panic and device history; separate observed messages from inferred causes.
- Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
- Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

## Starter request

TASK: Investigate a rebooting iPhone from its panic logs

MY SETUP
- An accessible panic log from your own iPhone, model and repair history

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Read the panic and device history; separate observed messages from inferred causes.
2. Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
3. Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

EXPECTED RESULT
A traceable fault hypothesis to investigate before replacing parts.

LIMITATIONS
One user report, not independently tested. The author's custom patch left the phone tethered; it is not a general repair recipe.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Instinct (instinct)

Status: Needs verification
Tested: false

## Requirements

- An accessible panic log from your own iPhone, model and repair history

## Connections

- Paste the complete panic text with device details.
- Attach an existing log file that Claude can read.

## Steps

- Read the panic and device history; separate observed messages from inferred causes.
- Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
- Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

## Starter request

TASK: Investigate a rebooting iPhone from its panic logs

MY SETUP
- An accessible panic log from your own iPhone, model and repair history

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Read the panic and device history; separate observed messages from inferred causes.
2. Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
3. Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

EXPECTED RESULT
A traceable fault hypothesis to investigate before replacing parts.

LIMITATIONS
One user report, not independently tested. The author's custom patch left the phone tethered; it is not a general repair recipe.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Meta Muse (muse)

Status: Needs verification
Tested: false

## Requirements

- An accessible panic log from your own iPhone, model and repair history

## Connections

- Paste the complete panic text with device details.
- Attach an existing log file that Claude can read.

## Steps

- Read the panic and device history; separate observed messages from inferred causes.
- Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
- Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

## Starter request

TASK: Investigate a rebooting iPhone from its panic logs

MY SETUP
- An accessible panic log from your own iPhone, model and repair history

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Read the panic and device history; separate observed messages from inferred causes.
2. Quote the lines supporting each fault hypothesis. Ask what physical inspection could distinguish them.
3. Return a diagnostic brief and a non-destructive next check for a repairer. Stop before restores or firmware changes.

EXPECTED RESULT
A traceable fault hypothesis to investigate before replacing parts.

LIMITATIONS
One user report, not independently tested. The author's custom patch left the phone tethered; it is not a general repair recipe.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

## Complete JSON

https://agents.goodbot.guide/api/workflows/discovery-bdeba0e44e192ef915572868