This New Open Source Tool Just Fixed Your Claude Code Workflow

Claude Code workflow is stuck: every session lives in one folder with one agent. This Claude Code tutorial covers Agit, the Claude Code setup, the Claude Code tips we use daily, and how Claude Code agents hand sessions to each other. Try Runable at https://runable.com/?utm_source=ytlong&utm_medium=AILABS-393 and turn your next idea into a real, live product from a single prompt. Agit on GitHub: https://github.com/Einsia/agent-git Community with All Resources: https://ailabspro.io/?v=CHHEjuNBxoQ The Roundup, our daily newsletter covering the AI stories that matter. Join now: https://www.theroundup.so/ What we cover - The gap in every Claude Code workflow: your conversation is stuck to one agent in one folder, so sharing it means writing it out by hand - What Agit is, and how it points the Git model at your conversations instead of your code - Git from scratch for anyone who has never used it: commits, branches, push, reviewing changes - Why this matters if you are vibe coding with Claude and have never touched version control Storing and sharing sessions - Multiple conversations on one project, each on its own branch, so they stay separate - Commits save your prompts and the agent's response, and going back changes what the agent sees, not your app - 1 GB storage on private repos, no limit on public ones, and why public is one way - Profiles, collaborators and pull requests, plus read-only links with an open limit - Cherry-pick a message and its response into your current session, so context moves between conversations instead of being rewritten A Claude Code agents workflow across two tools - Forking a session into Codex, the coding agent from the makers of ChatGPT, with no handoff document - What carries over, messages and tool records, and what does not, the model's thinking - The dynamic workflow Claude Code does not give you on its own: picking up the same conversation in a different agentic AI tool - Why we need this daily working in both Codex and Claude Code Install and setup - Both install commands, which one we used, and why the other failed for us - Account, browser login, init, repo name and auto push - agents.md or claude.md, and why we added both - Where Agit stores everything, in the .agit folder in your home folder - The full vibe coding setup for the demo, built on the web app template from our community Keys and passwords - Agit replaces recognised keys with placeholders when saving and checks again before pushing - The gap: a password made of ordinary words has no pattern, so it can slip through - The skill we built to register passwords first, and why it has to be added at the start Vibe coding with Claude - New to vibe coding? Vibe coding is building software by describing what you want to an agent instead of writing code, and this is the session layer most vibe coding tools leave out - Claude Code tips for anyone running more than one conversation on the same project - These workflows apply in Claude AI, Claude Code, Codex or any AI coding tool that reads a project instructions file - The skill, the starter pack and the rest of our resources are in AI Labs Pro 00:00 Intro 00:56 Git basics 02:06 How Agit works 04:02 Sponsor 04:58 Install & setup 06:02 Creating a repo 07:34 Rewind & revert 08:54 Cherry-pick 09:44 Fork to another agent 10:39 Handling secrets Hashtags: #ai #claude #ClaudeCode #vibecoding #agenticai #git #ClaudeAI #aicoding #claudecodeworkflow #claudecodetips #Codex #ChatGPT