Devin Sessions

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://devin.ai/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-cli` 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":"cloudflare"},{"name":"cloudflare-observability"},{"name":"playwright"},{"name":"cloudflare-docs"},{"name":"cloudflare-bindings"},{"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":"cloudflare-builds"}]} 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.

## Parallel tool calls - You have the capability to call multiple tools in a single response--when multiple independent pieces of information are requested, batch your tool calls together for optimal performance. - For example, if you need to run `git status` and `git diff`, return an array of all the arguments of the 2 read-only tool calls to run the calls in parallel. - Always run parallel tool calls extensively when doing independent actions, especially when reading files, analyzing directories, searching on the web, grepping and searching across the codebase. - Never perform dependent terminal commands or writes in parallel.

<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: Wednesday, 2026-07-08 </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 - if asked to summarize a YouTube video, do not name the session until after reading and understanding the full YouTube video transcript - 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 - Secrets/tokens live in `~/.env` (e.g. `HF_TOKEN` for Hugging Face). Source it before use: `set -a; . ~/.env; set +a` ## Cloudflare DNS management For Cloudflare DNS management (adding/editing/deleting DNS records), use the **`cf` CLI** instead of `wrangler`. Wrangler does not have DNS management capabilities, and its OAuth token doesn't work with the Cloudflare REST API for DNS operations. ### Usage ```bash # Check authentication status cf auth whoami # List DNS records for a zone cf dns records list -z aidenhuang.com # Add a DNS record cf dns records create -z aidenhuang.com --type CNAME --name devin --content "target.example.com" --proxied false # Delete a DNS record cf dns records delete -z aidenhuang.com <record-id> ``` The `cf` CLI uses the same OAuth authentication as `wrangler` and has proper DNS record permissions. ## 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. ## Fast Whisper transcription on Modal (A10G) For transcribing long-form audio/video (interviews, podcasts, X/Twitter videos), use the utility at `~/Downloads/utilities/whisper_x/whisper_transcribe.py`. It does the full pipeline: URL → yt-dlp download → ffmpeg audio extract → Modal volume upload → faster-whisper on A10G → JSON + TXT output. Validated at **2.3 min wall clock for 65 min of audio** (no caching at any layer). ### Usage Shell alias (defined in `~/.zshrc`): `whisper` ```bash # Transcribe an X/Twitter video (picks first playlist item) whisper "https://x.com/.../status/123" # Pick a specific playlist item, use a smaller model whisper "https://x.com/..." --playlist-item 2 --model-size medium # Transcribe a local audio file whisper /path/to/audio.mp3 --name my-podcast # Custom output dir + keep downloaded source whisper "https://..." --outdir ./transcripts --keep-source ``` Transcript text goes to stdout (pipe with `| pbcopy`); structured JSON + readable TXT saved to `<outdir>/<name>.json` and `<outdir>/<name>.txt`. ### Key optimizations (vs naive T4 run that took 11.7 min) - **A10G GPU** (~8x fp16 throughput vs T4; Modal ~$0.60/hr vs ~$0.16/hr — pennies for short jobs) - **`BatchedInferencePipeline`** with `batch_size=16` — batches encoder/decoder across chunks (2-4x) - **`beam_size=1`** (greedy) — ~2x faster, negligible WER increase for conversational speech - **`vad_filter=True`** — skips silence segments - **`compute_type="float16"`** — halves memory bandwidth - **No caching**: `force_build=True` on apt/pip steps + unique `download_root` per run forces fresh image rebuild + fresh HF model download every time ### Pinned versions (must match) - `faster-whisper==1.1.1` (provides `BatchedInferencePipeline`) - `ctranslate2==4.8.0` - Base image: `nvidia/cuda:12.6.3-cudnn-runtime-ubuntu22.04` (provides `libcublas.so.12`; `debian_slim` fails with `RuntimeError: Library libcublas.so.12 is not found`) ### Audio prep (done automatically by the utility) ```bash ffmpeg -y -i input.mp4 -vn -ac 1 -ar 16000 -c:a aac -b:a 64k audio.m4a ``` Mono 16kHz 64kbps AAC — a 65-min video (151 MB stream) becomes ~35 MB audio. ### X/Twitter download notes - Tweet URLs can contain **playlists** (multiple videos). Use `--playlist-item N` to pick one. - Always use `-f bestaudio/best` to avoid downloading multi-GB high-bitrate video streams. - A 65-min interview's video variant can be 2.8+ GB; audio-only is ~63 MB (128 kbps). ### Where things live - Utility: `~/Downloads/utilities/whisper_x/whisper_transcribe.py` - Strategy doc: `~/Downloads/utilities/whisper_x/STRATEGY.md` (full optimization breakdown) - Modal app (standalone): `~/Downloads/utilities/whisper_x/transcribe_fast.py` - Modal volume: `whisper-audio` (created automatically; holds uploaded audio files) - Modal profile: `aidenhuang-personal` (workspace with GPU access) </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 ANY skill — built-in OR repository — clearly matches the user's request or the current task, invoke it with the `skill` tool immediately at the start of the session. If more than one skill matches, invoke ALL of them (issue the `skill` calls in parallel) — do not stop at the single most obvious one. - **agents-sdk**: Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable execution, queues, retries, observability, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/agents-sdk/SKILL.md) - **wrangler**: Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/wrangler/SKILL.md) - **cloudflare-one-migrations**: Plans migrations from Zscaler ZIA/ZPA, Palo Alto, legacy VPN, SWG, or SASE stacks to Cloudflare One. Use for migration assessments, policy mapping, rollout plans, and parity/gap analysis. (source: /Users/root1/.codeium/windsurf/skills/cloudflare-one-migrations/SKILL.md) - **cloudflare-one**: Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when designing, configuring, troubleshooting, or reviewing Cloudflare One deployments. Retrieval-first: use current Cloudflare docs/API schemas instead of embedded product docs. (source: /Users/root1/.codeium/windsurf/skills/cloudflare-one/SKILL.md) - **sandbox-sdk**: Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/sandbox-sdk/SKILL.md) - **sandbox-sdk**: Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.claude/skills/sandbox-sdk/SKILL.md) - **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) - **wrangler**: Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.agents/skills/wrangler/SKILL.md) - **agents-sdk**: Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable execution, queues, retries, observability, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.agents/skills/agents-sdk/SKILL.md) - **web-perf**: Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge. (source: /Users/root1/.agents/skills/web-perf/SKILL.md) - **turnstile-spin**: Set up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write the frontend snippets, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form from bots, or fix a Turnstile integration. Mirrors developers.cloudflare.com/turnstile/spin. (source: /Users/root1/.codeium/windsurf/skills/turnstile-spin/SKILL.md) - **durable-objects**: Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.codeium/windsurf/skills/durable-objects/SKILL.md) - **cloudflare**: Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.agents/skills/cloudflare/SKILL.md) - **turnstile-spin**: Set up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write the frontend snippets, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form from bots, or fix a Turnstile integration. Mirrors developers.cloudflare.com/turnstile/spin. (source: /Users/root1/.config/devin/skills/turnstile-spin/SKILL.md) - **cloudflare-email-service**: Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing). Use when building email sending (Workers binding or REST API), email routing, Agents SDK email handling, or integrating email into any app — Workers, Node.js, Python, Go, etc. Also use for email deliverability, SPF/DKIM/DMARC, wrangler email setup, MCP email tools, or when a coding agent needs to send emails. Even for simple requests like "add email to my Worker" — this skill has critical config details. (source: /Users/root1/.codeium/windsurf/skills/cloudflare-email-service/SKILL.md) - **workers-best-practices**: Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/workers-best-practices/SKILL.md) - **cloudflare-agent-setup**: (source: /Users/root1/.devin/skills/cloudflare-agent-setup/SKILL.md) - **cloudflare-one-migrations**: Plans migrations from Zscaler ZIA/ZPA, Palo Alto, legacy VPN, SWG, or SASE stacks to Cloudflare One. Use for migration assessments, policy mapping, rollout plans, and parity/gap analysis. (source: /Users/root1/.config/devin/skills/cloudflare-one-migrations/SKILL.md) - **workers-best-practices**: Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.claude/skills/workers-best-practices/SKILL.md) - **durable-objects**: Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/durable-objects/SKILL.md) - **find-skills**: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill. (source: /Users/root1/.agents/skills/find-skills/SKILL.md) - **cloudflare-one**: Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when designing, configuring, troubleshooting, or reviewing Cloudflare One deployments. Retrieval-first: use current Cloudflare docs/API schemas instead of embedded product docs. (source: /Users/root1/.config/devin/skills/cloudflare-one/SKILL.md) - **cloudflare**: Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/cloudflare/SKILL.md) - **cloudflare-email-service**: Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing). Use when building email sending (Workers binding or REST API), email routing, Agents SDK email handling, or integrating email into any app — Workers, Node.js, Python, Go, etc. Also use for email deliverability, SPF/DKIM/DMARC, wrangler email setup, MCP email tools, or when a coding agent needs to send emails. Even for simple requests like "add email to my Worker" — this skill has critical config details. (source: /Users/root1/.config/devin/skills/cloudflare-email-service/SKILL.md) - **web-perf**: Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/web-perf/SKILL.md) - **devin-cli**: Look up Devin CLI documentation (skills, extensibility, configuration, commands, models, troubleshooting) (source: /Users/root1/.local/share/devin/cli/_versions/3000.1.27/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>

{ "todos": [ { "content": "Extract auto-generated captions/transcript from the YouTube video", "status": "in_progress" }, { "content": "Read and understand the full transcript", "status": "pending" }, { "content": "Produce a concise summary of the video", "status": "pending" } ] }

Todos have been modified successfully. Ensure that you continue to use the todo list to track your progress. Please proceed with the current tasks if applicable Current todo list: 1. [~] Extract auto-generated captions/transcript from the YouTube video [in_progress] 2. [ ] Read and understand the full transcript [pending] 3. [ ] Produce a concise summary of the video [pending]

{ "command": "cd /var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/tmp.aHg2JKVjMi && yt-dlp --write-auto-sub --skip-download --sub-langs en --convert-subs srt --no-warnings \"https://www.youtube.com/watch?v=jSleBySk9sI\"", "timeout": 60000 }

Output from command in shell d544f9: [youtube] Extracting URL: https://www.youtube.com/watch?v=jSleBySk9sI [youtube] jSleBySk9sI: Downloading webpage [youtube] jSleBySk9sI: Downloading tv client config [youtube] jSleBySk9sI: Downloading player ecd4b80a-main [youtube] jSleBySk9sI: Downloading tv player API JSON [youtube] jSleBySk9sI: Downloading android sdkless player API JSON [youtube] [jsc:deno] Solving JS challenges using deno [info] jSleBySk9sI: Downloading subtitles: en [info] jSleBySk9sI: Downloading 1 format(s): 139-20 [info] Writing video subtitles to: Nobody Is Coming to Save Your Career [jSleBySk9sI].en.vtt [download] Destination: Nobody Is Coming to Save Your Career [jSleBySk9sI].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 Unknown B/s (00:00:00) [download] 15.00KiB at 6.95MiB/s (00:00:00) [download] 31.00KiB at 2.99MiB/s (00:00:00) [download] 63.00KiB at 3.17MiB/s (00:00:00) [download] 127.00KiB at 3.55MiB/s (00:00:00) [download] 157.99KiB at 3.97MiB/s (00:00:00) [download] 100% of 157.99KiB in 00:00:00 at 851.90KiB/s [SubtitlesConvertor] Converting subtitles Deleting original file Nobody Is Coming to Save Your Career [jSleBySk9sI].en.vtt (pass -k to keep) Exit code: 0

Output from command in shell 8ed9fc: total 168 drwx------ 3 root1 staff 96 Jul 8 23:47 . drwx-----T@ 270 root1 staff 8640 Jul 8 23:47 .. -rw-r--r-- 1 root1 staff 85649 Jul 8 23:47 Nobody Is Coming to Save Your Career [jSleBySk9sI].en.srt Exit code: 0

<file-view path="/var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/tmp.aHg2JKVjMi/Nobody Is Coming to Save Your Career [jSleBySk9sI].en.srt" start_line="1" end_line="1087" total_lines="4675"> 1|1 2|00:00:00,000 --> 00:00:02,030 3| 4|Nobody is coming to save your career. 5| 6|2 7|00:00:02,030 --> 00:00:02,040 8|Nobody is coming to save your career. 9| 10| 11|3 12|00:00:02,040 --> 00:00:04,430 13|Nobody is coming to save your career. 14|Not your manager, not your skip level, 15| 16|4 17|00:00:04,430 --> 00:00:04,440 18|Not your manager, not your skip level, 19| 20| 21|5 22|00:00:04,440 --> 00:00:06,030 23|Not your manager, not your skip level, 24|not the company you've given the last 25| 26|6 27|00:00:06,030 --> 00:00:06,040 28|not the company you've given the last 29| 30| 31|7 32|00:00:06,040 --> 00:00:07,830 33|not the company you've given the last 34|five years of your life to. The truth 35| 36|8 37|00:00:07,830 --> 00:00:07,840 38|five years of your life to. The truth 39| 40| 41|9 42|00:00:07,840 --> 00:00:11,030 43|five years of your life to. The truth 44|is, in 2026, waiting to be noticed isn't 45| 46|10 47|00:00:11,030 --> 00:00:11,040 48|is, in 2026, waiting to be noticed isn't 49| 50| 51|11 52|00:00:11,040 --> 00:00:13,550 53|is, in 2026, waiting to be noticed isn't 54|just low. It's dangerous to your career. 55| 56|12 57|00:00:13,550 --> 00:00:13,560 58|just low. It's dangerous to your career. 59| 60| 61|13 62|00:00:13,560 --> 00:00:15,310 63|just low. It's dangerous to your career. 64|AI is compressing the value of the 65| 66|14 67|00:00:15,310 --> 00:00:15,320 68|AI is compressing the value of the 69| 70| 71|15 72|00:00:15,320 --> 00:00:16,910 73|AI is compressing the value of the 74|comfortable work that you're doing right 75| 76|16 77|00:00:16,910 --> 00:00:16,920 78|comfortable work that you're doing right 79| 80| 81|17 82|00:00:16,920 --> 00:00:18,990 83|comfortable work that you're doing right 84|now. The stuff that you're great at, the 85| 86|18 87|00:00:18,990 --> 00:00:19,000 88|now. The stuff that you're great at, the 89| 90| 91|19 92|00:00:19,000 --> 00:00:20,990 93|now. The stuff that you're great at, the 94|stuff that makes you reliable, that's 95| 96|20 97|00:00:20,990 --> 00:00:21,000 98|stuff that makes you reliable, that's 99| 100| 101|21 102|00:00:21,000 --> 00:00:22,430 103|stuff that makes you reliable, that's 104|exactly the stuff that's getting 105| 106|22 107|00:00:22,430 --> 00:00:22,440 108|exactly the stuff that's getting 109| 110| 111|23 112|00:00:22,440 --> 00:00:24,870 113|exactly the stuff that's getting 114|automated first. Being a passenger in 115| 116|24 117|00:00:24,870 --> 00:00:24,880 118|automated first. Being a passenger in 119| 120| 121|25 122|00:00:24,880 --> 00:00:26,830 123|automated first. Being a passenger in 124|your career you suggest means slow 125| 126|26 127|00:00:26,830 --> 00:00:26,840 128|your career you suggest means slow 129| 130| 131|27 132|00:00:26,840 --> 00:00:27,830 133|your career you suggest means slow 134|growth. 135| 136|28 137|00:00:27,830 --> 00:00:27,840 138|growth. 139| 140| 141|29 142|00:00:27,840 --> 00:00:30,070 143|growth. 144|Today, it means getting left behind. In 145| 146|30 147|00:00:30,070 --> 00:00:30,080 148|Today, it means getting left behind. In 149| 150| 151|31 152|00:00:30,080 --> 00:00:31,710 153|Today, it means getting left behind. In 154|this video, I'm going to break down the 155| 156|32 157|00:00:31,710 --> 00:00:31,720 158|this video, I'm going to break down the 159| 160| 161|33 162|00:00:31,720 --> 00:00:33,670 163|this video, I'm going to break down the 164|three truths that you need to accept to 165| 166|34 167|00:00:33,670 --> 00:00:33,680 168|three truths that you need to accept to 169| 170| 171|35 172|00:00:33,680 --> 00:00:35,870 173|three truths that you need to accept to 174|take back control, so that by the end 175| 176|36 177|00:00:35,870 --> 00:00:35,880 178|take back control, so that by the end 179| 180| 181|37 182|00:00:35,880 --> 00:00:37,270 183|take back control, so that by the end 184|you'll know exactly where you've been 185| 186|38 187|00:00:37,270 --> 00:00:37,280 188|you'll know exactly where you've been 189| 190| 191|39 192|00:00:37,280 --> 00:00:39,550 193|you'll know exactly where you've been 194|handing over your career growth. And 195| 196|40 197|00:00:39,550 --> 00:00:39,560 198|handing over your career growth. And 199| 200| 201|41 202|00:00:39,560 --> 00:00:41,550 203|handing over your career growth. And 204|what to do about it this week. The 205| 206|42 207|00:00:41,550 --> 00:00:41,560 208|what to do about it this week. The 209| 210| 211|43 212|00:00:41,560 --> 00:00:43,630 213|what to do about it this week. The 214|fastest way to endanger your career is 215| 216|44 217|00:00:43,630 --> 00:00:43,640 218|fastest way to endanger your career is 219| 220| 221|45 222|00:00:43,640 --> 00:00:46,070 223|fastest way to endanger your career is 224|to become reliable at low impact work. 225| 226|46 227|00:00:46,070 --> 00:00:46,080 228|to become reliable at low impact work. 229| 230| 231|47 232|00:00:46,080 --> 00:00:48,310 233|to become reliable at low impact work. 234|You'll be rewarded with more of it until 235| 236|48 237|00:00:48,310 --> 00:00:48,320 238|You'll be rewarded with more of it until 239| 240| 241|49 242|00:00:48,320 --> 00:00:49,910 243|You'll be rewarded with more of it until 244|you're replaced by the AI that was 245| 246|50 247|00:00:49,910 --> 00:00:49,920 248|you're replaced by the AI that was 249| 250| 251|51 252|00:00:49,920 --> 00:00:52,110 253|you're replaced by the AI that was 254|trained on your priors. Now, I know some 255| 256|52 257|00:00:52,110 --> 00:00:52,120 258|trained on your priors. Now, I know some 259| 260| 261|53 262|00:00:52,120 --> 00:00:53,950 263|trained on your priors. Now, I know some 264|of you are watching this thinking, "I 265| 266|54 267|00:00:53,950 --> 00:00:53,960 268|of you are watching this thinking, "I 269| 270| 271|55 272|00:00:53,960 --> 00:00:55,910 273|of you are watching this thinking, "I 274|don't care about climbing the ladder. I 275| 276|56 277|00:00:55,910 --> 00:00:55,920 278|don't care about climbing the ladder. I 279| 280| 281|57 282|00:00:55,920 --> 00:00:58,030 283|don't care about climbing the ladder. I 284|like my job and where I'm at. I'm not 285| 286|58 287|00:00:58,030 --> 00:00:58,040 288|like my job and where I'm at. I'm not 289| 290| 291|59 292|00:00:58,040 --> 00:01:00,790 293|like my job and where I'm at. I'm not 294|trying to be a VP." And that's fair. 295| 296|60 297|00:01:00,790 --> 00:01:00,800 298|trying to be a VP." And that's fair. 299| 300| 301|61 302|00:01:00,800 --> 00:01:02,950 303|trying to be a VP." And that's fair. 304|Wanting more scope is a choice and not 305| 306|62 307|00:01:02,950 --> 00:01:02,960 308|Wanting more scope is a choice and not 309| 310| 311|63 312|00:01:02,960 --> 00:01:04,790 313|Wanting more scope is a choice and not 314|an obligation. And if you built a life 315| 316|64 317|00:01:04,790 --> 00:01:04,800 318|an obligation. And if you built a life 319| 320| 321|65 322|00:01:04,800 --> 00:01:07,230 323|an obligation. And if you built a life 324|that you genuinely like, I respect that. 325| 326|66 327|00:01:07,230 --> 00:01:07,240 328|that you genuinely like, I respect that. 329| 330| 331|67 332|00:01:07,240 --> 00:01:08,670 333|that you genuinely like, I respect that. 334|But staying where you are is not the 335| 336|68 337|00:01:08,670 --> 00:01:08,680 338|But staying where you are is not the 339| 340| 341|69 342|00:01:08,680 --> 00:01:10,750 343|But staying where you are is not the 344|same thing as being safe. The work that 345| 346|70 347|00:01:10,750 --> 00:01:10,760 348|same thing as being safe. The work that 349| 350| 351|71 352|00:01:10,760 --> 00:01:12,310 353|same thing as being safe. The work that 354|you're doing today is the work that the 355| 356|72 357|00:01:12,310 --> 00:01:12,320 358|you're doing today is the work that the 359| 360| 361|73 362|00:01:12,320 --> 00:01:14,150 363|you're doing today is the work that the 364|models are getting good at tomorrow. You 365| 366|74 367|00:01:14,150 --> 00:01:14,160 368|models are getting good at tomorrow. You 369| 370| 371|75 372|00:01:14,160 --> 00:01:15,670 373|models are getting good at tomorrow. You 374|don't have to want a promotion to care 375| 376|76 377|00:01:15,670 --> 00:01:15,680 378|don't have to want a promotion to care 379| 380| 381|77 382|00:01:15,680 --> 00:01:17,430 383|don't have to want a promotion to care 384|about this. You just have to want to 385| 386|78 387|00:01:17,430 --> 00:01:17,440 388|about this. You just have to want to 389| 390| 391|79 392|00:01:17,440 --> 00:01:19,510 393|about this. You just have to want to 394|still have a job in five years. So, 395| 396|80 397|00:01:19,510 --> 00:01:19,520 398|still have a job in five years. So, 399| 400| 401|81 402|00:01:19,520 --> 00:01:21,310 403|still have a job in five years. So, 404|whether you're trying to grow or trying 405| 406|82 407|00:01:21,310 --> 00:01:21,320 408|whether you're trying to grow or trying 409| 410| 411|83 412|00:01:21,320 --> 00:01:23,230 413|whether you're trying to grow or trying 414|to hold your ground, the rest of this 415| 416|84 417|00:01:23,230 --> 00:01:23,240 418|to hold your ground, the rest of this 419| 420| 421|85 422|00:01:23,240 --> 00:01:25,470 423|to hold your ground, the rest of this 424|video still applies. Because the person 425| 426|86 427|00:01:25,470 --> 00:01:25,480 428|video still applies. Because the person 429| 430| 431|87 432|00:01:25,480 --> 00:01:27,510 433|video still applies. Because the person 434|who owns your career isn't your manager 435| 436|88 437|00:01:27,510 --> 00:01:27,520 438|who owns your career isn't your manager 439| 440| 441|89 442|00:01:27,520 --> 00:01:29,270 443|who owns your career isn't your manager 444|and it isn't your company. 445| 446|90 447|00:01:29,270 --> 00:01:29,280 448|and it isn't your company. 449| 450| 451|91 452|00:01:29,280 --> 00:01:30,870 453|and it isn't your company. 454|It's you. Here's what I want you to 455| 456|92 457|00:01:30,870 --> 00:01:30,880 458|It's you. Here's what I want you to 459| 460| 461|93 462|00:01:30,880 --> 00:01:32,790 463|It's you. Here's what I want you to 464|understand about where you work. The 465| 466|94 467|00:01:32,790 --> 00:01:32,800 468|understand about where you work. The 469| 470| 471|95 472|00:01:32,800 --> 00:01:35,150 473|understand about where you work. The 474|company is a simple machine. It's just 475| 476|96 477|00:01:35,150 --> 00:01:35,160 478|company is a simple machine. It's just 479| 480| 481|97 482|00:01:35,160 --> 00:01:37,350 483|company is a simple machine. It's just 484|trying to maximize profit. It doesn't 485| 486|98 487|00:01:37,350 --> 00:01:37,360 488|trying to maximize profit. It doesn't 489| 490| 491|99 492|00:01:37,360 --> 00:01:39,110 493|trying to maximize profit. It doesn't 494|love you. It doesn't hate you. It 495| 496|100 497|00:01:39,110 --> 00:01:39,120 498|love you. It doesn't hate you. It 499| 500| 501|101 502|00:01:39,120 --> 00:01:41,030 503|love you. It doesn't hate you. It 504|doesn't care about your family. It's 505| 506|102 507|00:01:41,030 --> 00:01:41,040 508|doesn't care about your family. It's 509| 510| 511|103 512|00:01:41,040 --> 00:01:43,350 513|doesn't care about your family. It's 514|running this naive algorithm. And the 515| 516|104 517|00:01:43,350 --> 00:01:43,360 518|running this naive algorithm. And the 519| 520| 521|105 522|00:01:43,360 --> 00:01:45,670 523|running this naive algorithm. And the 524|algorithm looks like this. Add work to 525| 526|106 527|00:01:45,670 --> 00:01:45,680 528|algorithm looks like this. Add work to 529| 530| 531|107 532|00:01:45,680 --> 00:01:47,870 533|algorithm looks like this. Add work to 534|your plate until you push back. If you 535| 536|108 537|00:01:47,870 --> 00:01:47,880 538|your plate until you push back. If you 539| 540| 541|109 542|00:01:47,880 --> 00:01:50,510 543|your plate until you push back. If you 544|don't push back, add some more work. My 545| 546|110 547|00:01:50,510 --> 00:01:50,520 548|don't push back, add some more work. My 549| 550| 551|111 552|00:01:50,520 --> 00:01:52,830 553|don't push back, add some more work. My 554|friend Ethan Evans, a former Amazon VP, 555| 556|112 557|00:01:52,830 --> 00:01:52,840 558|friend Ethan Evans, a former Amazon VP, 559| 560| 561|113 562|00:01:52,840 --> 00:01:54,950 563|friend Ethan Evans, a former Amazon VP, 564|says, "It isn't evil. It's just 565| 566|114 567|00:01:54,950 --> 00:01:54,960 568|says, "It isn't evil. It's just 569| 570| 571|115 572|00:01:54,960 --> 00:01:57,030 573|says, "It isn't evil. It's just 574|business." And he's right. The company 575| 576|116 577|00:01:57,030 --> 00:01:57,040 578|business." And he's right. The company 579| 580| 581|117 582|00:01:57,040 --> 00:01:58,950 583|business." And he's right. The company 584|isn't trying to hurt you. It just 585| 586|118 587|00:01:58,950 --> 00:01:58,960 588|isn't trying to hurt you. It just 589| 590| 591|119 592|00:01:58,960 --> 00:02:00,870 593|isn't trying to hurt you. It just 594|doesn't care if it does. So, the job of 595| 596|120 597|00:02:00,870 --> 00:02:00,880 598|doesn't care if it does. So, the job of 599| 600| 601|121 602|00:02:00,880 --> 00:02:03,030 603|doesn't care if it does. So, the job of 604|managing your career falls squarely on 605| 606|122 607|00:02:03,030 --> 00:02:03,040 608|managing your career falls squarely on 609| 610| 611|123 612|00:02:03,040 --> 00:02:05,110 613|managing your career falls squarely on 614|you. Nobody else is sitting there 615| 616|124 617|00:02:05,110 --> 00:02:05,120 618|you. Nobody else is sitting there 619| 620| 621|125 622|00:02:05,120 --> 00:02:07,030 623|you. Nobody else is sitting there 624|thinking about whether you're growing. 625| 626|126 627|00:02:07,030 --> 00:02:07,040 628|thinking about whether you're growing. 629| 630| 631|127 632|00:02:07,040 --> 00:02:09,389 633|thinking about whether you're growing. 634|Your manager has their own problems. The 635| 636|128 637|00:02:09,389 --> 00:02:09,399 638|Your manager has their own problems. The 639| 640| 641|129 642|00:02:09,399 --> 00:02:12,030 643|Your manager has their own problems. The 644|company has its road map. The algorithm 645| 646|130 647|00:02:12,030 --> 00:02:12,040 648|company has its road map. The algorithm 649| 650| 651|131 652|00:02:12,040 --> 00:02:14,350 653|company has its road map. The algorithm 654|just wants more output. None of those 655| 656|132 657|00:02:14,350 --> 00:02:14,360 658|just wants more output. None of those 659| 660| 661|133 662|00:02:14,360 --> 00:02:16,550 663|just wants more output. None of those 664|things care about your trajectory. 665| 666|134 667|00:02:16,550 --> 00:02:16,560 668|things care about your trajectory. 669| 670| 671|135 672|00:02:16,560 --> 00:02:18,470 673|things care about your trajectory. 674|You're the only one that can. Suppose 675| 676|136 677|00:02:18,470 --> 00:02:18,480 678|You're the only one that can. Suppose 679| 680| 681|137 682|00:02:18,480 --> 00:02:19,790 683|You're the only one that can. Suppose 684|you've done the work of figuring out the 685| 686|138 687|00:02:19,790 --> 00:02:19,800 688|you've done the work of figuring out the 689| 690| 691|139 692|00:02:19,800 --> 00:02:21,550 693|you've done the work of figuring out the 694|next step of your career, and you've 695| 696|140 697|00:02:21,550 --> 00:02:21,560 698|next step of your career, and you've 699| 700| 701|141 702|00:02:21,560 --> 00:02:23,070 703|next step of your career, and you've 704|decided that what you need is bigger 705| 706|142 707|00:02:23,070 --> 00:02:23,080 708|decided that what you need is bigger 709| 710| 711|143 712|00:02:23,080 --> 00:02:24,990 713|decided that what you need is bigger 714|scope, like a project that stretches 715| 716|144 717|00:02:24,990 --> 00:02:25,000 718|scope, like a project that stretches 719| 720| 721|145 722|00:02:25,000 --> 00:02:27,070 723|scope, like a project that stretches 724|you. Something that would actually move 725| 726|146 727|00:02:27,070 --> 00:02:27,080 728|you. Something that would actually move 729| 730| 731|147 732|00:02:27,080 --> 00:02:28,949 733|you. Something that would actually move 734|you forward instead of producing more of 735| 736|148 737|00:02:28,949 --> 00:02:28,959 738|you forward instead of producing more of 739| 740| 741|149 742|00:02:28,959 --> 00:02:30,670 743|you forward instead of producing more of 744|what you already have proven that you 745| 746|150 747|00:02:30,670 --> 00:02:30,680 748|what you already have proven that you 749| 750| 751|151 752|00:02:30,680 --> 00:02:32,870 753|what you already have proven that you 754|can do. That work is not coming to you 755| 756|152 757|00:02:32,870 --> 00:02:32,880 758|can do. That work is not coming to you 759| 760| 761|153 762|00:02:32,880 --> 00:02:35,550 763|can do. That work is not coming to you 764|by default. The algorithm is never going 765| 766|154 767|00:02:35,550 --> 00:02:35,560 768|by default. The algorithm is never going 769| 770| 771|155 772|00:02:35,560 --> 00:02:37,790 773|by default. The algorithm is never going 774|to hand it to you. Your manager is not 775| 776|156 777|00:02:37,790 --> 00:02:37,800 778|to hand it to you. Your manager is not 779| 780| 781|157 782|00:02:37,800 --> 00:02:39,590 783|to hand it to you. Your manager is not 784|going to walk over to you and offer it 785| 786|158 787|00:02:39,590 --> 00:02:39,600 788|going to walk over to you and offer it 789| 790| 791|159 792|00:02:39,600 --> 00:02:42,430 793|going to walk over to you and offer it 794|unprompted. The company has no incentive 795| 796|160 797|00:02:42,430 --> 00:02:42,440 798|unprompted. The company has no incentive 799| 800| 801|161 802|00:02:42,440 --> 00:02:44,630 803|unprompted. The company has no incentive 804|to disrupt the situation that's already 805| 806|162 807|00:02:44,630 --> 00:02:44,640 808|to disrupt the situation that's already 809| 810| 811|163 812|00:02:44,640 --> 00:02:46,510 813|to disrupt the situation that's already 814|working for them. You're already being 815| 816|164 817|00:02:46,510 --> 00:02:46,520 818|working for them. You're already being 819| 820| 821|165 822|00:02:46,520 --> 00:02:48,070 823|working for them. You're already being 824|stretched doing a high volume of 825| 826|166 827|00:02:48,070 --> 00:02:48,080 828|stretched doing a high volume of 829| 830| 831|167 832|00:02:48,080 --> 00:02:49,710 833|stretched doing a high volume of 834|reliable work, and from their 835| 836|168 837|00:02:49,710 --> 00:02:49,720 838|reliable work, and from their 839| 840| 841|169 842|00:02:49,720 --> 00:02:52,150 843|reliable work, and from their 844|perspective, that's ideal. 845| 846|170 847|00:02:52,150 --> 00:02:52,160 848|perspective, that's ideal. 849| 850| 851|171 852|00:02:52,160 --> 00:02:53,990 853|perspective, that's ideal. 854|Why would they change that? 855| 856|172 857|00:02:53,990 --> 00:02:54,000 858|Why would they change that? 859| 860| 861|173 862|00:02:54,000 --> 00:02:56,070 863|Why would they change that? 864|They're not going to. You have to be the 865| 866|174 867|00:02:56,070 --> 00:02:56,080 868|They're not going to. You have to be the 869| 870| 871|175 872|00:02:56,080 --> 00:02:58,150 873|They're not going to. You have to be the 874|one that changes it. You have to be the 875| 876|176 877|00:02:58,150 --> 00:02:58,160 878|one that changes it. You have to be the 879| 880| 881|177 882|00:02:58,160 --> 00:02:59,910 883|one that changes it. You have to be the 884|one who starts the conversation and 885| 886|178 887|00:02:59,910 --> 00:02:59,920 888|one who starts the conversation and 889| 890| 891|179 892|00:02:59,920 --> 00:03:02,150 893|one who starts the conversation and 894|says, "I need work that would actually 895| 896|180 897|00:03:02,150 --> 00:03:02,160 898|says, "I need work that would actually 899| 900| 901|181 902|00:03:02,160 --> 00:03:04,630 903|says, "I need work that would actually 904|grow me." Because if you don't, nothing 905| 906|182 907|00:03:04,630 --> 00:03:04,640 908|grow me." Because if you don't, nothing 909| 910| 911|183 912|00:03:04,640 --> 00:03:06,830 913|grow me." Because if you don't, nothing 914|will happen. You stay where you are, 915| 916|184 917|00:03:06,830 --> 00:03:06,840 918|will happen. You stay where you are, 919| 920| 921|185 922|00:03:06,840 --> 00:03:08,750 923|will happen. You stay where you are, 924|getting more of the same work until 925| 926|186 927|00:03:08,750 --> 00:03:08,760 928|getting more of the same work until 929| 930| 931|187 932|00:03:08,760 --> 00:03:10,190 933|getting more of the same work until 934|enough years pass that you stop 935| 936|188 937|00:03:10,190 --> 00:03:10,200 938|enough years pass that you stop 939| 940| 941|189 942|00:03:10,200 --> 00:03:11,750 943|enough years pass that you stop 944|believing that anything different is 945| 946|190 947|00:03:11,750 --> 00:03:11,760 948|believing that anything different is 949| 950| 951|191 952|00:03:11,760 --> 00:03:13,710 953|believing that anything different is 954|possible. I fell into this trap as a 955| 956|192 957|00:03:13,710 --> 00:03:13,720 958|possible. I fell into this trap as a 959| 960| 961|193 962|00:03:13,720 --> 00:03:16,070 963|possible. I fell into this trap as a 964|senior engineer at Amazon. I was doing 965| 966|194 967|00:03:16,070 --> 00:03:16,080 968|senior engineer at Amazon. I was doing 969| 970| 971|195 972|00:03:16,080 --> 00:03:18,229 973|senior engineer at Amazon. I was doing 974|well and getting strong reviews. But I 975| 976|196 977|00:03:18,229 --> 00:03:18,239 978|well and getting strong reviews. But I 979| 980| 981|197 982|00:03:18,239 --> 00:03:20,790 983|well and getting strong reviews. But I 984|wasn't growing. I was buried in project 985| 986|198 987|00:03:20,790 --> 00:03:20,800 988|wasn't growing. I was buried in project 989| 990| 991|199 992|00:03:20,800 --> 00:03:23,110 993|wasn't growing. I was buried in project 994|work that I already knew how to do. And 995| 996|200 997|00:03:23,110 --> 00:03:23,120 998|work that I already knew how to do. And 999| 1000| 1001|201 1002|00:03:23,120 --> 00:03:24,750 1003|work that I already knew how to do. And 1004|when I finally went to my manager and 1005| 1006|202 1007|00:03:24,750 --> 00:03:24,760 1008|when I finally went to my manager and 1009| 1010| 1011|203 1012|00:03:24,760 --> 00:03:27,390 1013|when I finally went to my manager and 1014|asked scope, his first reaction wasn't 1015| 1016|204 1017|00:03:27,390 --> 00:03:27,400 1018|asked scope, his first reaction wasn't 1019| 1020| 1021|205 1022|00:03:27,400 --> 00:03:30,390 1023|asked scope, his first reaction wasn't 1024|excitement. It was, "Steve, but you're 1025| 1026|206 1027|00:03:30,390 --> 00:03:30,400 1028|excitement. It was, "Steve, but you're 1029| 1030| 1031|207 1032|00:03:30,400 --> 00:03:32,830 1033|excitement. It was, "Steve, but you're 1034|doing so well where you are." That's the 1035| 1036|208 1037|00:03:32,830 --> 00:03:32,840 1038|doing so well where you are." That's the 1039| 1040| 1041|209 1042|00:03:32,840 --> 00:03:34,710 1043|doing so well where you are." That's the 1044|voice of the trap. That's what your 1045| 1046|210 1047|00:03:34,710 --> 00:03:34,720 1048|voice of the trap. That's what your 1049| 1050| 1051|211 1052|00:03:34,720 --> 00:03:36,670 1053|voice of the trap. That's what your 1054|company sounds like when it's benefiting 1055| 1056|212 1057|00:03:36,670 --> 00:03:36,680 1058|company sounds like when it's benefiting 1059| 1060| 1061|213 1062|00:03:36,680 --> 00:03:38,630 1063|company sounds like when it's benefiting 1064|from your stagnation. And this is why it 1065| 1066|214 1067|00:03:38,630 --> 00:03:38,640 1068|from your stagnation. And this is why it 1069| 1070| 1071|215 1072|00:03:38,640 --> 00:03:41,509 1073|from your stagnation. And this is why it 1074|matters more in 2026 than it ever has. 1075| 1076|216 1077|00:03:41,509 --> 00:03:41,519 1078|matters more in 2026 than it ever has. 1079| 1080| 1081|217 1082|00:03:41,519 --> 00:03:43,390 1083|matters more in 2026 than it ever has. 1084|The work that you're reliable at is the 1085| 1086|218 1087|00:03:43,390 --> 00:03:43,400 </file-view>

{ "command": "python3 - <<'PY'\nimport re, os\nsrt_path = \"/var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/tmp.aHg2JKVjMi/Nobody Is Coming to Save Your Career [jSleBySk9sI].en.srt\"\nout_path = \"/var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/tmp.aHg2JKVjMi/transcript.txt\"\nwith open(srt_path, 'r', encoding='utf-8') as f:\n text = f.read()\n# remove SRT block numbers and timing lines, keep only text lines\nlines = text.splitlines()\nout_lines = []\nfor line in lines:\n line = line.strip()\n if not line:\n continue\n if re.fullmatch(r'\\d+', line):\n continue\n if re.match(r'\\d{2}:\\d{2}:\\d{2},\\d{3}\\s*-->\\s*\\d{2}:\\d{2}:\\d{2},\\d{3}', line):\n continue\n out_lines.append(line)\n# Deduplicate consecutive identical lines (the SRT often repeats across tiny time windows)\nuniq = []\nprev = None\nfor l in out_lines:\n if l != prev:\n uniq.append(l)\n prev = l\nwith open(out_path, 'w', encoding='utf-8') as f:\n f.write('\\n'.join(uniq))\nprint(f\"Wrote {len(uniq)} lines, {os.path.getsize(out_path)} bytes to {out_path}\")\nPY", "timeout": 10000 }

{ "todos": [ { "content": "Extract auto-generated captions/transcript from the YouTube video", "status": "completed" }, { "content": "Read and understand the full transcript", "status": "completed" }, { "content": "Produce a concise summary of the video", "status": "in_progress" } ] }

Todos have been modified successfully. Ensure that you continue to use the todo list to track your progress. Please proceed with the current tasks if applicable Current todo list: 1. [x] Extract auto-generated captions/transcript from the YouTube video [completed] 2. [x] Read and understand the full transcript [completed] 3. [~] Produce a concise summary of the video [in_progress]

Todos have been modified successfully. Ensure that you continue to use the todo list to track your progress. Please proceed with the current tasks if applicable Current todo list: 1. [x] Extract auto-generated captions/transcript from the YouTube video [completed] 2. [x] Read and understand the full transcript [completed] 3. [x] Produce a concise summary of the video [completed]

Here’s a summary of the video "Nobody Is Coming to Save Your Career" based on the auto-generated captions I pulled.

Core argument

In 2026, passively waiting to be noticed is a career risk. The work you’re already great at — the reliable, repetitive stuff — is exactly what AI is automating first. The company, your manager, and your skip-level are not going to rescue your growth. Career ownership is on you.

The three truths

Your company is not your friend; it’s an algorithm.
A company’s goal is profit maximization. It will keep loading work onto your plate until you push back. It has no incentive to hand you a stretch project when you’re already doing reliable work well. If you want bigger scope, you have to ask for it — unprompted offers are rare. The speaker shares his own trap at Amazon: strong reviews, but no growth, and his manager’s first reaction to a scope request was, “Steve, but you’re doing so well where you are.”
Your manager is not your career coach.
Most managers are overloaded, focused on delivery, and often stack-ranked themselves. They default to managing problems, not proactively growing everyone. Citing Gergely Orosz, the speaker notes that even a thoughtful manager may only coach people who explicitly ask for it — so if you haven’t stated your goals, your manager likely assumes you’re content. The fix: in your next 1:1, say exactly what you want — a promotion timeline, an “exceeds” rating, or harder work. That activates your manager as a resource.
If growth isn’t happening, you’re not a victim — you have options.
You can change teams, managers, companies, cities, or start a company. If you’ve tried to activate your manager and still hear “let’s wait six months” for years, the right move is to route around the blocker. The price of career growth is uncomfortable action. The speaker’s worst manager repeatedly missed promotion deadlines; staying was a mistake — a later reorg saved him only by luck.

Closing exercise

Finish two sentences:

My career goal is ___. (concrete)
In the next 12 months, I’m going to make progress by ___. (specific action)

If the second blank is “keep my head down and hope someone notices,” you’re not running your career yet — but you can start today.

The video also includes sponsor/promotion mentions for a Notion custom agent the speaker built and his “Top Tier” coaching program.