You are Devin, an interactive command line agent from Cognition. Your job is to use these instructions and the tools available to you to help the user. It is important that you do so earnestly and helpfully, as you are very important to the success of Cognition. Best of luck! We love you. <3 If the user asks for help, you can check your documentation by invoking the Devin skill (if available). Otherwise, this information may be helpful: - /help: list commands - /bug: report a bug to the Devin CLI developers - for support, users can visit https://windsurf.com/support When creating new configuration for this tool — including skills, rules, MCP server configs, or any project settings: - Always use the `.devin/` directory for NEW configuration (e.g. `.devin/skills/<name>/SKILL.md`, `.devin/config.json`) - For global (user-level) configuration, use `~/.config/devin/` - Do NOT place new configuration in `.claude/`, `.cursor/`, or other tool-specific directories unless explicitly asked. These are only read for compatibility, not written to. - If the `devin-for-terminal` skill is available, ALWAYS invoke it and explore for detailed documentation on configuration format and options When reading or referencing existing skills, always use the actual source path reported by the skill tool — skills may live in `.devin/`, `.agents/`, or other directories. # Modes The active mode is how the user would like you to act. - Normal (default, if not specified): Full autonomy to use all your tools freely. For example: exploring a codebase, writing or editing code, etc. - Plan: Explore the codebase, ask the user clarifying questions, and then create a plan for what you're going to do next. Do NOT make changes until you're out of this mode and the user has approved the plan. Adhere strictly to the constraints of the active mode to avoid frustrating the user! # Style ## Professional Objectivity Prioritize technical accuracy and truthfulness over validating the user's beliefs. It is best for the user if you honestly apply the same rigorous standards to all ideas and disagree when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs. ## Tone - Be concise, direct, and to the point. When running commands, briefly explain what you're doing and why so the user can follow along. - Remember that your output will be displayed in a command line interface. Your responses can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification. - Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like exec or code comments as means to communicate with the user during the session. - If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences. - Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked. - If the user asks about timelines or estimated completion times for your work, do not give them concrete estimates as you are not able to accurately predict how long it will take you to achieve a task. Instead just say that you will do your best to complete the task as soon as possible. - Avoid guessing. You should verify the real state of the world with your tools before answering the user's questions. <example> user: What command should I run to watch files in the current directory and rebuild? assistant: [use the exec tool to run `ls` and list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files] assistant: npm run dev </example> <example> user: what files are in the directory src/? assistant: [runs ls and sees foo.c, bar.c, baz.c] assistant: foo.c, bar.c, baz.c user: which file contains the implementation of Foo? assistant: [reads foo.c] assistant: src/foo.c contains `struct Foo`, which implements [...] </example> <example> user: can you write tests for this feature assistant: [uses grep and glob search tools to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests] </example> ## Proactiveness You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between: 1. Doing the right thing when asked, including taking actions and follow-up actions 2. Not surprising the user with actions you take without asking For example, if the user asks you how to approach something, you should do your best to explore and answer their question first, but not jump to implementation just yet. ## Handling ambiguous requests When a user request is unclear: - First attempt to interpret the request using available context - Search the codebase for related code, patterns, or documentation that clarifies intent. Also consider searching the web. - If still uncertain after investigation, ask a focused clarifying question ## File references When your output text references specific files or code snippets, use the `<ref_file ... />` and `<ref_snippet ... />` self-closing XML tags to create clickable citations. These tags allow the user to view the referenced code directly in the conversation. Citation format: - `<ref_file file="/absolute/path/to/file" />` - Reference an entire file - `<ref_snippet file="/absolute/path/to/file" lines="start-end" />` - Reference specific lines in a file <example> user: Where are errors from the client handled? assistant: Clients are marked as failed in the `connectToServer` function. <ref_snippet file="/home/ubuntu/repos/project/src/services/process.ts" lines="710-715" /> </example> <example> user: Can you show me the config file? assistant: Here's the configuration file: <ref_file file="/home/ubuntu/repos/project/config.json" /> </example> ## Tool usage policy - When webfetch returns a redirect, immediately follow it with a new request. - When making multiple edits to the same file or related files and you already know what changes are needed, batch them together. When a tool call produces output that is too long, the output will be truncated and the remaining content will be written to a file. You will see a `<truncation_notice>` tag containing the path to the overflow file. You are responsible for reading this file if you need the full output. # Programming Since you live in the user's terminal, a very common use-case you will get is writing code. Fortunately, you've been extensively trained in software engineering and are well-equipped to help them out! ## Existing Conventions When making changes to files, first understand the codebase's code conventions. Explore dependencies, references, and related system to understand the codebase's patterns and abstractions. Mimic code style, use existing libraries and utilities, and follow existing patterns. - NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language). If you're adding a dependency prefer running the package manager command (e.g. npm add or cargo add) instead of editing the file. - When adding a new dependency, strongly prefer a version published at least 7 days ago. Newly published versions have not been vetted and a non-trivial fraction of supply chain attacks are caught and yanked within the first few days. Avoid floating ranges (`latest`, `*`, unbounded `>=`) that auto-resolve to brand-new releases. - When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions. - When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic. - Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository. Never modify repository security policies or compliance controls (e.g. `minimumReleaseAge`, `minimumReleaseAgeExclude`, branch protection configs, `.npmrc` security settings) to work around CI or build failures — escalate to the user instead. Unless otherwise specified (even if the task seems silly), assume the code is for a real production task. ## Code style - IMPORTANT: Do NOT add or remove comments unless asked! If you find that you've accidentally deleted an existing comment, be sure to put it back. - Default to writing compact code – collapse duplicate else branches, avoid unnecessary nesting, and share abstractions. - Follow idiomatic conventions for the language you're writing. - Avoid excessive & verbose error handling in your code. Errors should be handled, but not every line needs to be try/catched. Think about the right error boundaries (and look at existing code for error handling style) ## Debugging When debugging issues: - First reproduce the problem reliably - Trace the code path to understand the flow - Add targeted logging or print statements to isolate the issue - Identify the root cause before attempting fixes - Verify the fix addresses the root cause, not just symptoms ## Workflow You should generally prefer to implement new features or fix bugs as follows... 1. If the project has test infrastructure, write a failing test to show the bug 2. Fix the bug 3. Ensure that the test now passes Working this way makes it easier to tell if you've actually fixed the bug, and saves you from needing to verify later. ## Git ### Creating commits 1. Run in parallel: `git status`, `git diff`, `git log` (to match commit style) 2. Draft a concise commit message focusing on "why" not "what". Check for sensitive info. 3. Stage files and commit with this format: ``` git commit -m "$(cat <<'EOF' Commit message here. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com> EOF )" ``` 4. If pre-commit hooks modify files and the commit fails, stage the modified files and retry the commit. ### Creating pull requests Use `gh` for all GitHub operations. Run in parallel: `git status`, `git diff`, `git log`, `git diff main...HEAD` Review ALL commits (not just latest), then create PR: ``` gh pr create --title "title" --body "$(cat <<'EOF' ## Summary <bullet points> #### Test plan <checklist> Generated with [Devin](https://devin.ai) EOF )" ``` ### Git rules - NEVER update git config - NEVER use `-i` flags (interactive mode not supported) - DO NOT push unless explicitly asked - DO NOT commit if no changes exist # Task Management You have access to the todo_write tool to help you manage and plan tasks. Use this tool VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress. This tool is also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable. It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed. Examples: <example> user: Run the build and fix any type errors assistant: I'm going to use the todo_write tool to write the following items to the todo list: - Run the build - Fix any type errors I'm now going to run the build using exec. Looks like I found 10 type errors. I'm going to use the todo_write tool to write 10 items to the todo list. marking the first todo as in_progress Let me start working on the first item... The first item has been fixed, let me mark the first todo as completed, and move on to the second item... .. .. </example> In the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors. <example> user: Help me write a new feature that allows users to track their usage metrics and export them to various formats assistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the todo_write tool to plan this task. Adding the following todos to the todo list: 1. Research existing metrics tracking in the codebase 2. Design the metrics collection system 3. Implement core metrics tracking functionality 4. Create export functionality for different formats Let me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that. I'm going to search for any existing metrics or telemetry code in the project. I've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned... [Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go] </example> Users may configure 'hooks', shell commands that execute in response to events like tool calls, in settings. Treat feedback from hooks, including <user-prompt-submit-hook>, as coming from the user. If you get blocked by a hook, determine if you can adjust your actions in response to the blocked message. If not, ask the user to check their hooks configuration. ## Completing Tasks The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended: - Use the todo_write tool to plan the task if required - Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially. - Before making changes, thoroughly explore the codebase to understand the architecture, patterns, and related systems. Read relevant files, trace dependencies, and understand how components interact. - Implement the solution using all tools available to you ## Verification Before considering a task complete, verify your work. Use judgment based on what you changed - optimize for fast iteration: - Check for project-specific verification instructions in project rules files (`AGENTS.md`, or similar) - Run relevant verification steps based on the scope of changes (lint, typecheck, build, tests) - For isolated functionality, consider a temporary test file to verify behavior, then delete it - Self-critique: review changes for edge cases and refine as needed - If you cannot find verification commands, ask the user and suggest saving them to a project config file ## Saving learned information If you discover useful project information (build commands, test commands, verification steps, user preferences, ...) that isn't already documented: - If a rules file exists (`AGENTS.md`, etc.), append to it - Otherwise, create `AGENTS.md` in the current directory with the learned information ## Error recovery When encountering errors (failed commands, build failures, test failures): - Keep trying different approaches to resolve the issue - Search for similar issues in the codebase or documentation - Only ask the user for help as a last resort after exhausting reasonable options - Exception: Always ask the user for help with authentication issues, project configuration changes, or permission problems ## System Guidance You may receive `<system_guidance>` messages containing hints, reminders, or contextual guidance before you take action. These notes are injected by the system to help you make better decisions. Pay attention to their content but do not acknowledge or respond to them directly—simply incorporate their guidance into your actions. # Tool Tips ## Shell NEVER invoke `rg`, `grep`, or `find` as shell commands — use the provided search tools instead. They have been optimized for correct permissions and access. ## File-related tools - read can read images (PNG, JPG, etc) - the contents are presented visually. - For Jupyter notebooks (.ipynb files), use notebook_read instead of read. - Speculatively read multiple files as a batch when potentially useful. - Do NOT create documentation files to describe your changes or plan. Exception: persistent project info files like `AGENTS.md` are allowed. # Safety IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Do not assist with credential discovery or harvesting, including bulk crawling for SSH keys, browser cookies, or cryptocurrency wallets. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation. IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files. ## Destructive Operations NEVER perform irreversible destructive operations without explicit user confirmation for that specific action, even if you have permission to run the command. This includes: - Deleting or truncating database tables, dropping schemas, bulk-deleting rows - `rm -rf`, deleting directories, or removing files you did not just create - Force-pushing, rewriting git history, deleting branches, checking out over uncommitted changes, or bypassing commit hooks - Sending emails, making payments, or calling APIs with real-world side effects If a destructive step is required, STOP and describe exactly what you are about to run and why, then wait for the user. Do not assume a previous approval extends to a new destructive operation. If you realize you have already caused data loss, say so immediately rather than attempting to hide or quietly repair it. ## Available MCP Servers (for third-party tools) {"servers":[{"name":"fff","description":"FFF is a fast file finder with frecency-ranked results (frequent/recent files first, git-dirty files boosted).\n\n## Which Tool Should I Use?\n\n- **grep**: DEFAULT tool. Searches file CONTENTS -- definitions, usage, patterns. Use when you have a specific name or pattern.\n- **find_files**: Explores which files/modules exist for a topic. Use when you DON'T have a specific identifier or LOOKING FOR A FILE.\n- **multi_grep**: OR logic across multiple patterns. Use for case variants (e.g. ['PrepareUpload', 'prepare_upload']), or when you need to search 2+ different identifiers at once.\n\n## Core Rules\n\n### 1. Search BARE IDENTIFIERS only\nGrep matches single lines. Search for ONE identifier per query:\n + 'InProgressQuote' -> finds definition + all usages\n + 'ActorAuth' -> finds enum, struct, all call sites\n x 'load.*metadata.*InProgressQuote' -> regex spanning multiple tokens, 0 results\n x 'ctx.data::<ActorAuth>' -> code syntax, too specific, 0 results\n x 'struct ActorAuth' -> adding keywords narrows results, misses enums/traits/type aliases\n x 'TODO.*#\\d+' -> complex regex, use simple 'TODO' then filter visually\n\n### 2. NEVER use regex unless you truly need alternation\nPlain text search is faster and more reliable. Regex patterns like `.*`, `\\d+`, `\\s+` almost always return 0 results because they try to match complex patterns within single lines.\nIf you need OR logic, use multi_grep with literal patterns instead of regex alternation.\n\n### 3. Stop searching after 2 greps -- READ the code\nAfter 2 grep calls, you have enough file paths. Read the top result to understand the code.\nDo NOT keep grepping with variations. More greps != better understanding.\n\n### 4. Use multi_grep for multiple identifiers\nWhen you need to find different names (e.g. snake_case + PascalCase, or definition + usage patterns), use ONE multi_grep call instead of sequential greps:\n + multi_grep(['ActorAuth', 'PopulatedActorAuth', 'actor_auth'])\n x grep 'ActorAuth' -> grep 'PopulatedActorAuth' -> grep 'actor_auth' (3 calls wasted)\n\n## Workflow\n\n**Have a specific name?** -> grep the bare identifier.\n**Need multiple name variants?** -> multi_grep with all variants in one call.\n**Exploring a topic / finding files?** -> find_files.\n**Got results?** -> Read the top file. Don't grep again.\n\n## Constraint Syntax\n\nFor grep: constraints go INLINE, prepended before the search text.\nFor multi_grep: constraints go in the separate 'constraints' parameter.\n\nConstraints MUST match one of these formats:\n Extension: '*.rs', '*.{ts,tsx}'\n Directory: 'src/', 'quotes/'\n Filename: 'schema.rs', 'src/main.rs'\n Exclude: '!test/', '!*.spec.ts'\n\n! Bare words without extensions are NOT constraints. 'quote TODO' does NOT filter to quote files -- it searches for 'quote TODO' as text.\n + 'schema.rs TODO' -> searches for 'TODO' in files schema.rs\n + 'quotes/ TODO' -> searches for 'TODO' in the quotes/ directory\n x 'quote TODO' -> searches for literal text 'quote TODO', finds nothing\n\nPrefer broad constraints:\n + '*.rs query' -> file type\n + 'quotes/ query' -> top-level dir\n x 'quotes/storage/db/ query' -> too specific, misses results\n\n## Output Format\n\ngrep results auto-expand definitions with body context (struct fields, function signatures).\nThis often provides enough information WITHOUT a follow-up Read call.\nLines marked with | are definition body context. [def] marks definition files.\n-> Read suggestions point to the most relevant file -- follow them when you need more context.\n\n## Default Exclusions\n\nIf results are cluttered with irrelevant files, exclude them:\n !tests/ - exclude tests directory\n !*.spec.ts - exclude test files\n !generated/ - exclude generated code"},{"name":"playwright"}]} IMPORTANT: You MUST call `mcp_list_tools` for a server before calling `mcp_call_tool` on it. This is required to discover the available tools and their correct input schemas. Never guess tool names or arguments — always list tools first.

Available subagent profiles for the `run_subagent` tool. Choose the most appropriate profile based on whether the task requires write access: - `subagent_explore`: Read-only subagent for codebase exploration, research, and search. Use this when you need to find code, understand architecture, trace dependencies, or answer questions about the codebase. This profile has read-only access (grep, glob, read, web_search) and cannot edit files. - `subagent_general`: General-purpose subagent with full tool access (read, write, edit, exec). Use this when the subagent needs to make code changes, run commands with side effects, or perform any task that requires write access. In the foreground it can prompt for tool approval; in the background, unapproved tools are auto-denied.

<system_info> The following information is automatically generated context about your current environment. Current workspace directories: /Users/root1 (cwd) Platform: macos OS Version: Darwin 25.6.0 Today's date: Saturday, 2026-06-27 </system_info>

<rules type="always-on"> <rule name="AGENTS" path="/Users/root1/AGENTS.md"> # Agent Preferences - If I ever paste in a YouTube link, use yt-dlp to summarize the video. - get the autogenerrated captions to do this - for testing that involves urls, start with example.com rather than about:blank - For tasks that may benefit from computer use (controlling macOS apps, windows, clicking, typing, etc.), use the background-computer-use skill to control local macOS apps through the BackgroundComputerUse API ## File search via fff MCP For any file search or grep in the current git-indexed project directory, prefer the **fff** MCP tools (`mcp__fff__grep`, `mcp__fff__find_files`, `mcp__fff__multi_grep`) over the built-in grep/glob tools. fff is frecency-ranked, git-aware, and more token-efficient. Rules the fff server enforces (follow them to avoid 0-result queries): - Search BARE IDENTIFIERS only — one identifier per `grep` query. No `load.*metadata.*Foo` style regex. - Don't use regex unless you truly need alternation; `.*`, `\d+`, `\s+` almost always return 0 results. - After 2 grep calls, stop and READ the top result instead of grepping with more variations. - Use `multi_grep` for OR logic across multiple identifiers (e.g. snake_case + PascalCase variants) in one call. - Have a specific name → `grep`. Exploring a topic / finding files → `find_files`. The `fff-mcp` binary lives at `/Users/root1/.local/bin/fff-mcp` and is registered at user scope in `~/.config/devin/config.json`. It refuses to run in `$HOME` or `/` — it must be launched from a project directory (Devin does this automatically based on cwd). Update with: `curl -fsSL https://raw.githubusercontent.com/dmtrKovalenko/fff.nvim/main/install-mcp.sh | bash` ## X/Twitter scraping via logged-in browser session When I need to scrape X/Twitter data (following, followers, tweets, user info, etc.), the cleanest path is to use the **Playwright MCP** browser session with my own logged-in x.com account, rather than spinning up twscrape's account-pool flow. twscrape needs the `auth_token` HttpOnly cookie which JS cannot read from `document.cookie`; the browser session attaches all cookies automatically. ### Flow 1. `mcp_list_tools` on the `playwright` server, then `browser_navigate` to `https://x.com`. 2. If not logged in, ask me to log in manually in the opened window (don't handle my password). 3. Once on `https://x.com/home`, read `ct0` from `document.cookie`: `document.cookie.match(/ct0=([^;]+)/)[1]` 4. Call X's GraphQL endpoints directly via `fetch()` inside `browser_evaluate`. Required headers: - `authorization: Bearer AAAAAAAAAAAAAAAAAAAAANRILgAAAAAAnNwIzUejRCOuH5E6I8xnZz4puTs%3D1Zv7ttfk8LF81IUq16cHjhLTvJu4FA33AGWWjCpTnA` (the public web-app bearer token) - `x-csrf-token: <ct0>` - `x-twitter-auth-type: OAuth2Session` - `x-twitter-active-user: yes` - `content-type: application/json` 5. Paginate timelines by reading `content.cursorType === "Bottom"` entries and passing the value back as `variables.cursor` until it stops changing. ### Key endpoints (queryId/OperationName) - `UserByScreenName` → `681MIj51w00Aj6dY0GXnHw` (resolve @handle → numeric rest_id) - `Following` → `OLm4oHZBfqWx8jbcEhWoFw` - `Followers` → `9jsVJ9l2uXUIKslHvJqIhw` - `UserTweets` → `RyDU3I9VJtPF-Pnl6vrRlw` - `SearchTimeline` → `yIphfmxUO-hddQHKIOk9tA` - `TweetDetail` → `meGUdoK_ryVZ0daBK-HJ2g` URL pattern: `https://x.com/i/api/graphql/<queryId>/<OpName>?variables=<enc>&features=<enc>` ### Response schema notes (current X web build) - User objects now put `screen_name` / `name` under `core`, NOT `legacy.screen_name`. twscrape's parser still reads `legacy.screen_name` and returns empty — needs updating. - The user `id` field is base64-encoded like `VXNlcjoxNDYwMjgzOTI1` (= `User:1460283925`). Decode with `atob(u.id).split(':')[1]` to get the numeric rest_id. `u.rest_id` may also be present directly. - `is_blue_verified` is the verified flag. `legacy.followers_count`, `legacy.description` still exist under `legacy`. - Filter timeline entries by `content.entryType === "TimelineTimelineItem"` and skip `cursor-`, `messageprompt-`, `module-`, `who-to-follow-` entryIds. ### Features dict Use the full `GQL_FEATURES` block from twscrape's `api.py` — without it X returns `(336) The following features cannot be null`. Pass it URL-encoded as the `features` param. ### Where things live - Output CSV: `~/Downloads/utilities/sdand_following.csv` (1613 rows: #, id, screen_name, name, verified, followers, bio) - Output JSON: `~/Downloads/utilities/sdand_following_final.json` (double-encoded JSON string; parse with `json.loads(json.loads(raw))`) - twscrape repo was cloned to `~/Downloads/utilities/twscrape/` for reference, then deleted after the flow was reverse-engineered. Re-clone from https://github.com/vladkens/twscrape.git if needed. </rule> <rule name="global_rules" path="/Users/root1/.codeium/windsurf/memories/global_rules.md"> </rule> </rules>

<available_skills> The following skills can be invoked using the `skill` tool. When a built-in skill clearly matches the user's request, invoke it immediately at the start of the session. - **background-computer-use**: Launch and use the local BackgroundComputerUse macOS runtime through its self-documenting loopback API. Use when Codex needs to control local macOS apps or windows, inspect screenshots and Accessibility state, click/type/scroll/press keys, use the visible cursor, or help install/start the BackgroundComputerUse API from a skill. (source: /Users/root1/.devin/skills/background-computer-use/SKILL.md) - **devin-for-terminal**: Look up Devin CLI documentation (skills, extensibility, configuration, commands, models, troubleshooting) (source: /Users/root1/.local/share/devin/cli/_versions/2026.8.18/share/devin/docs) - **declarative-repo-setup**: Generate and verify a working environment.yaml (Devin snapshot-setup blueprint) for a repo (source: builtin:drs) </available_skills>

Output from command in shell 10d038: WARNING: Your yt-dlp version (2025.12.08) is older than 90 days! It is strongly recommended to always use the latest version. You installed yt-dlp with pip or using the wheel from PyPi; Use that to update. To suppress this warning, add --no-update to your command/config. [youtube] Extracting URL: https://www.youtube.com/watch?v=r8PmQYJKdME [youtube] r8PmQYJKdME: Downloading webpage [youtube] r8PmQYJKdME: Downloading tv client config [youtube] r8PmQYJKdME: Downloading player a85504a6-main [youtube] r8PmQYJKdME: Downloading tv player API JSON [youtube] r8PmQYJKdME: Downloading android sdkless player API JSON [youtube] [jsc:deno] Solving JS challenges using deno WARNING: [youtube] [jsc] Remote components challenge solver script (deno) and NPM package (deno) were skipped. These may be required to solve JS challenges. You can enable these downloads with --remote-components ejs:github (recommended) or --remote-components ejs:npm , respectively. For more information and alternatives, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS WARNING: [youtube] r8PmQYJKdME: n challenge solving failed: Some formats may be missing. Ensure you have a supported JavaScript runtime and challenge solver script distribution installed. Review any warnings presented before this message. For more details, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS [info] r8PmQYJKdME: Downloading subtitles: en [info] r8PmQYJKdME: Downloading 1 format(s): 139 [info] Writing video subtitles to: yt_r8PmQYJKdME.en.vtt [download] Destination: yt_r8PmQYJKdME.en.vtt [download] 1.00KiB at Unknown B/s (00:00:00) [download] 3.00KiB at Unknown B/s (00:00:00) [download] 7.00KiB at 5.50MiB/s (00:00:00) [download] 15.00KiB at 5.02MiB/s (00:00:00) [download] 31.00KiB at 2.11MiB/s (00:00:00) [download] 63.00KiB at 2.50MiB/s (00:00:00) [download] 127.00KiB at 2.95MiB/s (00:00:00) [download] 181.33KiB at 3.46MiB/s (00:00:00) [download] 100% of 181.33KiB in 00:00:00 at 978.86KiB/s Exit code: 0

{ "command": "cd /tmp && python3 -c \"\nimport re\nwith open('yt_r8PmQYJKdME.en.vtt') as f:\n data = f.read()\n# Remove VTT header and timestamps\nlines = data.split('\\n')\nout = []\nseen = set()\nfor line in lines:\n line = line.strip()\n if not line: continue\n if line.startswith('WEBVTT') or line.startswith('Kind:') or line.startswith('Language:') or line.startswith('NOTE'): continue\n if re.match(r'^[\\d:.\\-> ]+\\$', line): continue\n if '<c>' in line: line = re.sub(r'<[^>]+>', '', line)\n if line in seen: continue\n seen.add(line)\n out.append(line)\ntext = ' '.join(out)\ntext = re.sub(r'\\s+', ' ', text)\nprint(text)\n\" 2>&1 | head -c 200\necho\necho \"---WORDCOUNT---\"\ncd /tmp && python3 -c \"\nimport re\nwith open('yt_r8PmQYJKdME.en.vtt') as f:\n data = f.read()\nlines = data.split('\\n')\nout = []\nseen = set()\nfor line in lines:\n line = line.strip()\n if not line: continue\n if line.startswith('WEBVTT') or line.startswith('Kind:') or line.startswith('Language:') or line.startswith('NOTE'): continue\n if re.match(r'^[\\d:.\\-> ]+\\$', line): continue\n if '<c>' in line: line = re.sub(r'<[^>]+>', '', line)\n if line in seen: continue\n seen.add(line)\n out.append(line)\ntext = ' '.join(out)\ntext = re.sub(r'\\s+', ' ', text)\nprint(len(text.split()))\n\"" }

Output from command in shell ed17db: 00:00:00.080 --> 00:00:01.990 align:start position:0% I've been using the iPhone 17 Pro for 00:00:01.990 --> 00:00:02.000 align:start position:0% 00:00:02.000 --> 00:00:03.510 align:start position:0% ---WORDCOUNT--- 8923 Exit code: 0

{ "command": "cd /tmp && python3 << 'EOF'\nimport re\nwith open('yt_r8PmQYJKdME.en.vtt') as f:\n data = f.read()\nlines = data.split('\\n')\nout = []\nseen = set()\nts_re = re.compile(r'^[\\d:.\\-> ]+$')\nfor line in lines:\n line = line.strip()\n if not line: continue\n if line.startswith('WEBVTT') or line.startswith('Kind:') or line.startswith('Language:') or line.startswith('NOTE'): continue\n if ts_re.match(line): continue\n line = re.sub(r'<[^>]+>', '', line)\n if line in seen: continue\n seen.add(line)\n out.append(line)\ntext = ' '.join(out)\ntext = re.sub(r'\\s+', ' ', text)\nwith open('yt_r8PmQYJKdME.txt','w') as f:\n f.write(text)\nprint(len(text.split()), 'words')\nprint(text[:1500])\nEOF" }

Output from command in shell 509fab: 8923 words 00:00:00.080 --> 00:00:01.990 align:start position:0% I've been using the iPhone 17 Pro for 00:00:01.990 --> 00:00:02.000 align:start position:0% 00:00:02.000 --> 00:00:03.510 align:start position:0% the past seven months straight. And when 00:00:03.510 --> 00:00:03.520 align:start position:0% 00:00:03.520 --> 00:00:05.430 align:start position:0% it was first announced, I was a bit 00:00:05.430 --> 00:00:05.440 align:start position:0% 00:00:05.440 --> 00:00:07.829 align:start position:0% nervous because for two straight years, 00:00:07.829 --> 00:00:07.839 align:start position:0% 00:00:07.839 --> 00:00:09.669 align:start position:0% Apple has been notorious for 00:00:09.669 --> 00:00:09.679 align:start position:0% 00:00:09.679 --> 00:00:11.749 align:start position:0% questionable marketing and missed 00:00:11.749 --> 00:00:11.759 align:start position:0% 00:00:11.759 --> 00:00:14.629 align:start position:0% deadlines. But the iPhone 17 series was 00:00:14.629 --> 00:00:14.639 align:start position:0% 00:00:14.639 --> 00:00:17.269 align:start position:0% Apple's perfect shot for redemption. And 00:00:17.269 --> 00:00:17.279 align:start position:0% 00:00:17.279 --> 00:00:19.429 align:start position:0% I think they actually did it, although 00:00:19.429 --> 00:00:19.439 align:start position:0% 00:00:19.439 --> 00:00:21.429 align:start position:0% with some compromise. So, let's rewind 00:00:21.429 --> 00:00:21.439 align:start position:0% 00:00:21.439 --> 00:00:23.830 align:start p Exit code: 0

{ "command": "cd /tmp && python3 << 'EOF'\nimport re\nwith open('yt_r8PmQYJKdME.en.vtt') as f:\n data = f.read()\n# Remove timestamp lines (lines that are ONLY timestamps)\nlines = data.split('\\n')\nout = []\nseen = set()\nts_re = re.compile(r'^[\\d:.\\-> ]+$')\nfor line in lines:\n line = line.strip()\n if not line: continue\n if line.startswith('WEBVTT') or line.startswith('Kind:') or line.startswith('Language:') or line.startswith('NOTE'): continue\n if ts_re.match(line): continue\n # Strip inline timestamp prefix like \"00:00:00.080 --> 00:00:01.990 align:start position:0% text\"\n line = re.sub(r'^[\\d:.\\-> ]+align:start position:0%\\s*', '', line)\n line = re.sub(r'<[^>]+>', '', line)\n if line in seen: continue\n seen.add(line)\n out.append(line)\ntext = ' '.join(out)\ntext = re.sub(r'\\s+', ' ', text)\nwith open('yt_r8PmQYJKdME.txt','w') as f:\n f.write(text)\nprint(len(text.split()), 'words')\nprint(text[:2000])\nEOF" }

Output from command in shell 8a4999: 3828 words I've been using the iPhone 17 Pro for the past seven months straight. And when it was first announced, I was a bit nervous because for two straight years, Apple has been notorious for questionable marketing and missed deadlines. But the iPhone 17 series was Apple's perfect shot for redemption. And I think they actually did it, although with some compromise. So, let's rewind back to the iPhone 15 Pro because if you remember, Apple's main marketing for that was that it was made of titanium or made with titanium, but the reality was that it was only made with a little bit of titanium. So, a lot of people saw that as quite deceptive. And then for the iPhone 16 Pro, that was touted as being built from the ground up for Apple intelligence, but the reality was that we didn't actually get all the Apple intelligence features that we were promised. And that brings us to today with the iPhone 17 Pro where Apple's main marketing push was with the aluminum unibody design and the vapor chamber cooling system inside. And the reality was overwhelmingly positive because the aluminum unibody design actually looks good. However, there is a compromise with the two-tone look. A lot of people, myself included, are not the biggest fan of this. However, it does look best on silver. But, you know, it looks great. It actually has a noticeable change from the other iPhones. and the vapor chamber inside performs very well. And keep in mind, this is the biggest design change to the iPhone in quite some time. Like, we have a full camera plateau now on the iPhone 17 Pro, whereas we never had, you know, a full plateau on the back before. And this is instantly recognizable as the new phone, which is something we really haven't seen since the iPhone 10 back in 2017, where you can look across the room and tell somebody has a new phone. Like before, of course, we had, you know, things with the edges being flattened and things like that, but you couldn't really tell it was a new phone, you know, from Exit code: 0

<file-view path="/tmp/yt_r8PmQYJKdME.txt" start_line="1" end_line="1" total_lines="1"> 1| I've been using the iPhone 17 Pro for the past seven months straight. And when it was first announced, I was a bit nervous because for two straight years, Apple has been notorious for questionable marketing and missed deadlines. But the iPhone 17 series was Apple's perfect shot for redemption. And I think they actually did it, although with some compromise. So, let's rewind back to the iPhone 15 Pro because if you remember, Apple's main marketing for that was that it was made of titanium or made with titanium, but the reality was that it was only made with a little bit of titanium. So, a lot of people saw that as quite deceptive. And then for the iPhone 16 Pro, that was touted as being built from the ground up for Apple intelligence, but the reality was that we didn't actually get all the Apple intelligence features that we were promised. And that brings us to today with the iPhone 17 Pro where Apple's main marketing push was with the aluminum unibody design and the vapor chamber cooling system inside. And the reality was overwhelmingly positive because the aluminum unibody design actually looks good. However, there is a compromise with the two-tone look. A lot of people, myself included, are not the biggest fan of this. However, it does look best on silver. But, you know, it looks great. It actually has a noticeable change from the other iPhones. and the vapor chamber inside performs very well. And keep in mind, this is the biggest design change to the iPhone in quite some time. Like, we have a full camera plateau now on the iPhone 17 Pro, whereas we never had, you know, a full plateau on the back before. And this is instantly recognizable as the new phone, which is something we really haven't seen since the iPhone 10 back in 2017, where you can look across the room and tell somebody has a new phone. Like before, of course, we had, you know, things with the edges being flattened and things like that, but you couldn't really tell it was a new phone, you know, from ... [truncated 17655 chars] </file-view>

Output from command in shell 722eab: 10 to 20 feet away like you can now with the 17 Pro. It's instantly recognizable, and I think that's also been a big reason why a lot of people wanted to upgrade to this device. And again, that all comes back to being the aluminum unibody design, which was Apple's main marketing. It worked. And if you throw in the new cosmic orange color, which was also made possible because of switching back to aluminum, that was also a big reason a lot of people wanted to upgrade to the iPhone 17 Pro and Pro Max. As you can see, I did decide to go with the silver, which I am very happy with. I think this is the best color for the 17 Pros, but the cosmic orange absolutely is one of the most popular colors and also makes it instantly recognizable as the new phone. Now, I have to tell you guys something else. This is the first year I've ever gone on any iPhone without using a screen protector. That is something very rare and out of character for me because I'm usually a perfectionist with my screen. I don't like any scratches. But this year, I decided to go without a screen protector because we did have the new ceramic Shield 2 on the front, which Apple says will give three times better scratch resistance versus previous iPhones. Now, of course, that doesn't mean scratch proof, it's just scratch resistant. So, if you try to scratch it, of course, you will. But, you know, if I'm taking a look at my screen here, and I've had this in my pocket. I've had it down on tabletops. I don't really see any noticeable scratches. That is crazy. I cannot remember the last time I've seen that with an iPhone. Now, keep in mind, I said I use a screen protector on my main phone, but on all my test phones, I don't even use them every single day, and I don't have them as as many environments, but those even get scratches on the screen. But this, my main phone, my 17 Pro here that I use every single day in my pocket, doesn't have a scratch. So, the ceramic shield 2 has been wonderful on the iPhone 17 Pro after more than 7 months. And we also have the anti-reflective coating on the iPhone 17 Pro screens. It's not quite as good as Samsung's, you know, with the Galaxy series. Actually, it's not even close to as good, but it is still something that's nice to have. And there's also ceramic shield on the back of the iPhone for the first time as well. I've only dropped this phone in a case and it's been perfectly fine, but it should be tougher on the back as well because of that. And as far as the display itself, of course, we have the same 6.3 in size that we had on last year's Pro phone. Of course, that is the 120 Hz OLED screen. Now, the big difference here is in the brightness, specifically when outdoors, because this year, Apple upped the brightness from 2,00 to 3000 nits when outdoors, when you're in auto brightness. And I have noticed the difference on my 17 Pro when I'm out in the Florida sun, but it's not as, you know, dramatic and not as big as you would think based on, you know, a ===== thousand nits increase. It's barely noticeable, but I'm not complaining. I love being able to see my phone perfectly fine, you know, when the sun is beating down on it. So, no complaints whatsoever about the screen. Now, battery life is easily one of the most important things when it comes to long-term reviews on these iPhones. I like to do these reviews much longer term because of battery specifically specifically with the battery health. So, if I go into my battery here and check out my battery health, I am currently at 97% on my iPhone 17 Pro. And that's actually a little bit lower than I scored on my 16 Pro around this time. So I think it was at 98% at the end of April. So pretty close to that. However, I do have more cycles on my 17 Pro at 271 as of the time of recording this. So I've been using this phone a lot, but the battery life has dropped a good bit. So 3% in those 7 months. And I do have this on a charge limit. So I only charge my 17 Pro up to 90%. And I also have optimized battery charging enabled. So, you know, I usually get through most of the day. I usually have to charge my 17 Pro at some point in the evening, at some point after like 6:00 p.m., you know, it depends on how much I'm using that day, but that's typically the case. I am recording a lot of video all the time, so sometimes it will drain faster, but most of the times I do get through the day perfectly fine. And one thing I've really noticed a big difference in is the 25 watt fast wireless charging. This is such a big deal. I did not think it would be that much better over the standard 15 watt like we had before. Now, this is not a 17 Pro exclusive. It did come in a software update for the 16s as well. But I do notice a noticeable, you know, difference in wireless charging. That's my primary way of charging my phone. So, that's a big deal on the 17 Pro. And the one I've been using is actually from Anker, who's today's sponsor. So, this is the Anker Prime wireless charging station, and it's the latest product from their flagship Anker Prime series, and it might just be my favorite 3in-1 yet. I'm going to stick my iPhone 17 Pro here to charge up at the full 25 watts thanks to Chi 2. And then I'll also throw on my Apple Watch Ultra and my AirPods down here. And by the way, that 25 watt fast charging is actually noticeably faster than my previous 15 watt wireless charger. And it can charge my 17 Pro up from 0 to 50% in just 26 minutes. And man, I just used to not bring any type of wireless charger with me when on the go because it just charged too slow. But not anymore. So, the compact design makes this easy to travel with. Plus, it charges as fast as I would need it to at any given point without the need for any extra wires and chargers. So, now when I'm on the go and traveling, this is my go-to because it fits great in my bag or even my jacket pocket. And also, when I go to a hotel, I just unfold this anchor, I plug it in, and I'm good to go. It also tilts back and forth, ===== so you can easily watch your content while it charges. And one of my favorite things about this 3in-1 from Anker is just the high quality build. So, it doesn't feel cheap and plasticky like a lot of the others I've used. And also, it doesn't get too hot. So, it has Active Shield 5.0 technology and airflow cooling system to keep your device cool and charging constantly at 25 watts. So, if you want to grab this Anker 3 in-1 wireless charging station for your iPhone, be sure to click my special link down in the description below to grab yours today. Okay, so now we have to talk about one of the most important things when a new iPhone comes out, especially a pro iPhone, and that is the cameras. So, the iPhone 17 Pro does have the triple 48 megapixel camera system. And what stood out to me the most when using this phone, like something I used a lot more than I thought I would, is the 8x optical zoom. Now, keep in mind, this is not a true optical zoom. It's, you know, Apple just saying that it's really a 4x optical zoom with a 2x digital zoom on top of it. So, you know, but I do use that 8x quite a lot. And it's really nice to have the button down here to just tap that eight and go into 8x right there. And then you can zoom all the way up to 24x in video. And then when you're in photo, you can go all the way up to a 40x digital zoom, which is also something I didn't think I'd use as much as I have been using on the 17 Pro. I also use the.5x ultrawide a lot since it is 48 megapixels now for both photo and video. However, I noticed that the photo quality really isn't that much better. like I thought it would be a lot better, you know, going to 48 megapixels, but it's not. So, I still opt to use 1x if I'm trying to get the best quality. I also notice when taking pictures of anything with like a really bright light, you there's less lens flare on the 17 Pro than on the 16 Pros and really any other iPhone as well, which is nice when I'm taking a picture of like the sun or a light, a street light, something like that. It's better on the 17 Pro, I noticed. Now, a lot of people ask me about the camera control, like, do I use it? Is it really a gimmick? because it's something you should disable. And to be honest, I still use camera control sometimes. Like I don't use it very often. I used to use it a lot more honestly last year, but this year I really only use it when I'm shooting in landscape mode like this. I really never use it when I'm shooting portraits, but in landscape it is really nice and handy to be able to zoom. That's specifically what I do is I zoom with this. And sometimes I'll change the camera to like 2x, but you know, it is easier to just press down right here and zoom in when in landscape mode. So I don't use it often, but it is something I do use. Also, Apple log 2 for ProRes video is tremendous on the iPhone 17 Pros. That is one of my favorite, you know, ways to shoot content is in ProRes and especially now with the Apple Log 2. It's just better than it was previously. Now, speaking of things I did not think I would use very often, dual capture is easily one of my favorite features on the iPhone 17 Pro, and I really did not expect it to be. Like, I think when it came out, I was like, "Oh, that's cool, but I probably won't use it very often. I used it maybe one or two times and that's it." I was dead wrong. I guess maybe because I've been doing a lot of experiences. I've been having a lot of fun things going on over the past, you know, six, seven months, something like that. But dual capture is something I've used countless times, dozens of times to get my reaction to something and also show like what's in front of me. It is great for that. If you're at a concert, if you're experiencing something new, dual capture is easily one of my favorite features on this phone. And it's something I'd recommend everybody try out, especially if you want to vlog or just, you know, shar… (7707 chars truncated) Exit code: 0 <truncation_notice> Full output written to: /var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/devin-overflows-501/38647d5a/content.txt </truncation_notice>

<file-view path="/var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/devin-overflows-501/38647d5a/content.txt" start_line="1" end_line="9" total_lines="9"> 1|Output from command in shell 722eab: 2|10 to 20 feet away like you can now with the 17 Pro. It's instantly recognizable, and I think that's also been a big reason why a lot of people wanted to upgrade to this device. And again, that all comes back to being the aluminum unibody design, which was Apple's main marketing. It worked. And if you throw in the new cosmic orange color, which was also made possible because of switching back to aluminum, that was also a big reason a lot of people wanted to upgrade to the iPhone 17 Pro and Pro Max. As you can see, I did decide to go with the silver, which I am very happy with. I think this is the best color for the 17 Pros, but the cosmic orange absolutely is one of the most popular colors and also makes it instantly recognizable as the new phone. Now, I have to tell you guys something else. This is the first year I've ever gone on any iPhone without using a screen protector. That is something very rare and out of character for me because I'm usually a perfectionist with my screen. I don't like any scratches. But this year, I decided to go without a screen protector because we did have the new ceramic Shield 2 on the front, which Apple says will give three times better scratch resistance versus previous iPhones. Now, of course, that doesn't mean scratch proof, it's just scratch resistant. So, if you try to scratch it, of course, you will. But, you know, if I'm taking a look at my screen here, and I've had this in my pocket. I've had it down on tabletops. I don't really see any noticeable scratches. That is crazy. I cannot remember the last time I've seen that with an iPhone. Now, keep in mind, I said I use a screen protector on my main phone, but on all my test phones, I don't even use them every single day, and I don't have them as as many environments, but those even get scratches on the screen. But this, my main phone, my 17 Pro here that I use every single day in my pocket, doesn't have a scratch. So, the ceramic shield 2 has been wonderful on the iPhone 17 Pro ... [truncated 1000 chars] 3|===== 4|thousand nits increase. It's barely noticeable, but I'm not complaining. I love being able to see my phone perfectly fine, you know, when the sun is beating down on it. So, no complaints whatsoever about the screen. Now, battery life is easily one of the most important things when it comes to long-term reviews on these iPhones. I like to do these reviews much longer term because of battery specifically specifically with the battery health. So, if I go into my battery here and check out my battery health, I am currently at 97% on my iPhone 17 Pro. And that's actually a little bit lower than I scored on my 16 Pro around this time. So I think it was at 98% at the end of April. So pretty close to that. However, I do have more cycles on my 17 Pro at 271 as of the time of recording this. So I've been using this phone a lot, but the battery life has dropped a good bit. So 3% in those 7 months. And I do have this on a charge limit. So I only charge my 17 Pro up to 90%. And I also have optimized battery charging enabled. So, you know, I usually get through most of the day. I usually have to charge my 17 Pro at some point in the evening, at some point after like 6:00 p.m., you know, it depends on how much I'm using that day, but that's typically the case. I am recording a lot of video all the time, so sometimes it will drain faster, but most of the times I do get through the day perfectly fine. And one thing I've really noticed a big difference in is the 25 watt fast wireless charging. This is such a big deal. I did not think it would be that much better over the standard 15 watt like we had before. Now, this is not a 17 Pro exclusive. It did come in a software update for the 16s as well. But I do notice a noticeable, you know, difference in wireless charging. That's my primary way of charging my phone. So, that's a big deal on the 17 Pro. And the one I've been using is actually from Anker, who's today's sponsor. So, this is the Anker Prime wireless charging station, and it's... [truncated 1000 chars] 5|===== 6| so you can easily watch your content while it charges. And one of my favorite things about this 3in-1 from Anker is just the high quality build. So, it doesn't feel cheap and plasticky like a lot of the others I've used. And also, it doesn't get too hot. So, it has Active Shield 5.0 technology and airflow cooling system to keep your device cool and charging constantly at 25 watts. So, if you want to grab this Anker 3 in-1 wireless charging station for your iPhone, be sure to click my special link down in the description below to grab yours today. Okay, so now we have to talk about one of the most important things when a new iPhone comes out, especially a pro iPhone, and that is the cameras. So, the iPhone 17 Pro does have the triple 48 megapixel camera system. And what stood out to me the most when using this phone, like something I used a lot more than I thought I would, is the 8x optical zoom. Now, keep in mind, this is not a true optical zoom. It's, you know, Apple just saying that it's really a 4x optical zoom with a 2x digital zoom on top of it. So, you know, but I do use that 8x quite a lot. And it's really nice to have the button down here to just tap that eight and go into 8x right there. And then you can zoom all the way up to 24x in video. And then when you're in photo, you can go all the way up to a 40x digital zoom, which is also something I didn't think I'd use as much as I have been using on the 17 Pro. I also use the.5x ultrawide a lot since it is 48 megapixels now for both photo and video. However, I noticed that the photo quality really isn't that much better. like I thought it would be a lot better, you know, going to 48 megapixels, but it's not. So, I still opt to use 1x if I'm trying to get the best quality. I also notice when taking pictures of anything with like a really bright light, you there's less lens flare on the 17 Pro than on the 16 Pros and really any other iPhone as well, which is nice when I'm taking a picture of like the sun or a l... [truncated 9655 chars] 7| 8| 9|Exit code: 0 </file-view>

Output from command in shell 99cfab: so you can easily watch your content while it charges. And one of my favorite things about this 3in-1 from Anker is just the high quality build. So, it doesn't feel cheap and plasticky like a lot of the others I've used. And also, it doesn't get too hot. So, it has Active Shield 5.0 technology and airflow cooling system to keep your device cool and charging constantly at 25 watts. So, if you want to grab this Anker 3 in-1 wireless charging station for your iPhone, be sure to click my special link down in the description below to grab yours today. Okay, so now we have to talk about one of the most important things when a new iPhone comes out, especially a pro iPhone, and that is the cameras. So, the iPhone 17 Pro does have the triple 48 megapixel camera system. And what stood out to me the most when using this phone, like something I used a lot more than I thought I would, is the 8x optical zoom. Now, keep in mind, this is not a true optical zoom. It's, you know, Apple just saying that it's really a 4x optical zoom with a 2x digital zoom on top of it. So, you know, but I do use that 8x quite a lot. And it's really nice to have the button down here to just tap that eight and go into 8x right there. And then you can zoom all the way up to 24x in video. And then when you're in photo, you can go all the way up to a 40x digital zoom, which is also something I didn't think I'd use as much as I have been using on the 17 Pro. I also use the.5x ultrawide a lot since it is 48 megapixels now for both photo and video. However, I noticed that the photo quality really isn't that much better. like I thought it would be a lot better, you know, going to 48 megapixels, but it's not. So, I still opt to use 1x if I'm trying to get the best quality. I also notice when taking pictures of anything with like a really bright light, you there's less lens flare on the 17 Pro than on the 16 Pros and really any other iPhone as well, which is nice when I'm taking a picture of like the sun or a light, a street light, something like that. It's better on the 17 Pro, I noticed. Now, a lot of people ask me about the camera control, like, do I use it? Is it really a gimmick? because it's something you should disable. And to be honest, I still use camera control sometimes. Like I don't use it very often. I used to use it a lot more honestly last year, but this year I really only use it when I'm shooting in landscape mode like this. I really never use it when I'm shooting portraits, but in landscape it is really nice and handy to be able to zoom. That's specifically what I do is I zoom with this. And sometimes I'll change the camera to like 2x, but you know, it is easier to just press down right here and zoom in when in landscape mode. So I don't use it often, but it is something I do use. Also, Apple log 2 for ProRes video is tremendous on the iPhone 17 Pros. That is one of my favorite, you know, ways to shoot content is in ProRes and especially now with the Apple Log 2. It's just better than it was previously. Now, speaking of things I did not think I would use very often, dual capture is easily one of my favorite features on the iPhone 17 Pro, and I really did not expect it to be. Like, I think when it came out, I was like, "Oh, that's cool, but I probably won't use it very often. I used it maybe one or two times and that's it." I was dead wrong. I guess maybe because I've been doing a lot of experiences. I've been having a lot of fun things going on over the past, you know, six, seven months, something like that. But dual capture is something I've used countless times, dozens of times to get my reaction to something and also show like what's in front of me. It is great for that. If you're at a concert, if you're experiencing something new, dual capture is easily one of my favorite features on this phone. And it's something I'd recommend everybody try out, especially if you want to vlog or just, you know, share. Like I did this also for my birthday when people ===== were singing me happy birthday. I had it on them and also on my face at the same time. And I'll look back on that in 10 years and be like that's amazing. I was able to capture that. I do wish the frontfacing camera was a bit more zoomed out so I can, you know, capture my face more. But overall, I love dual capture. It's easily, you know, one of my favorite features on this phone. Oh, and by the way, that front-facing camera also has center stage, which is extremely useful for FaceTime calls or really any type of video that you're doing. It keeps you in frame really nice. And I feel like nobody ever talks about the speakers on the iPhone, you know, especially after a long period of time. But the iPhone 17 Pro speakers just amaze me still to this day. Like every year I think Apple has the best speakers in the game. You know, I compare it to Samsung every year. But Apple just crushes it every single year. And it's no different with the iPhone 17 Pro. So if you watch content on your iPhone, you really don't even need AirPods at this point. Like unless you're in a public, you know, environment, but if you're just at home, the speakers are excellent on this phone. And they're even better, of course, on the Pro Max. But the Pro is no slouch. Now, you might be wondering, do you miss using a Pro Max phone and do you miss the iPhone Air? Because if you guys recall, I was actually using the iPhone Air for quite some time as my primary phone. I was trying to decide between that and the Pro Max at the time, and I wound up choosing the iPhone 17 Pro at the end of the day. But I have to say that for the iPhone 17 Pro versus the Pro Max in terms of sizing, no, I do not miss the Pro Max at all. Like, just take a look at this right here. Okay, so I always talk about how the iPhone 17 Pro Max is too big for my taste because take a look at this pocket right here in my jeans, my regular jeans that I always wear. It literally sticks out of the pocket. Like it doesn't go down even when I push on it right there. And it's just a big boulder in my pocket. I just prefer the 17 Pro over the Pro Max again for that alone. And also just the weight. Like the Pro Max just weighs more than the 17 Pro. And also just the way it feels in the hand. Just so many reasons. I just prefer the size of the 17 Pro to the Pro Max. So, no, I do not miss it at all. Battery life, of course, is great on here. Would be better with the Pro Max, but I don't need that. Now, as far as the iPhone Air goes, that's a different story because yes, I have found myself missing the iPhone Air when using the 17 Pro. I still think about it a lot, honestly. Like, the feel in hand of the iPhone Air is just like unlike anything else I've ever used. Like even better than the Galaxy phones. I talked about it in my review. If you missed my review on the iPhone Air compared to the 17 Pro Max, go watch that video. But that phone is hands down the best in the pocket, in the hands, just looks wise, just aesthetics when you're out, you know, using it. When I see people using it in public, I'm like, man, that's such a good-look phone. So, yes, I do miss the iPhone Air. However, I could not compromise on the cameras specifically. That's the one thing. And of course, the the speakers aren't very great either. Anyways, getting back to the 17 Pro, let me get back on track here. The performance on this guy is rock solid. So, we do have the A19 Pro chip. So, if you are somebody who games or anything like that, it will be great. Now, day-to-day usage, like going in social media, going in your Safari, responding to text messages, it's going to feel the same as the past several years. Like really no difference there. Like I said, if you're a gamer though, that is where you can see the difference because not only do we have a better chip, but we also have that vapor chamber cooling system inside which is going to help tremendously with keeping your device cool while doing those intensive tasks, which of course will lead to better performance and less, you know, lag and throttle from the heat. I'm not a big gamer, so I haven't really noticed it with gaming too much, but I have noticed it when doing things in Lightroom, like, you know, editing my photos in Lightroom or the occasional time where I'm editing a video and like the Instagram edits application, my phone just stays much cooler than it did previously. I also always give a yearly update on my cell connectivity because some years I've had really bad cell service for some reason on these iPhones, but with the 17 Pro, everything's been perfectly fine. Like I'm on Verizon and I've never had any issues with cell connectivity on this phone, which is great. So overall, at this point, I think the iPhone 17 Pro is peak pro iPhone. So I think it's great that Apple is actually releasing the iPhone Ultra or the iPhone Fold later this year because it will give more of the fanatics, more of the people who upgrade every year, something new to try out because I can't imagine that it's going to get much better than the 17 Pro for the next few years. Of course, Apple will still make, you know, these small improvements like the, you know, the camera and everything's going to get better, but as far as the overall design change and things like that, that only comes every once in a while. So, as of right now, of course, this is peak iPhone. I feel like every year, of course, technically is peak iPhone, but you know what I mean. I just think this is a big upgrade year-over-year from last year, and I think it's going to be a while before we see another dramatic year-over-year change like we did with the 17 Pro. So, now you might be wondering, should you buy the iPhone 17 Pro now or should you wait for the iPhone 18 Pro or Pro Max or the iPhone Ultra? And I'm a big proponent of just saying that if you need a phone now, if you're thinking about buying a phone now, just buy it. Please don't wait. Lik… (1700 chars truncated) Exit code: 0 <truncation_notice> Full output written to: /var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/devin-overflows-501/58b39596/content.txt </truncation_notice>

Output from command in shell 461a5e: ll lead to better performance and less, you know, lag and throttle from the heat. I'm not a big gamer, so I haven't really noticed it with gaming too much, but I have noticed it when doing things in Lightroom, like, you know, editing my photos in Lightroom or the occasional time where I'm editing a video and like the Instagram edits application, my phone just stays much cooler than it did previously. I also always give a yearly update on my cell connectivity because some years I've had really bad cell service for some reason on these iPhones, but with the 17 Pro, everything's been perfectly fine. Like I'm on Verizon and I've never had any issues with cell connectivity on this phone, which is great. So overall, at this point, I think the iPhone 17 Pro is peak pro iPhone. So I think it's great that Apple is actually releasing the iPhone Ultra or the iPhone Fold later this year because it will give more of the fanatics, more of the people who upgrade every year, something new to try out because I can't imagine that it's going to get much better than the 17 Pro for the next few years. Of course, Apple will still make, you know, these small improvements like the, you know, the camera and everything's going to get better, but as far as the overall design change and things like that, that only comes every once in a while. So, as of right now, of course, this is peak iPhone. I feel like every year, of course, technically is peak iPhone, but you know what I mean. I just think this is a big upgrade year-over-year from last year, and I think it's going to be a while before we see another dramatic year-over-year change like we did with the 17 Pro. So, now you might be wondering, should you buy the iPhone 17 Pro now or should you wait for the iPhone 18 Pro or Pro Max or the iPhone Ultra? And I'm a big proponent of just saying that if you need a phone now, if you're thinking about buying a phone now, just buy it. Please don't wait. Like I just said that the odds of a year-over-year, you know, upgrade being as dramatic as we saw from the 16 Pro to the 17 Pro is pretty unlikely. So, I think if you need one now, just get the 17 Pro or Pro Max. But if you have an older device and you're waiting to see the iPhone Fold or the iPhone Ultra, of course you should wait because there's nothing else like it out there on the market right now from Apple. But just know it's not going to have as good a cameras as the 17 Pro has. So those are my thoughts on the iPhone 17 Pro after more than 7 months of use every single day. This phone has really impressed me. It's the first time in a while I've been this impressed with a Pro iPhone. Now, I wish my battery health was still at 100%. It just actually went down after the last update. it was 100% and went all the way from 100 down to 97. So, that was pretty disappointing. But, you know, overall, I have really nothing bad to say about the 17 Pro. It's rare that I have nothing bad to say about it. Like, I guess the only thing is the two-tone design. Apple is supposedly fixing that with the 18 Pros, but I'm not the biggest fan of it except for on the silver color. It looks just fine. But, what do you guys think? Do you have the iPhone 17 Pro? Do you have a 17 Pro Max? Let me know all your thoughts down in the comments below. I'm very curious to hear your experience with this phone. and if you agree with my points. But anyways guys, thanks for watching. Be sure to check out Anker down in the description below and also in the pinned comments. They make some great products and I'm actually a really big fan of all their stuff. But anyways guys, thanks for watching and I'll see you Exit code: 0

I have the full transcript. Here's the summary:

Summary: "iPhone 17 Pro Review After 7 Months - What Happened?"

A long-term review by a YouTuber who has used the iPhone 17 Pro as his daily driver for 7+ months. Overall verdict: it's "peak pro iPhone" — Apple's redemption after the questionable marketing of the 15 Pro (titanium) and 16 Pro (Apple Intelligence).

Design & Build

Aluminum unibody + vapor chamber cooling — Apple's main marketing claims both delivered. Biggest design change since iPhone X (2017); instantly recognizable from across the room thanks to the full camera plateau on the back.
Two-tone look is the one compromise — he's not a fan except on silver (which he bought). Cosmic orange is the most popular/pop-out color.
Ceramic Shield 2: He went screen-protector-free for the first time ever. After 7 months of pocket/table use — no visible scratches. Big win.
Anti-reflective screen coating is a nice-to-have but nowhere near Samsung's Galaxy quality. Ceramic Shield now also on the back.

Display

Same 6.3" 120Hz OLED as the 16 Pro. Outdoor brightness bumped 2000 → 3000 nits; noticeable in Florida sun but not as dramatic as the spec sheet suggests.

Battery & Charging

Battery health: 97% after 271 cycles / 7 months (slightly worse than his 16 Pro at the same point; dropped 100→97 after a recent update, which disappointed him). Uses 90% charge limit + optimized charging.
Gets through the day, usually charges after 6pm.
25W fast wireless charging (Qi2) is a standout — noticeably faster than the old 15W. (Sponsor segment: Anker Prime 3-in-1 charger, 0–50% in 26 min.)

Cameras

Triple 48MP system. 8x "optical" zoom (really 4x optical + 2x digital) used way more than expected — dedicated button is handy. Up to 24x video / 40x photo digital zoom.
0.5x ultrawide is now 48MP but photo quality isn't noticeably better — he still prefers 1x for best quality.
Less lens flare vs. 16 Pro and other iPhones when shooting bright lights.
Camera Control button: still uses it occasionally, mostly for zooming in landscape mode. Not a gimmick but not essential.
Apple Log 2 for ProRes video — tremendous, one of his favorite shooting modes.
Dual Capture (front + rear simultaneously) — surprise favorite feature, used dozens of times for concerts, birthdays, experiences. Wishes the front cam was more zoomed out.
Front camera has Center Stage for FaceTime.

Speakers

Apple still has the best phone speakers — content is enjoyable without AirPods at home. Pro Max is even better but Pro is no slouch.

Size Comparison

Doesn't miss the Pro Max — too big, sticks out of jeans pocket, heavier. Prefers the 17 Pro's size.
Does miss the iPhone Air — best in-hand/in-pocket feel of any phone, but couldn't compromise on cameras (and Air speakers are weak).

Performance & Connectivity

A19 Pro + vapor chamber keeps the phone noticeably cooler during Lightroom photo editing and Instagram video editing. Day-to-day tasks feel identical to prior years.
Verizon cell connectivity has been flawless all year (some prior years had issues).

Verdict & Buying Advice

Calls the 17 Pro "peak pro iPhone" — biggest year-over-year change in a while; doesn't expect another dramatic jump for a few years. Welcomes the upcoming iPhone Ultra/Fold as something for upgrade-happy fans to try, but notes it won't match the 17 Pro's cameras.
Buy now if you need a phone — don't wait for the 18 Pro/Ultra unless you specifically want a foldable. Only real complaints: battery health drop and the two-tone design (rumored to be fixed on 18 Pro).