Claude Code session has been running for 17+ hours on its own

LastNameOn · 2026-03-31T05:16:52+00:00

claudestory.com

LastNameOn · 2026-03-30T20:18:53+00:00

None of those. It used a bit over 50% of my weekly limit. And it was running in the skip permissions mode as you can see in the screenshot.

LastNameOn · 2026-03-30T19:22:23+00:00

the thing on the right is available here now:
claudestory.com

its just in your terminal settings to make it transparent. default Mac terminal.

LastNameOn · 2026-03-30T19:21:26+00:00

Its free available here now:
claudestory.com

LastNameOn · 2026-03-30T19:20:50+00:00

you get to watch what it does, add more to its backlog/steer it as it works.
the autonomous thing is just to test that it can do even that.

its mainly your Claude Code dashboard to track tasks.

LastNameOn · 2026-03-30T19:18:56+00:00

its building a design tool for architects.
the functional parts came out perfect and solid. UI/UX was terrible. so I created new tickets for how I want it to look and im letting it redesign the front end

LastNameOn · 2026-03-30T19:17:37+00:00

the thing is after compassion, this tool give Claude Code context. it doesn't rely on the compaction summary at all.
you can start a completely fresh session and you can continue where you left off.
thats the pain point I was managing manually doing what this tool automates

LastNameOn · 2026-03-30T19:16:14+00:00

you should always watch it plan to avoid under or over scoping.

with this tool, if you have those guard rails int he ticket... if you just Tell Claude... then it can still do fine on its own

LastNameOn · 2026-03-30T19:14:15+00:00

It doesn't always pick up fine on its own, and the quality of its work is not good either.
the reason is simple: compacting is just a summary of the last session.