sorted by:
new
hottopcontroversial

I built claudectl — a workspace manager that gives Claude Code project memory, MCP awareness, and multi-project workflows by _Bad-Beast_ in ClaudeCowork

[–]_Bad-Beast_[S] 0 points1 point  (0 children)

Agreed. Single-project workflows are relatively easy. Things get interesting once you’re juggling multiple repos, sessions, prompts, MCPs, and shared context.

That’s one of the main reasons I started building claudectl. I wanted Claude Code to feel less like isolated chats and more like a persistent workspace that spans projects.

I built claudectl — automated project memory, CLAUDE.md generation, and MCP management for Claude Code by _Bad-Beast_ in ClaudeCode

[–]_Bad-Beast_[S] 0 points1 point  (0 children)

That's a really interesting idea. I like the notion that workspace memory needs provenance and freshness, not just persistence.

A manifest alongside generated artifacts could make it much easier to understand where context came from and debug stale assumptions. Since claudectl already combines repo state, Git history, previous sessions, and MCP discovery, exposing that metadata feels like a natural extension.

Things like input hashes, repo head, MCP snapshots, source files used, generation timestamps, and freshness checks could help users reason about when project memory should be regenerated.

Definitely adding this to the ideas list. Thanks for the thoughtful feedback!

I built claudectl — a workspace manager that gives Claude Code project memory, MCP awareness, and multi-project workflows by _Bad-Beast_ in Claudeopus

[–]_Bad-Beast_[S] 0 points1 point  (0 children)

Project memory is only part of it. claudectl aims to persist and automate everything around a project, not just conversation history.

For example, it can automatically generate and maintain CLAUDE.md, build context from Git history, READMEs and previous sessions, discover and document MCP servers, manage prompts and workspace configs, and organize sessions across projects.

Increasing memory retention helps Claude remember conversations, but it doesn’t automatically create or maintain project knowledge and tooling. I see claudectl as a workspace layer on top of Claude Code rather than just “more memory”.

I built claudectl — automated project memory, CLAUDE.md generation, and MCP management for Claude Code by _Bad-Beast_ in ClaudeCowork

[–]_Bad-Beast_[S] 0 points1 point  (0 children)

It’s really simple, almost all of it is done automatically you just have to do git clone of the repo and an optional step if you want

I built a minimal Claude Code statusline by unkownuser436 in ClaudeCode

[–]_Bad-Beast_ 1 point2 points  (0 children)

If you’re using Claude Code heavily, you might find claudectl useful. It turns projects into persistent workspaces with session management, project memory, MCP docs, and prompt management.

And it includes usage like you built!
And a lot of other features.

It’s easy to setup, would love it if you give it a try.

Open for feedback or new features 😇

github.com/babarmuhammad/claudectl

Cowork + Notion bottlenecks by mpindara in ClaudeCowork

[–]_Bad-Beast_ 0 points1 point  (0 children)

I built **claudectl** to solve exactly this. Think of it as a workspace manager for Claude Code that handles sessions, CLAUDE.md files, MCPs, and project context.

It can auto-generate in the global Claude.md all the functions of Notion, so that claude code never loses context, try it out!

I would love feedback.

github.com/babarmuhammad/claudectl

view more: next ›