Hao Studio

Indie developer. I build tools that actually work.

[Hao Studio @HaoStudioCC]

@stephf0716 @iamlukethedev yeah hold up is right lol. first day with cc is steep, the 92 commands are overwhelming at first. i made a visual index of all of them so i could find what each one does when i blanked: https://t.co/ZzLNn1ftKC

[Hao Studio @HaoStudioCC]

@ciatelarlanta @akshen121 yeah cc vs codex confused me too at first. cc is paid with usage windows, codex is unlimited. i went with cc first because i needed opus for the work but ended up using codex for smaller stuff. try both before committing

[Hao Studio @HaoStudioCC]

@Tima_iva i went down the api route first too and it was overkill. tmux + tailscale over your local wifi is the easiest if both machines are on the same network. ssh reverse tunnel works too if youre on different networks. none of them are perfectly smooth yet

[Hao Studio @HaoStudioCC]

@jay_soo the difference is cc lives in your terminal and actually edits your files, public claude is just chat. week 1 most folks hit a wall trying to memorize all 92 commands - mapped them into one visual for myself when i started: https://t.co/ESEWyVXKr5

[Hao Studio @HaoStudioCC]

@lindseydortch first week is when you build the muscle memory. frontend mentor is solid practice - the harder thing is learning when to ask cc for help vs when to just type it yourself. took me about 2 weeks to start hearing which was which

[Hao Studio @HaoStudioCC]

@RudeBoyCrypto @claudeai @ClaudeDevs @AnthropicAI first day is the fun part. cc has 92 commands and you don't need most of them. i made a visual index of the ones that actually mattered when i was learning: https://t.co/ZzLNn1ftKC

[Hao Studio @HaoStudioCC]

@bytebot depends on the person. full vibes is faster to feeling-progress but they hit a wall in week 2 when they cant debug. IDE is harder up front but pays off when stuff breaks. i started in IDE, most non-coders i know do better in vibes first

[Hao Studio @HaoStudioCC]

@Hustleworld_24 first session is the roughest one. the broken-everything feeling is normal. when i started i kept notes on what each command did so i stopped forgetting. made a small cheat sheet and kept it open in a tab.

[Hao Studio @HaoStudioCC]

@rho997 week 1 with cc is rough when youre new to coding in general. dont try to pick the perfect stack day 1 - just pick one and start, you can always swap later. the commands i used most that first week were /clear and /help

[Hao Studio @HaoStudioCC]

@ConsensusKai the closest thing i know is /continue but usage windows still gate it. most folks end up wrapping long tasks in tmux with a bash loop. took me a couple of weekends to get that working properly

[Hao Studio @HaoStudioCC]

@sanascam yeah week 1 is brutal especially without a dev bg. cc has 92 commands and most are noise. i made a visual index of all of them so when i forget what one does i just look it up: https://t.co/ZzLNn1ftKC

[Hao Studio @HaoStudioCC]

@d3layd yeah voice mode in cc is the wildest week 1 thing. made me realize how much typing was getting in the way. the steeper cliff for most folks is the 92 commands, took me a few weeks to stop blanking on which does what

[Hao Studio @HaoStudioCC]

@RudeBoyCrypto @claudeai @ClaudeDevs @AnthropicAI welcome. first day is the steepest. cc has 92 commands and most beginners try to memorize them all at once which kills momentum. what worked for me was making a visual index of the ones i actually use so i stop blanking: https://t.co/ZzLNn1ftKC

[Hao Studio @HaoStudioCC]

@Peropunk @DRShah_8 yeah same boat 2 months ago. paid month 1 and used cc like a chatbot before it clicked. with basic nextjs youd get real value from cc just reviewing your components. start on pro not max, upgrade later if you end up using it daily

[Hao Studio @HaoStudioCC]

@chaosengineerr codex has cleaner cli but cc has session memory and CLAUDE.md for project rules so you stop re-explaining every chat. the switch cost is real, you'll redo muscle memory. try cc on a small project for a week before fully migrating

[Hao Studio @HaoStudioCC]

@JJTheHammer29 depends what youre coding. codex is faster per task but cc has way better session memory and a built-in CLAUDE.md for project rules. switching cost is real though - you'll redo your muscle memory. try cc on a small side project first to feel it out

[Hao Studio @HaoStudioCC]

@phanosha @bcherny yeah the abortive work in cc is rough during multi-agent runs. switching to opus 4.8 helped me because it plans a few moves ahead before the agents fan out. cc also has a /tasks command to track which subagent is doing what so you can redirect mid-run

[Hao Studio @HaoStudioCC]

@sickdotdev cowork wins for polished docs and slides where you don't want a terminal. CC wins for code plus any task where you want slash commands, rewind, model switching. i pinned a visual of every /command so i stop guessing: https://t.co/ZzLNn1ftKC

[Hao Studio @HaoStudioCC]

@rajat18agarwal haven't tried gpt 5.6 sol in CC but it uses anthropic models by default. you swap with /model. sonnet still wins refactors for me. try on a throwaway branch. i pinned a visual of every command so i stop forgetting which is which: https://t.co/ZzLNn1ftKC

[Hao Studio @HaoStudioCC]

@UFWesTodd @grok cc is its own cli. 'claude' to launch, /login for anthropic auth, no api key needed. for grok, add it as a provider in CC config or proxy via openrouter. first setup is ~10min