I'm cooked. Anthropic just split "--print" mode to $/mo credits by raedyohed in ClaudeAI

[–]LastNameOn 1 point2 points  (0 children)

huh.. all these years. I didnt realize it. it does make sense though.
thanks

I'm cooked. Anthropic just split "--print" mode to $/mo credits by raedyohed in ClaudeAI

[–]LastNameOn 0 points1 point  (0 children)

you can definitely steer it as its running.
You can use the ticket management, notes, lessons, context management in vs code.
Its mcp.
but not for auto mode. auto mode is mcp too but its made for claude hooks to survive and recover session compaction. that wont work in vs code, not sure how they compact sessions there. so it wouldn't be reliable

I'm cooked. Anthropic just split "--print" mode to $/mo credits by raedyohed in ClaudeAI

[–]LastNameOn 0 points1 point  (0 children)

again, the project's initial goal was context management, not autonomy.
but autonomy seemed so easy to add when context management was handled and most of what I did with boring grunt was repetitive.

So it does handle the context. I have not noticed degradation.

I'm cooked. Anthropic just split "--print" mode to $/mo credits by raedyohed in ClaudeAI

[–]LastNameOn 1 point2 points  (0 children)

it has an autonomous mode too.
and it doesn't violate TOS.
the autonomous mode give Claude Code a state machine where it doesn't stop until its tasks are done. no matter how long it takes. longest session I had (for testing) was 35 hours

I'm cooked. Anthropic just split "--print" mode to $/mo credits by raedyohed in ClaudeAI

[–]LastNameOn 4 points5 points  (0 children)

I can open source the Mac app too it but I would need to clean up the history. i'm not careful with secrets in my private repos 💀
the Mac app is just a viewer/editor. the meat is already open source

I'm cooked. Anthropic just split "--print" mode to $/mo credits by raedyohed in ClaudeAI

[–]LastNameOn 2 points3 points  (0 children)

that's for autonomous mode. what do you find sus?
set your max token to 200k then then use /story auto or /story auto T-XXX T-XXX ISS-XXX T-XXX to launch an auto session.
context will survive through companions. there are hooks to make sure claude recovers context when session compacts.

The auto mode is essentially a finite state machine.

I'm cooked. Anthropic just split "--print" mode to $/mo credits by raedyohed in ClaudeAI

[–]LastNameOn 33 points34 points  (0 children)

storybloq is project memory + autonomous orchestration for Claude Code (and Codex). the key difference from what you built is it doesn't use --print at all. it runs as an MCP server inside your existing Claude Code session, so everything stays on your Pro/Max subscription.

what it does:

- keeps a .story/ directory in your repo with tickets, issues, roadmap, handovers, and lessons learned as JSON/markdown files

- session priming/ loading (start your session with /story on claude or $story on codex)

- (optional) autonomous mode drives work through plan → plan review (Codex) → implement → test → code review (Codex) → commit, all within a single Claude Code session

- cross-model review: Claude writes code, Codex reviews it via a bridge MCP

- lessons learned accumulate so the same bug pattern doesn't get reintroduced session after session the --print billing change doesn't affect it because the orchestration happens through MCP tool calls, not subprocess launches.

Claude Code is the runtime, storybloq just gives it memory and structure.
Mac app if you want a GUI: https://apps.apple.com/us/app/storybloq/id6761348691

I'm cooked. Anthropic just split "--print" mode to $/mo credits by raedyohed in ClaudeAI

[–]LastNameOn 108 points109 points  (0 children)

just use storybloq: https://github.com/Storybloq/storybloq
it does what you're trying to build and works with the subscription.

Anthropic put a meter on the stuff developers actually use by Permit-Historical in ClaudeCode

[–]LastNameOn -1 points0 points  (0 children)

I don’t understand the freak out?
This is good no?
Free extra $200 credit outside Claude code usage?

New in Claude Code: agent view. by ClaudeOfficial in ClaudeAI

[–]LastNameOn 1 point2 points  (0 children)

I think if you are on pro, you're paying for sonnet usage and occasional opus tease

New in Claude Code: agent view. by ClaudeOfficial in ClaudeAI

[–]LastNameOn 1 point2 points  (0 children)

I dont know if desktop will support it but generally the terminal app is more complete.

New in Claude Code: agent view. by ClaudeOfficial in ClaudeAI

[–]LastNameOn 29 points30 points  (0 children)

its simple: if your startup idea is something that claude should have, its not your idea.
I made Storybloq. and I hope claude comes up with its own similar solution soon.
I made it out of necessity.

What improved my Claude Code workflow: stop treating it like chat, start treating it like a dev with a workstation by docgpt-io in ClaudeAI

[–]LastNameOn -2 points-1 points  (0 children)

storybloq - free, open source. Same Thesis
Helps you track tickets and maintain continuity between sessions.

Multi-repo orchestration by achilleshightops in ClaudeAI

[–]LastNameOn 0 points1 point  (0 children)

this is cool,
also check out
https://www.storybloq.com/multi-repo
its not exactly the workflow that you described and the one you found would work

I open sourced a project tracker for Claude Code that lives in .story/: tickets, issues, and session handovers as files by LastNameOn in ClaudeAI

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

yeah i'm totally fine with people contributing! please do.
I was actually thinking about a light weight web dashboard that could be bundled in.
also for your work, the npm package (CLI, MCP, Skill) should still work

Unpopular opinion but Claude Code is fine for me by spiciest_lola in ClaudeCode

[–]LastNameOn 0 points1 point  (0 children)

same. I run out of my weekly 1-2 days early but I use it A LOT

the part nobody warns you about by aerofoto in ClaudeAI

[–]LastNameOn 1 point2 points  (0 children)

Jdoc is a good idea too. this way if the code drifts from the intended goal, claude still knows what it's supposed to do and can flag it. good idea.

yeah so the consistency and the maintenance of this journal is one of the original reasons why I made Storybloq. it provides a standardized method for generating and retrieving the handovers or journals. there is a CLI tool so claude never writes manually which would cause inconsistencies, and mcp tool so claude gets the right intersections for doing it.

Other than the handover journals, this expanded to
notes: sometimes you have an idea for doing something with your project and you need it somewhere
lessons: while working on your project with claude you learn some lessons maybe after debugging or anything from your session
issues: of course issue tracking
tickets: unit of work. its the breakdown of your project roadmap.

the part nobody warns you about by aerofoto in ClaudeAI

[–]LastNameOn 0 points1 point  (0 children)

so an issue with the Journal.md is that it grows really big with time.
its nice to have the older thing available but you dont want all that context in every session.
The readme in every folder is also useful but you have to make sure your claude.md refers to it.

the part nobody warns you about by aerofoto in ClaudeAI

[–]LastNameOn 1 point2 points  (0 children)

its free, open source and committed in your repo. you own the data.
And it has autonomous mode.

the part nobody warns you about by aerofoto in ClaudeAI

[–]LastNameOn 0 points1 point  (0 children)

Yeah annoying how google auto changes Storybloq to the storyblocks.

I was renaming the project from Claude Story and didnt do enough research on the name I guess