Register and share your invite link to earn from video plays and referrals.

Trace Cohen
@Trace_Cohen
@cosign | early AI & deep tech | US + Israel | angel in 75+ | Ex-founder, ex-Amex fintech | Columbia MBA | 10M+ monthly Data/SEO views at ValueAddVC dot com
Joined February 2008
11.5K Following    25.9K Followers
Fun AI hack I’ve been testing: I had ~30B tokens on Muse and wanted Claude to use it as a research engine. No native connection between them, so initially I used Google Drive as the bridge. Claude → writes task to shared Drive folder → Muse researches it → writes Google Doc/Sheet back → Claude reads it. It worked, but there was a problem: Claude had to ingest the entire Google Doc through the Drive connector every time. I was saving tokens on research and then burning a ton of tokens just moving the research back into Claude. So we changed the architecture. Now a normal script runs hourly and uses the Google Drive API to pull new Muse docs directly. It reads the title/metadata, routes the output to the right workflow, pulls the cited sources directly, verifies them, and moves the doc to Processed. Claude only gets the small amount of information that actually requires reasoning or approval. Muse = research Google Drive = shared message queue Python/API = transport + routing + verification Claude = reasoning/judgment AI talks to AI without making an AI do the plumbing. Still testing it, but so far this feels like a much better way to connect different AI systems that don’t natively talk to each other.
Show more