← All topics

workflow

2 captures, most recent first.

rohan anil @_arohan_

I had one of the best coding sessions last night with claude code. I was trying to do something bit complicated, I started out writing md files with full descriptions of all the gotcha, and how to run, how to debug if you got stuck – this took some effort then I watched Claude nail what otherwise would have taken both expertise & time in just a few hrs. 9:43 AM · Sep 9, 2025 · 1,807 Views
Note from Claude Sonnet 5

A positive testimonial for Claude Code, describing how thorough upfront documentation (md files with gotchas and debug steps) led to strong autonomous performance on a complex coding task. Practical/anecdotal evidence about Claude Code workflow effectiveness.

claude codecoding agentstwitterworkflowai coding assistants

Jacques @JacquesThibs

[Top, cut off tweet]: "...to use my local environment." 7:16 PM · Jul 18, 2025 · 240 Views 💬 2 🔁 ❤ 🔖 ↗ Jacques @JacquesThibs · 1h Running Multiple Claude Code Accounts Add these lines to your ~/.zshrc or ~/.bashrc file to create shortcuts for different accounts. The magic is the CLAUDE_CONFIG_DIR environment variable. It tells Claude where to store its config, keeping accounts completely separate: alias cwork='CLAUDE_CONFIG_DIR=$HOME/.claude-batman claude' alias cpers='CLAUDE_CONFIG_DIR=$HOME/.claude-bwayne claude' Make the config directories with mkdir -p ~/.claude-batman ~/.claude-bwayne, then reload your shell with source ~/.zshrc. Now you can open two terminals and run cwork shell in one and cpers shell in the other. Happy clauding :) 💬 1 🔁 ❤ 1 📊 126 ↗ Jacques @JacquesThibs · 1h Now I need more monitors
Note from Claude Sonnet 5

A practical tip tweet from Jacques Thibodeau (AI safety researcher) on running multiple Claude Code accounts via CLAUDE_CONFIG_DIR shell aliases. Technical/workflow content Nathan was reading, likely relevant to his own Claude Code setup practices.

twitterclaude-codetoolingshellworkflowjacques-thibodeau