# technologytips.blog Fix Library: all AI Fix files 4 files, generated 2026-11-12T21:20:11Z. Each file below starts at a line beginning "=== FIX:" and is complete on its own. License: CC BY 4.0, free to use and share with credit to technologytips.blog. Index: https://technologytips.blog/fixes/index.json === FIX: locked-out-of-1password-app-still-open | https://technologytips.blog/articles/locked-out-of-1password-app-still-open/ | sha256 895870027be5ed152cc1cf02fd11ee07c2e55548f9b1859f4f351af39121d8f9 === --- name: save-1password-items-when-app-is-still-open description: Use when a person forgot their 1Password account password, has no recovery code, and the 1Password app is still open on one device. Walks them through a new account, copying items across and setting up recovery. license: CC BY 4.0. Free to use and share with credit to technologytips.blog. metadata: publisher: technologytips.blog article: https://technologytips.blog/articles/locked-out-of-1password-app-still-open/ article_title: "Stuck with a locked 1Password account while the app is still open? Start here" published: 2026-11-12 platforms: [mac, windows, linux] needs: [none] risk: high version: 1 --- # Save 1Password items when the app is still open *An AI Fix file from technologytips.blog. Give this file to your AI assistant and say: "Read this file, then walk me through it one step at a time." It works on your own computer, and it asks before anything that can't be undone.* ## What this fixes You forgot your 1Password account password, you have no recovery code, and the app is still open on one device. You end up with a new account that has recovery built in, holding copies of your items. This file will not promise a result, it will not get into an account that is not yours, and it cannot recover what 1Password cannot. 1Password says no one can reset an account password. ## Read this first (safety) - Never ask me to paste a password, recovery code, secret key, 2FA code or private key into this chat. If a step needs one, tell me to type it only into the official app or website. - Before any step that deletes, overwrites, signs out, resets or uninstalls anything, stop, tell me exactly what will happen, and wait for me to say yes. - Make or confirm a backup before changing anything you can't undo. - Only use official apps, official download pages and official documentation. Never suggest cracked software, unofficial installers or scripts from unknown sources. - Never turn off a security feature (encryption, 2FA, firewall, antivirus, FileVault, BitLocker) permanently. If a fix needs it off for a moment, say so and turn it back on. - If anything looks different from these steps, stop and tell me instead of guessing. - This file is general help, not professional support. For account recovery, the company that runs the account is the only real authority. - Do not sign out of, quit, uninstall or remove the old account until I say every item has been checked in the new account. - This is only for my own account, or one I am allowed to manage. This file is marked risk high because signing out too early can end my access to the items on screen, and nothing can bring them back. ## What you need - A computer (Mac, Windows or Linux) where the 1Password 8 app is still open and showing my items. - A second email address that the old account does not use. - About an evening, with no rush. Fast is how items get lost. - Nothing to install. ## Instructions for the AI You are helping one person fix one problem on their own computer, using only the steps and sources in this file. Be kind and patient. Say it is not their fault. Go one step at a time and wait for them to say it is done. Read every command aloud in plain words before they run it. Never run a command that deletes, overwrites, moves, signs out, resets or uninstalls without their yes. If your answer would differ from this file, say so and ask. Say "as of November 2026" when you give a menu path, because menus change. If something does not match what they see, stop and help them describe it, word for word. There are no commands in this file. Everything happens in the 1Password app and on 1Password.com, by the reader. ## Questions to ask first Ask these a few at a time, in plain words. If the answer changes the steps, say how. 1. Which computer are you on, and which version of the 1Password app is open? 2. Is the app still open and showing your items right now? If it is closed or locked, stop and use the official page in Sources. 3. Have you looked for a Login item named "1Password Account" in your Personal vault, found your Emergency Kit, or checked for a recovery code? 4. Are you part of a family or a team, so an organizer or administrator could recover your account? 5. Do you have a second email address for a new account? If the answer to 3 or 4 gives a way back in, use it and stop here. ## Steps 1. **Leave the app open.** Tell me not to sign out, quit, uninstall or reset. Explain that quick ways to open the app, like Touch ID or Apple Watch, will eventually expire, so we work in one sitting. 2. **Create a new account.** Ask me to go to start.1password.com/sign-up in a browser, with a different email address. Suggest a plan with a recovery path: individual and family accounts can use recovery codes, and team and business administrators can help recover an account (as of November 2026). I type every password myself, only into 1Password. 3. **Save the new Emergency Kit.** Ask me to download it and write the new account password on it. Suggest a printed copy kept somewhere safe, and one given to someone I trust. 4. **Add the new account to the same app.** Say: select your account at the top of the sidebar, then Manage Accounts, then Add an Account, and follow the onscreen instructions (1Password 8, as of November 2026). 5. **Show every vault.** Say: select your account at the top of the sidebar, then All Accounts. I should see vaults from both accounts. 6. **Confirm before copying.** Remind me that copying leaves the old vault whole, while a move copies and then deletes the original. We copy. Wait for my yes. 7. **Copy my items.** Say: right-click an item, select Duplicate, then choose a vault in the new account. Read the confirmation screen aloud, because it shows who can see the item. Repeat for every item I want to keep. 8. **Check every item.** Ask me to open each item in the new account and compare the count with the old vault. Name the small win when it matches. Remind me that this is the slow part and the safe part. 9. **Set up recovery on the new account.** Say: select your account at the top of the sidebar, then Manage Accounts, choose the new account, then Sign-in & Recovery, then Set up recovery code. I store the code somewhere safe and never paste it here. I wait at least one hour before I ever use it. If my plan has a family organizer or a second administrator, add one. 10. **Stop and ask before removing the old account.** The official page ends with removing the old account from the app. Tell me exactly what will happen: the old account and its local items go away from this app. Suggest waiting until I have used the new account for a while. Do nothing until I say yes. ## How to check it worked - I can open three or four items I use every week in the new account, and test one sign-in. - The Sign-in & Recovery screen lists a recovery code. - I can open the app with the new account's password. - Name the small win: the hard part is done and the vault is safe in a new home. Then tell me the evening is mine, and nudge me to spend it with someone I love. ## If something goes wrong - An item will not copy. Leave it in the old vault, keep going, and delete nothing to make room. - The old account asks for a password I do not have. The official page says I will need to start over and contact 1Password Support. A new account is still a fresh start. - The app locks before I finish. Stop. Do not guess at passwords, and do not follow steps from a forum. Use the official page below, and remember that 1Password Support is the only real authority on my account. - If you are stuck or unsure, stop. Do not retry the same step over and over. Use the company's official support page: https://support.1password.com/forgot-account-password/. ## Never do this - Never sign out of the old account until everything is checked. - Never export my data as a shortcut. The export file is not encrypted and the export asks for the account password. - Never paste a secret into this chat. - Never run a command you do not understand. Ask me to explain it first. - Never use an unofficial download, a cracked app, or a script from a forum. ## Sources 1. 1Password Support. "If you forgot your 1Password account password." https://support.1password.com/forgot-account-password/. Checked November 12, 2026. 2. 1Password Support. "Generate and use recovery codes." https://support.1password.com/recovery-codes/. Checked November 12, 2026. 3. 1Password Support. "Move or copy items." https://support.1password.com/move-copy-items/. Checked November 12, 2026. 4. 1Password Support. "How to add another 1Password account to the apps and browser extension." https://support.1password.com/add-account/. Checked November 12, 2026. 5. 1Password Support. "Get to know your Emergency Kit." https://support.1password.com/emergency-kit/. Checked November 12, 2026. 6. 1Password Support. "How to export your data from the 1Password apps." https://support.1password.com/export/. Checked November 12, 2026. ## About this file Made by technologytips.blog from the article https://technologytips.blog/articles/locked-out-of-1password-app-still-open/, checked against its sources on November 12, 2026. Written with AI, checked against the article and security-scanned. General help, not professional support. Menus, prices and rules change: check the official page before you rely on a step. Free to use and share with credit to technologytips.blog (CC BY 4.0). === FIX: check-video-audio-sync-automatically | https://technologytips.blog/articles/check-video-audio-sync-automatically/ | sha256 9448eee666487801b9b7c79e0ccce0b0c61868b672a4022ab8773293a6c0f321 === --- name: build-batch-video-sync-checker description: Build a command line tool that checks a whole folder of videos for audio and lip-sync problems and writes a report. Use it when someone has many recordings and cannot check each one by eye. license: CC BY 4.0. Free to use and share with credit to technologytips.blog. metadata: publisher: technologytips.blog article: https://technologytips.blog/articles/check-video-audio-sync-automatically/ article_title: "Out-of-sync audio in hundreds of videos? Build a checker" published: 2026-11-12 platforms: [mac, windows, linux] needs: [claude-code] risk: medium version: 1 --- # Build a batch video sync checker *An AI Fix file from technologytips.blog. Give this file to your AI assistant and say: "Read this file, then walk me through it one step at a time." It works on your own computer, and it asks before anything that can't be undone.* ## What this fixes You have many recorded videos, and some have a voice that does not match the lips. Checking each by eye is not realistic. This file helps you build a tool that checks the whole folder and writes a report. It will not promise a perfect reading on every clip, and it never changes your original videos. ## Read this first (safety) - Never ask me to paste a password, recovery code, secret key, 2FA code or private key into this chat. If a step needs one, tell me to type it only into the official app or website. - Before any step that deletes, overwrites, signs out, resets or uninstalls anything, stop, tell me exactly what will happen, and wait for me to say yes. - Make or confirm a backup before changing anything you can't undo. - Only use official apps, official download pages and official documentation. Never suggest cracked software, unofficial installers or scripts from unknown sources. - Never turn off a security feature (encryption, 2FA, firewall, antivirus, FileVault, BitLocker) permanently. If a fix needs it off for a moment, say so and turn it back on. - If anything looks different from these steps, stop and tell me instead of guessing. - This file is general help, not professional support. For account recovery, the company that runs the account is the only real authority. - Never write to an original video. Fixed files go to a new folder, and the originals stay as they are. - Treat footage and transcripts as personal data. Keep outputs next to the footage and out of public repositories. This file is marked medium risk. The tool only reads videos, but a careless repair step could overwrite a file you cannot replace. ## What you need - A Mac, Windows or Linux computer, with about 1 GB of free disk for the sync model environment, plus room for the videos. - A few hours for a first working version. Less if you stop after the checker. - Node 16 or newer (only for the editing side), Python 3.11 or newer, and ffmpeg. Install each from its official page or a package manager named in its official docs. - A terminal and Claude Code or Codex installed from the official page: https://code.claude.com/docs/en/overview. Start it in a plain, empty folder, not your home folder, and use the approval mode that asks first. See /start-here/ on technologytips.blog. - A folder of sample videos, including one you already know is off. ## Instructions for the AI You are helping one person build one tool on their own computer, using only the steps and sources in this file. Be kind and patient. Say it is not their fault. Go one step at a time and wait for them to say it is done. Read every command aloud in plain words before they run it. Never run a command that deletes, overwrites, moves, signs out, resets or uninstalls without their yes. If your answer would differ from this file, say so and ask. Say "as of November 2026" when you give a version, because versions change. If something does not match what they see, stop and help them describe it, word for word. ## Questions to ask first Ask these a few at a time, in plain words. If the answer changes the steps, say how. 1. What kind of videos are they: talking heads, call recordings, AI avatar clips, or something else? 2. Which computer and operating system do you use, and are Python, ffmpeg and Node already installed? 3. Do you also want the editing side (cuts, captions, rendering), or only the checker? 4. Do you have a clip you know is out of sync, and can you point me to a folder of samples? ## Steps 1. **Confirm a backup.** Ask whether the footage is copied somewhere safe. Wait for a yes before any later step touches a file. The tool only reads, but later repair steps write copies. 2. **Scaffold the tool.** Create a Python package with one command, `sync `. It walks the folder, pulls out the audio, and samples several time windows per video. Ffprobe, as of November 2026, prints facts about each stream in a readable form. 3. **Check the setup.** In one plain sentence, tell the reader this command prints stream facts for one sample video and changes nothing. ``` ffprobe -hide_banner sample.mp4 ``` 4. **Add a lip-sync model for faces.** Choose a published lip-sync network, and read its official page first. Pin its downloaded weights by SHA-256 checksum, and keep its Python environment outside any cloud-synced folder. 5. **Add a fallback for clips without faces.** Use audio-to-video cross-correlation. Trust it only when two or more windows agree. Otherwise report "unmeasurable". 6. **Write the verdicts.** Use pass, drift, step, review and unmeasurable. Save results as JSON lines, plus an HTML report and a CSV. 7. **Make it resumable.** Keep a per-file cache so a long run can stop and restart. 8. **Test with shifts you made.** Copy a good clip into a new folder. Delay the copy's audio by known amounts (asks before running, because it writes a new file). Confirm the checker reads the delays back within a few milliseconds. 9. **Run it on the real folder.** Run `sync` on the sample folder first. Read the report together. Wait for the reader to say what looks right before running on everything. 10. **Optional: build the editing side.** Describe each cut in one small file, in seconds, with frame math in whole frames. In Remotion, a video's first frame is 0 and its last is durationInFrames minus 1, as of November 2026. Add word timings with Whisper if they want cut-by-transcript. Gate every render with the sync checker, and do loudness after the render, not inside it. ## How to check it worked - A clip you delayed on purpose shows up as off, and the size matches what you set. - A clip you know is fine shows as pass. - Stop and rerun the tool, and confirm it skips files it already did. - Name the small win: the checker works. Then tell them the time they got back and nudge them to spend it on someone or something they love. ## If something goes wrong - A reading is "unmeasurable". That is honest. It usually means no face and no sharp sounds. Review that clip by ear. - Readings disagree between the two checks on a talking head. Trust the lip model for faces, and use the second check only for sharp events. - A gap grows over time. It may be drift. Check each person's own audio track, because tracks can have different offsets. - A voice sounds unclear after a fix. Check whether the edit used a poor call-audio copy or a track that picked up another voice, before blaming the tool. - If you are stuck or unsure, stop. Do not retry the same step over and over. Use the official docs for Remotion, ffprobe and Claude Code (see Sources). ## Never do this - Never overwrite an original video. - Never paste a secret into this chat. Read-only tokens go only into the tool's own settings. - Never run a command you do not understand. Ask me to explain it first. - Never use an unofficial download, a cracked app, or a script from a forum. ## Sources 1. Remotion. "The core idea." Official docs page, same as the article's source 1. Checked November 12, 2026. 2. Remotion. "Licensing." Official pricing page, same as the article's source 2. Checked November 12, 2026. 3. OpenAI (Whisper project). "openai/whisper." https://github.com/openai/whisper. Checked November 12, 2026. 4. FFmpeg. "ffprobe Documentation." Official documentation, same as the article's source 4. Checked November 12, 2026. 5. Anthropic. "Overview, Claude Code Docs." https://code.claude.com/docs/en/overview. Checked November 12, 2026. 6. Remotion. "Creating a new project." Official docs home, same as the article's source 6. Checked November 12, 2026. ## About this file Made by technologytips.blog from the article https://technologytips.blog/articles/check-video-audio-sync-automatically/, checked against its sources on November 12, 2026. Written with AI, checked against the article and security-scanned. General help, not professional support. Menus, prices and rules change: check the official page before you rely on a step. Free to use and share with credit to technologytips.blog (CC BY 4.0). === FIX: automatic-time-tracking-mac-for-client-billing | https://technologytips.blog/articles/automatic-time-tracking-mac-for-client-billing/ | sha256 ad979ad184b2bb794ef0d878c9b6558987ab67887ca40d43a45a1bfafa1025f6 === --- name: build-automatic-mac-time-tracker description: Build a local, single-user Mac app that logs your front app and window title, skips idle time and tags work to clients for billing. Use when someone forgets timers and wants private, automatic time tracking. license: CC BY 4.0. Free to use and share with credit to technologytips.blog. metadata: publisher: technologytips.blog article: https://technologytips.blog/articles/automatic-time-tracking-mac-for-client-billing/ article_title: "Stop guessing your billable hours: build automatic time tracking on your Mac" published: 2026-11-12 platforms: [mac] needs: [claude-code] risk: medium version: 1 --- # Build an automatic time tracker on your Mac *An AI Fix file from technologytips.blog. Give this file to your AI assistant and say: "Read this file, then walk me through it one step at a time." It works on your own computer, and it asks before anything that can't be undone.* ## What this fixes You forget to start and stop timers, so your billable hours are guesses. This file helps you build a small tracker that runs only on your own Mac, logs what you work on, tags it to the right client and feeds your invoices. It will not promise accurate results: matching work to clients needs checking before you bill, and this file will not help you watch anyone else's computer. ## Read this first (safety) - Never ask me to paste a password, recovery code, secret key, 2FA code or private key into this chat. If a step needs one, tell me to type it only into the official app or website. - Before any step that deletes, overwrites, signs out, resets or uninstalls anything, stop, tell me exactly what will happen, and wait for me to say yes. - Make or confirm a backup before changing anything you can't undo. - Only use official apps, official download pages and official documentation. Never suggest cracked software, unofficial installers or scripts from unknown sources. - Never turn off a security feature (encryption, 2FA, firewall, antivirus, FileVault, BitLocker) permanently. If a fix needs it off for a moment, say so and turn it back on. - If anything looks different from these steps, stop and tell me instead of guessing. - This file is general help, not professional support. For account recovery, the company that runs the account is the only real authority. - Window titles and browser history can show private things such as email subjects and bank pages. Do not enable screenshots. Do not send titles or URLs to an AI model unless I agree and they are stripped or hashed first. - Bind the tracker's web page to localhost only. Never expose it to a network. This file is marked medium risk. It changes settings and reads private activity, but you can undo every step. ## What you need - A Mac that you own, and a user account you are logged in to. - Node.js installed from the official site, and a terminal. - Claude Code or Codex installed from the vendor's official page. See https://technologytips.blog/start-here/ for how. Start it in a plain, empty folder, not your home folder, and choose the approval mode that asks before it runs anything. - Time to go slowly. Nothing here needs to be fast. ## Instructions for the AI You are helping one person build one tool on their own computer, using only the steps and sources in this file. Be kind and patient. Say it is not their fault. Go one step at a time and wait for them to say it is done. Read every command aloud in plain words before they run it. Never run a command that deletes, overwrites, moves, signs out, resets or uninstalls without their yes. If your answer would differ from this file, say so and ask. Say "as of November 2026" when you give a menu path, because menus change. If something does not match what they see, stop and help them describe it, word for word. Never ask for a password or key. Treat every build phase below as a design we built and ran, not a promise of results. ## Questions to ask first Ask these a few at a time, in plain words. If the answer changes the steps, say how. 1. Which Mac and which macOS version do you use? 2. Which apps and browsers do you work in, and which clients do you bill? 3. Do you bill by project or by the hour, and do you already have rates? 4. Do you want calendar sync, and are you comfortable with an AI model suggesting rules? If so, we will strip titles and URLs before anything is sent. ## Steps 1. **Check the prerequisites.** Confirm Node.js runs. Tell the reader that macOS will ask them to approve the program that runs AppleScript. As of November 2026, they approve it under System Settings, Privacy & Security, in the Accessibility and Automation lists [1][2]. They should grant access only to apps they know and trust [2]. 2. **Create the database.** Use SQLite through the better-sqlite3 library, in one local file outside the project folder. Tables: clients, projects, tags, tag rules, activities, time entries, invoices, settings. Turn on WAL mode with the library's pragma, as its own page recommends [6]. WAL needs all programs on the same computer, so keep the file on the local disk [4]. 3. **Build the tracker.** Every 30 seconds, ask AppleScript for the front app and window title [3]. Read the seconds since the last keyboard or mouse input from the system. Treat 2 minutes without input as idle. Write one row per unbroken stretch in the same window. 4. **Add safety limits.** Cap any one row at 2 hours. Ignore anything under 5 seconds. After a restart, restore saved state only if it is under about 10 minutes old. 5. **Add the rules engine.** A rule matches an app, domain, URL fragment, window title or browser profile, and assigns a tag, client and project. Run the highest priority first. 6. **Back up before you add more.** Confirm the reader has a copy of the database file in a place they control, and that the copy opens. Wait for a yes before continuing. 7. **Sync browser history, calendar and invoicing.** Read copies of the browser history files every 5 minutes, never the live files. Sync the calendar every 15 minutes, and log automatically only for matches of 0.9 or higher; leave the rest as suggestions. Set rates by override, then project, then client. 8. **Run it at login.** Create a launchd user agent, which runs only while the reader is logged in [5]. Say what the file contains before the AI writes it. Loading the agent starts a background program, so the AI asks first (asks before running). 9. **Add a catch-up check at login.** A Mac that was off overnight does not run missed jobs, so rebuild the day's totals when the reader logs in. ## How to check it worked - Open the tracker's local page and see rows for the last few minutes, with the right app and window title. - Walk away for 3 minutes and confirm the row ends and idle time is not billed. - Restart the Mac and confirm no multi-hour row appears. - Name the small win: the tracker is logging on its own. Then tell the reader the time they got back, the Friday evening they no longer spend rebuilding the week, and nudge them to spend it with someone they love. ## If something goes wrong - Window titles come back blank: the permission is probably off. Open Privacy & Security and check the Accessibility and Automation lists [1][2]. - A huge row appears: the 2 hour cap or the stale-state rule is missing. Ask to see that code. - A job did not run overnight: the Mac was probably off. Use the catch-up check from step 9. - If you are stuck or unsure, stop. Do not retry the same step over and over. Use Apple's support pages: https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/mac ## Never do this - Never enable screenshots, and never send raw window titles or URLs to an AI model. - Never expose the tracker to a network, because it has no login on purpose. - Never use it to watch anyone else's computer. - Never paste a secret into this chat. - Never run a command you do not understand. Ask me to explain it first. - Never use an unofficial download, a cracked app, or a script from a forum. ## Sources 1. Apple Support. "Change Privacy & Security settings on Mac." https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/mac. Checked November 12, 2026. 2. Apple Support. "Allow accessibility apps to access your Mac." https://support.apple.com/guide/mac-help/allow-accessibility-apps-to-access-your-mac-mh43185/mac. Checked November 12, 2026. 3. Apple Developer Documentation Archive. "Introduction to AppleScript Language Guide." https://developer.apple.com/library/archive/documentation/AppleScript/Conceptual/AppleScriptLangGuide/introduction/ASLR_intro.html. Checked November 12, 2026. 4. SQLite. "Write-Ahead Logging." The page "wal" on the official SQLite documentation site (the link is in the article's Sources). Checked November 12, 2026. 5. Apple Developer Documentation Archive. "Creating Launch Daemons and Agents." https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html. Checked November 12, 2026. 6. better-sqlite3 project (GitHub). "better-sqlite3." https://github.com/WiseLibs/better-sqlite3. Checked November 12, 2026. 7. Apple Support. "Protect data on your Mac with FileVault." https://support.apple.com/guide/mac-help/protect-data-on-your-mac-with-filevault-mh11785/mac. Checked November 12, 2026. ## About this file Made by technologytips.blog from the article https://technologytips.blog/articles/automatic-time-tracking-mac-for-client-billing/, checked against its sources on November 12, 2026. Written with AI, checked against the article and security-scanned. General help, not professional support. Menus, prices and rules change: check the official page before you rely on a step. Free to use and share with credit to technologytips.blog (CC BY 4.0). === FIX: ai-coding-agent-team-build-deploy-fix | https://technologytips.blog/articles/ai-coding-agent-team-build-deploy-fix/ | sha256 370642eda7e0fa31f79c1abf524662ca2d30cd1c98b00771d3f7df9aa38213c3 === --- name: build-a-team-of-claude-code-agents description: Build a small team of Claude Code subagents (planner, finisher, deployer, sweeper) with a shared to-do board, narrow tools and a human gate. Use when a reader wants agents that build, deploy and check projects without chaos. license: CC BY 4.0. Free to use and share with credit to technologytips.blog. metadata: publisher: technologytips.blog article: https://technologytips.blog/articles/ai-coding-agent-team-build-deploy-fix/ article_title: "Run a team of AI coding agents without chaos: our Claude Code playbook" published: 2026-11-12 platforms: [mac, linux, windows] needs: [claude-code] risk: high version: 1 --- # Build a team of Claude Code agents *An AI Fix file from technologytips.blog. Give this file to your AI assistant and say: "Read this file, then walk me through it one step at a time." It works on your own computer, and it asks before anything that can't be undone.* ## What this fixes You have projects that get written but never reach a live address, or that break without anyone noticing. This file helps you build a small team of Claude Code subagents with clear jobs, a shared to-do board and hard limits. It will not promise a result, and it will not give any agent your payment or customer-messaging tools. ## Read this first (safety) - Never ask me to paste a password, recovery code, secret key, 2FA code or private key into this chat. If a step needs one, tell me to type it only into the official app or website. - Before any step that deletes, overwrites, signs out, resets or uninstalls anything, stop, tell me exactly what will happen, and wait for me to say yes. - Make or confirm a backup before changing anything you can't undo. - Only use official apps, official download pages and official documentation. Never suggest cracked software, unofficial installers or scripts from unknown sources. - Never turn off a security feature (encryption, 2FA, firewall, antivirus, FileVault, BitLocker) permanently. If a fix needs it off for a moment, say so and turn it back on. - If anything looks different from these steps, stop and tell me instead of guessing. - This file is general help, not professional support. For account recovery, the company that runs the account is the only real authority. - Agents act with my accounts. Give each agent the fewest tools it needs. Keep deploys, money and customer messages behind my approval. - Use names of environment variables only. Never write a secret value into a file, a log or this chat. This file is marked risk high because agents that can push code and deploy can change things that are live. The steps keep a person in charge of the first live release. ## What you need - A computer with a terminal, and a project folder with your code in it. - A GitHub account and the gh command-line tool, signed in with `gh auth login` (as of November 2026). - A small database, such as a hosted free tier, and a place to host finished work. - About an afternoon for a first pass. - Claude Code installed from the official Claude Code docs: https://code.claude.com/docs/en/sub-agents (see the site's /start-here/ page for the install steps). Start it in a plain, empty folder, not your home folder, and use the approval mode that asks before it runs anything. ## Instructions for the AI You are helping one person build a small agent team on their own computer, using only the steps and sources in this file. Be kind and patient. Say it is not their fault. Go one step at a time and wait for them to say it is done. Read every command aloud in plain words before they run it. Never run a command that deletes, overwrites, moves, signs out, resets or uninstalls without their yes. If your answer would differ from this file, say so and ask. Say "as of November 2026" when you give a menu path or setting, because they change. If something does not match what they see, stop and help them describe it, word for word. ## Questions to ask first Ask these a few at a time, in plain words. If the answer changes the steps, say how. 1. Which projects do you want the team to handle, and where does each one go live? 2. Is each project already in a git repository, and is it pushed to GitHub? 3. Do you have a small database you can use for a to-do board? 4. What has gone wrong before: stuck deploys, unpushed work, jobs that fail without a sound? ## Steps 1. **Make a safe place first.** Ask me to commit everything in the project. Confirm it is committed before going on. This is the backup step for everything below. 2. **Push to a private repository.** Create a private repository from the local folder with gh. This copies my code to GitHub (asks before running). ``` gh repo create my-project --private --source=. --push ``` 3. **Build the board.** Help me make three things in my small database: a builds table (a key, a stage, an owner agent, a next action, a blocked reason, a repo address, a live address and a health result), an event log, and a queue view sorted by priority with blocked rows last. Show me the plan before you create anything. 4. **Write one agent file per role.** Roles: a planner, a finisher, a deployer and a sweeper. Save each in `.claude/agents/` as a markdown file with YAML frontmatter (as of November 2026). Give each a one-sentence job, an input rule (it receives exactly one build key), a numbered procedure and a short "hard rules" list. Show me each file before saving it. 5. **Set tools per agent.** In each file's frontmatter, list only the tools that agent needs. The planner gets read and write on the database only. The deployer gets a shell and git. Nobody gets payment or customer-messaging tools. Before removing a tool, ask me what the agent relied on. 6. **Limit work in progress to one.** Tell the planner not to dispatch a new build while one is mid-flight. 7. **Split "deployed" from "verified".** The deployer may set a build to live after a health address answers with a success code. Only a different agent, or I, may set it to shipped. 8. **Write the sweeper's runbook.** Save it as a separate markdown file the sweeper reads first. List each check with its exact command. Give each finding a fingerprint, so a rerun updates a ticket instead of copying it. 9. **Add the git rules.** The sweeper may push only non-default or local-only branches, as fast-forwards. A default branch in a repo with automated checks is a deploy, so I decide. Diverged repos and missing remotes are mine to decide. Never force-push, merge or delete a branch. 10. **Share the settings.** Help me put permission rules (allow, ask, deny) and any hooks in `.claude/settings.json` and commit it (as of November 2026). A hook that refuses to end a session with unpushed commits is a good first one. 11. **Schedule the sweeper.** Set it to run twice a day with a hard time cap on each run. Use cron, or the scheduler on my system. Ask before you create the schedule (asks before running). 12. **Approve the first live release.** Stop. Tell me what the deployer will publish, and wait for my yes before the first production release. Do this by hand, once. ## How to check it worked - Each agent file exists in `.claude/agents/`, and each lists only the tools it needs. - The queue view shows one build in flight at most, with blocked rows last. - The sweeper has run once, and its output file is fresh and has a date from today. - A test build reaches "live" only after a success response from its health address, and stays out of "shipped" until I mark it. - Name the small win: you now have a team with clear jobs. Then tell me the time I got back, and nudge me to spend it on someone or something I love. ## If something goes wrong - A sweeper run did not start. Check how fresh its output is, not the exit code. A job set for a time the computer was off may never have run. Ask me before changing the schedule. - A run ended at a login wall. Stop, tell me, and ask me to sign in to the official app myself. Never ask me for the login. - An agent is missing a tool it needs. Stop and tell me which tool and why. Put back only that tool. - A tunnel or service looks fixed after one good check. Run a second check after a delay before closing the ticket. - If you are stuck or unsure, stop. Do not retry the same step over and over. Use the official docs: https://code.claude.com/docs/en/sub-agents. ## Never do this - Never let an agent deploy, spend money or message customers without my approval. - Never leave an agent without a tools line. It may inherit every connected tool. - Never push a personal or financial repository. - Never paste a secret into this chat. - Never run a command you do not understand. Ask me to explain it first. - Never use an unofficial download, a cracked app, or a script from a forum. ## Sources 1. Anthropic (Claude Code Docs). "Create custom subagents." https://code.claude.com/docs/en/sub-agents. Checked November 12, 2026. 2. Anthropic (Claude Code Docs). "Hooks reference." https://code.claude.com/docs/en/hooks. Checked November 12, 2026. 3. Anthropic (Claude Code Docs). "Settings files and precedence." https://code.claude.com/docs/en/settings. Checked November 12, 2026. 4. GitHub CLI. "Manual." https://cli.github.com/manual/. Checked November 12, 2026. 5. GitHub CLI. "gh repo create." https://cli.github.com/manual/gh_repo_create. Checked November 12, 2026. ## About this file Made by technologytips.blog from the article https://technologytips.blog/articles/ai-coding-agent-team-build-deploy-fix/, checked against its sources on November 12, 2026. Written with AI, checked against the article and security-scanned. General help, not professional support. Menus, prices and rules change: check the official page before you rely on a step. Free to use and share with credit to technologytips.blog (CC BY 4.0).