Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More

Owned by Tam

Cộng đồng học cùng tamhn 😇

2 contributions to GoHighLevel w/ Robb Bailey
How I stopped repeating context into AI chats with company brain atlas
I used to waste 20+ mins before every single AI chat copying and pasting context about my business. I pasted my target audience, my voice rules, my offer details, and my past client results over and over again If I opened a new chat on my laptop, the AI forgot everything I taught it the day before. My outputs kept coming back generic, and my chat sidebar looked like a graveyard of 50 disorganized tabs I fixed this when I stopped treating AI as a chat box and turned my local directory into a company brain atlas: - Build a 4-folder local atlas: On my computer, I set up a dedicated folder with 4 simple markdown files: identity notes, daily project logs, reusable skills, and my offer teardowns. My business context lives permanently on my disk in obsidian. It never gets trapped inside a web browser - Connect MCP server: Inside claude settings, I plugged in lots of useful connectors i use daily, like Composio, Exa, and the blotato MCP connector (for content publishing) using my API key - Enforce the 80/20 leverage split: I spend my 20% high-focus energy speaking my raw field notes into my microphone. Claude and blotato handle the other 80% of the busywork: pulling the background context from my atlas folder, building a 6-slide carousel, and queuing the drafts I still spend 2 minutes reviewing the final slides to catch weird AI typos before hitting publish. Zero context re-pasting, zero generic chats, and zero wasted setup time. When you use AI for your business, do you still paste your background into every new chat, or does the model read from your local files?
How I split my daily building between chatgpt codex and claude code
I spent 10 days trying to force my entire development workflow into a single AI tool. I wanted one environment for everything: writing code, running automations, and publishing content. That was a mistake. I ran a test filtering 300 engineering profiles on linkedin. chatgpt codex pulled the first batch, hit an ethical safety refusal, and locked up completely I moved the exact same task to claude code with its browser extension, and it ran for 4 hours without a single warning The next day, the tables turned. I had to publish a 1000-word newsletter to substack, which has no public API. claude code struggled with the visual editor. chatgpt codex opened its in-app browser, logged into my account, placed the images, styled the headers, updated the SEO metadata, and added my footer template in 3 minutes. I stopped looking for a single winner and split my work across 2 lanes: - chatgpt codex for desktop apps and visual web tasks: It handles platforms without public APIs, lets me click visual diffs before saving to github, and controls my local mac tools - claude code for deep terminal automation: It runs long bash scripts, extracts data from restricted endpoints, and handles multi-file refactors without tripping safety filters I use codex when I need eyes on a browser screen, and claude when I need horsepower in the command line. When you automate daily tasks, do you force everything into 1 ecosystem, or do you run 2 models side by side?
1-2 of 2
Tam Hn
2
15 points to level up
@tam-hn-5811
itstamhn.com

Active 1d ago
Joined Oct 9, 2026
INTJ
Vietnam
Powered by