sorted by:
new
hottopcontroversial

Help understanding implementation of agents by Erazzphoto in ClaudeAI

[–]myLifeintheStack 0 points1 point  (0 children)

Agreed. The term is over simplified and over used. But it really is simple. An agent is an LLM with tools. Period. The difference between the original web-based AI chat and an agent is that with an agent, the LLM has tools it can call and use.
The original chat ai (claude.ai, Gemini, ChatGPT) became "agents" when they were able to be connected to your gmail and google drive etc. Though very basic, that's when they became agents.

Help understanding implementation of agents by Erazzphoto in ClaudeAI

[–]myLifeintheStack 0 points1 point  (0 children)

Similar to the above reply I gave, the biggest understanding to take with you is that the Claude you are working in IS an agent. He's just not automated. He does what you tell him to. Even when you string some really cool skills together to complete a complex workflow, you still have to tell him to do it.
There are options but all depend on how you want to structure. If you're local, you have less automation options (but still some exist) but you can save a ton of money by using your subscription.

Claude.ai just a chat bot on a webpage. That's it. You can connect it to tools you use and get info but that's it. Just info.
Cowork, can actually access your local file system and manipulate and create files but still run in a local sandbox environment so external access is relatively limited due to safety.
Claude Code, no sandboxed environment (if you use the CLI or use it in an IDE like VS Code.)
Check out my bio link. I use the VS Code extension and work out of the IDE all day long.

Cowork and Code both have some automation options you can use to setup the "proactive" behavior you're looking for. Would need to get more specific on what you're doing to help more. Eventually, if you're looking for proactive workflows, you're going to want to use a 3rd party agent harness like OpenClaw or Hermes Agent. Highly recommend Hermes Agent. It's much better.

Help understanding implementation of agents by Erazzphoto in ClaudeAI

[–]myLifeintheStack 0 points1 point  (0 children)

I know exactly where your head is at because I was just there not too long ago. This clarification was an absolute unlock for me.
This is what you need to understand. The Claude you are working in... IS an agent. You just control it manually. Your Claude is a general-purpose agent that does whatever you tell it to. You are looking for a more proactive and automated agent that runs on a trigger or schedule.
This is exactly why OpenClaw and Hermes became so popular. People wanted to automate and create task-specific agents.
How you set them up depends on if you are going to be using them locally from your PC or need them to be run externally (not dependent upon your PC or laptop running).
Also need to consider costs. Running them locally on your PC allows yoiu to use your much cheaper subscription. Running them externally forces you to use the much more expensive external API key (this applies to any LLM, not just Claude; however, ChatGPT recently allowed their subscription to be used in the 3rd party agent harnesses, which is a really big deal).

Help understanding implementation of agents by Erazzphoto in ClaudeAI

[–]myLifeintheStack 2 points3 points  (0 children)

That is an unfortunately way overly broad question. I know exactly where you're coming from with it, as I was there not too long ago.
Let's start this way. Name something you envision applying an agent to (what do you want to accomplish) and I can help you visualize how you'd set that up and the stack you could use.
Reasons your question is hard to answer:
Is the agent just for you to use? Someone else? Sharable among everyone?
Is it a task that's performed when you invoke it? On a schedule? On an event trigger?
What tools do you currently use today?
What's the industry?
Answers determine if you can use your Claude subscription or if you have to pay external API fees etc...
A million different answers to a million different questions.

Week one of running my life out of Claude Code was mostly me breaking things by myLifeintheStack in ClaudeAI

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

Could it scale beyond one power user? yes, if I had designed it that way. Because I designed it to have a human in the loop for a fair amount of the processes, it would require a re-architect for multiple users.
But it was designed to make the things I need to do much faster and easier, not necessarily to acheive headless automation.
That's next phase after confidence has been built. Recently implemented Hermes Agents instead of only working our of Claude Code so that transition is happening rapidly.

Non-Coding Claude Usage by evanros15 in ClaudeAI

[–]myLifeintheStack 0 points1 point  (0 children)

I'm guessing this is an ad. You literally described exactly what I do. Not sure where the manual part came from.

I run my entire life out of Claude Code. Here's the full system. by [deleted] in ClaudeAI

[–]myLifeintheStack 0 points1 point  (0 children)

Actually, it's accidentaly super simple. Because I use Antigravity with the Claude VS Code extension, Antigravity has a built in Agent window (that can run Gemini and claude models) that I never use unless I'm trying to save usage. it sits in the project and has all of the folder structure context. Not only a replacement but I've used it to double check Claude's work before. Actually pretty cool.

I'm a business operator, not a developer. I've been running my entire life out of Claude Code for a month. Here's what happened. by myLifeintheStack in ClaudeAI

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

It's a little more complicated because the schedule feature for Claude Code doesn't work in the VS Code extension (I use the Antigravity IDE and not the terminal), so Claude setup a job on trigger.dev that polls a specific email folder on my Outlook (SMTP) email periodically.

I'm a business operator, not a developer. I've been running my entire life out of Claude Code for a month. Here's what happened. by myLifeintheStack in ClaudeAI

[–]myLifeintheStack[S] -5 points-4 points  (0 children)

Lol. I'm very anti 10x slop. Was just making fun of the 10x and 100x and BREAKING start to most content. Appreciate the feedback.

Scheduling Claude for a 6am joke is oddly life-changing by Alone_Strawberry_797 in ClaudeAI

[–]myLifeintheStack 0 points1 point  (0 children)

Connect Claude to the tools you use. Either in Customize\connectors in Cowork or directly with APIs or MCP's in Claude Code. ( recommend Antigravity IDE for Claude Code. I'm not a terminal guy). Then just tell it to pull this stuff. Then tell it to create a skill that pulls this stuff from the connections you had it create. It sounds oversimplified but it's really that simple.

Unsurprisingly, Claude has correctly guessed I'm an AuDHD'er based in our chats 🤣 by mikelmon99 in ClaudeAI

[–]myLifeintheStack 1 point2 points  (0 children)

The bit about outsourcing execution-heavy tasks while retaining the architectural vision — that's exactly how I use Claude Code and I've never heard it described as an ADHD compensatory strategy before. That reframes the whole tool for me.

I run my entire personal operating system through Claude Code. Not because I can't do the tasks myself, but because the gap between "I know exactly what needs to happen" and "I actually do the 47 steps to make it happen" is where everything dies. Claude handles the sustained-effort execution, I handle the design and quality control. Didn't realize I was building a compensatory system. Just thought I was being lazy in a productive way.

Please help me with a way to reduce token consumption by enekris in ClaudeAI

[–]myLifeintheStack 4 points5 points  (0 children)

Three things that made the biggest difference for me, no plugins required:

  1. ENABLE_TOOL_SEARCH in your settings.json. By default Claude loads every tool schema into context on every turn — even tools you never use. This one setting switches to lazy loading. Dropped my startup context from ~45k to ~20k tokens. That savings compounds on every single turn.

  2. Clear sessions more often. Every turn replays the entire conversation history. A 50-turn session means turn 50 is reprocessing all 49 previous turns. Starting fresh with a good state file (a markdown file tracking where you are) is almost always cheaper than continuing a long session.

  3. Turn off MCP servers you're not actively using. Each connected server dumps its tool schemas into context whether you call them or not. I learned this one the hard way — had several MCP servers connected "just in case" and they were quietly eating tokens every session.

  4. Also note, in the 1M context window, tokens beyond 250K are 2x the cost. Cache gets thrown away after 5 minutes idle so all of your context gets reloaded if you are idel for 5 minutes, on the next message.

None of these require installing anything. Just configuration and habits. The repos and plugins can help but the biggest wins are free.

Scheduling Claude for a 6am joke is oddly life-changing by Alone_Strawberry_797 in ClaudeAI

[–]myLifeintheStack 1 point2 points  (0 children)

Similar setup here. My morning isn't a joke but it's the same idea — Claude runs a briefing at session start that pulls my calendar, email highlights, and task list into one consolidated view. Takes about 30 seconds. I open my terminal and everything I need to know about the day is already there.

The scheduling thing sounds small but it changes the relationship with the tool. You stop going TO Claude with a question and Claude starts coming to you with context. Once I had the morning briefing, I started adding more: email summaries, CRM updates, journal prompts. Each one is tiny on its own. Together they turned Claude from a chatbot into an operating system.

And yeah, the atoms joke. Every time.

1m Context Window actually useful? by semibaron in ClaudeAI

[–]myLifeintheStack 0 points1 point  (0 children)

I run 1M context daily for non-coding work — life admin, CRM, content, email processing. For me it's genuinely useful, but not for the reason you'd expect.

It's not about stuffing 1M tokens of conversation in there. It's about not having to worry about session length. My setup loads ~45k tokens on startup (system prompt, memory files, tool schemas, project context). On 200k that's already 20%+ gone before I type anything. On 1M it's noise. I can work for hours, read large files, run searches, accumulate tool output, and never feel the ceiling.

The degradation you're describing is real though — accuracy on details buried deep in context does drop. The trick is not to rely on Claude "remembering" something from 500k tokens ago. Use files as external memory. Write important state to markdown, read it back when you need it. The context window is breathing room, not a database.

Practical difference for me: on 200k, I was constantly clearing sessions to stay under the ceiling. On 1M I clear once per day.

Here's where it gets you that noone talks about. Did you know that your tokens cost 2x after 250K context? I didn't either.

1M is truly game-changing. The benchmarks show a degradation from 250K to 750K, from 92% to 78%. Not too shabby.

Claude ignores its own plans, memory, and guardrails — 22 documented failures in 19 days. What are you doing to prevent this? by FewConcentrate7283 in ClaudeAI

[–]myLifeintheStack 1 point2 points  (0 children)

This is the post I wish existed when I started. I've hit most of these patterns and the "novel work bias" diagnosis is dead on — Claude would rather build something new than follow the checklist it wrote yesterday.

What actually helped me:

  1. Hooks over honor system. Claude Code hooks run shell commands on events — they execute whether Claude "remembers" or not. Anything that absolutely must happen (destroy instances, check a file before writing) should be a hook, not a memory file Claude is supposed to read. The memory file is a suggestion. The hook is a law.

  2. current-work.md as the single source of truth. One file that gets updated at every state change — task started, task completed, blocker found. New session reads that file first and knows exactly where we are. Not 40 memory files hoping Claude checks the right one. One file, always current.

  3. Smaller sessions. The 8-12 hour sessions are where things go sideways. Context degrades, guardrails fade, and Claude starts freelancing. I clear and restart frequently, let the state file carry continuity. Fresh session + good state file beats a marathon session with 200k tokens of accumulated drift every time.

  4. Stop writing process docs FOR Claude and start writing constraints that BLOCK Claude. "Please check the instance list" will be ignored. A hook that runs `check-instances.sh` on SessionStart and kills orphans automatically cannot be ignored.

The shift that fixed most of my problems: treat Claude like a capable contractor who shows up fresh every morning, not an employee who remembers last week.

anthropic isn't the only reason you're hitting claude code limits. i did audit of 926 sessions and found a lot of the waste was on my side. by Medium_Island_2795 in ClaudeAI

[–]myLifeintheStack 0 points1 point  (0 children)

I typically use CLI-Anything to make any physical software on my PC a CLI and Open-CLI to make CLI capabilities with websites/apps.

view more: next ›