{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/5b426c56d97a4cb298d261fe69e1c120\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/5b426c56d97a4cb298d261fe69e1c120-9f2f0c3deabbd145.gif","duration":662.002,"title":"Using Claude Code, Codex, and HQ Commands","description":"This Loom explains how to use Cloud Code or Codex with the HQ workspace to work on LandersRx tasks efficiently. It emphasizes staying in the HQ folder, completing HQ onboarding, running HQ Sync each morning, and keeping HQ updated, with async syncing enabled and HQ turned off by shutting down the laptop at day end. It recommends starting a new session for each task to avoid running out of usage, archiving old sessions, and using lighter models like Opus 5 rather than the most expensive options. It also highlights key commands start work and handoff, where handoff saves the thread context to HQ and provides a resume thread ID, and it suggests using handoff instead of remembering other commands."}