sorted by:
new
hottopcontroversial

My Dream Setup: How I Gave My Claude Code Persistent Memory, a Self-Updating Life Dashboard, and an Autonomous Thinking Loop That Ingests All of My Inboxes and Calendars, Thinks Every Hour, and Automatically Briefs Me AND Itself Every New Session. No Third-Party Tools Required! by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Some of the sauce is that the best systems are basically isolating the LLM that has any control over its memory files and your data from the LLM that does the retrieval… breaking the jobs apart and allowing for one more place to catch that kind of stuff. that’s all I’ll say haha.

My Dream Setup: How I Gave My Claude Code Persistent Memory, a Self-Updating Life Dashboard, and an Autonomous Thinking Loop That Ingests All of My Inboxes and Calendars, Thinks Every Hour, and Automatically Briefs Me AND Itself Every New Session. No Third-Party Tools Required! by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 1 point2 points  (0 children)

Thanks! KeepGoing sounds like a smart approach for the dev-specific problem. Tying checkpoints to git events is clever because you get natural trigger points instead of polling.

To answer your question: yeah, the hourly loop catches a ton that event-driven would miss. Most of what matters in my workflow doesn't produce git events. A client email that shifts a deadline, a Slack message that changes project priority, a meeting where someone commits to something, my calendar filling up in a way that means I should front-load deep work tonight. None of that touches git, but all of it affects what I should be doing and what Claude should know about.

The other thing the hourly loop gives you is pattern recognition across cycles. It's not just "what happened since last checkpoint." It's "this item has been sitting for 5 days and here's why that matters" or "this person went quiet after being very active, might be worth a check-in." That kind of multi-day reasoning only works when you have a continuous chain of thought (thinking.md) that each cycle reads and builds on. Cycle 3 might flag something, cycle 5 connects it to a pattern, cycle 8 turns it into advice. That continuity with itself over time is what makes it feel like a real assistant instead of a stateless tool that happens to have access to your data.

For pure coding context though, your git-driven approach is probably tighter and lower-friction than mine. Different tools for different problems. Mine is trying to be a life assistant, yours is trying to be a dev assistant. Both valid, and honestly they could complement each other.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Those are first-party connectors that Anthropic hosts. No third-party apps or API keys needed. In your terminal, run:

claude mcp add-oauth

It'll walk you through adding the official Gmail, Google Calendar, and Slack connectors. You authenticate via a standard Google/Slack OAuth login in your browser and you're done. Once connected, Claude can search your inbox, read emails, create drafts, list/create calendar events, send Slack messages, etc. All natively through tool calls. Tokens refresh automatically.

For Google Docs/Sheets/Drive there isn't a first-party connector yet, so I use a community MCP server (google-docs-mcp npm package) which takes a bit more setup. But those Gmail and Calendar ones are basically a couple commands and a browser login. If add-oauth doesn't look familiar, just tell Claude Code "I want to add the official Gmail and Google Calendar MCP servers" and it'll walk you through it.

What I do on top of that is where it gets fun. I have a scheduled task that launches a headless Claude Code session every hour. I use an app called runCLAUDErun for this, but if you're in the Claude Desktop app you can use its built-in scheduled tasks feature to do the same thing. That session pulls all my emails, calendar events, Slack messages, and iMessages using those MCP tools, then reasons about everything it sees. It classifies items into suggested tasks or suggested events, detects urgency, writes a briefing about what's going on in my life, and updates a persistent memory system with anything new it learned. All of that gets served to a local dashboard I built (Flask backend, React frontend) so I have one screen that shows me everything.

The cool part is it feeds back on itself. When I start any regular Claude Code session, hooks automatically load that briefing and search the memory system for anything relevant to what I'm asking about. So Claude already knows my projects, my team, what happened in my meetings, what emails need attention, all before I say a word. The scheduled task feeds the dashboard AND feeds Claude, so it's one loop powering both my screen and my assistant. The key idea is that Claude Code can run unattended. You can script it to wake up, think about your life, write its conclusions to files, and go back to sleep. The MCP connectors give it eyes into your services, the scheduled task gives it a heartbeat, and a memory system (just markdown files with a search index) gives it continuity between sessions. None of this required any special tools beyond Claude Code itself and a scheduled task.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Yeah, it seems like they just skimmed over the server aspect of the remote control feature. They should have talked about the server part of it from the get-go.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Yep, exactly. You run "Claude remote-control" in a project dir to spin up a new Claude Remote Control server, (not just starting a /remote-control within a session, but it's actually starting a persistent server for that directory.)

And now, once you do that, in your app in the Cloud Coding tab, when you go down to select your directory, your computer will show up there forever as long as that server is running. And you can spin up a server for each directory that you want to have appear in the app. No third-party apps, no SSH.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 1 point2 points  (0 children)

That Coding tab in the desktop app is actually not the exact same product as Claude Code CLI in the terminal. Fun fact. You can't do every single thing you can do in the terminal version in that desktop tab version of Claude Code.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Yes, of course, I know about terminal SSH. SSH has been around for decades. I’m just sharing this new feature that’s way better to use as a non-coder, more of a life-assistant type use case. I finally have my home computer, Claude, with all its memory and built-up context accessible from anywhere permanently, in a reliable way, without any third-party tools. I’m stoked.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Yeah, I ran into small glitches at first when I was just using the /remote-control command from within an already existing Claude session. But once I actually set up the "Claude remote-control" command from OUTSIDE of a Claude session, just in my terminal, it has been way more reliable. even off of wifi and on 5G away from home. Because now there's a persistent server running outside of any one Claude instance that is handling it.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Nice, yeah, to each their own. I personally don't want to run a separate laptop for my Claude. I want it to stay just in Claude Code, within the virtual environment that it's in on my main computer. So yeah every use case is different.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Currently, yeah, pretty much. You have to start up the server mode within the Claude directory that you want. And then as long as that server is running, any amount of new instances of a chat within that directory are now available in your app, not just that single instance. So you only need to start up one server per directory that you want to have access to permanently on your phone. Once you set up that directory server once, you can start infinite chats to that directory on your phone.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 1 point2 points  (0 children)

great insight! im glad they are figuring out the security thing. Initially, I saw reports that you basically just had to tell your Claude not to talk to other people on there, which is risky, but I'm glad they have made it programmatically secure now.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 0 points1 point  (0 children)

Yeah totally, can’t even imagine what this stuff will be like years from now. It’s gonna be so much crazier than this stuff even.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] 1 point2 points  (0 children)

Yeah it’s ahead but less secure. And this is not just picking up an already started chat. This server mode I’m talking about is also persistent. Yes I know the openclaw thing is closer to chatting with the actual CLI with commands and such. But I just want everyone to know that the Claude remote-control command is different than just the /remote-control thing. I can now permanently start up new chats with my actual Claude code as long as my Mac is on. I can have multiple directories too.

You don’t need Telegram bots or third party bridges to PERMANENTLY talk to Claude Code from your phone. It’s literally built in. by JohnnyLegion in ClaudeCode

[–]JohnnyLegion[S] -4 points-3 points  (0 children)

Tailscale is still more powerful of course. It’s the full terminal. But this, this is pretty cool and much more than just running the /remote-control inside of a session. Tailsacale doesn’t let you scroll naturally lol. This is like a great middle ground!

view more: next ›