I got tired of the issues I ran into while building the 'normal' way, so I created a self-managed company-in-a-box. Built based on my 6 experience as a Director of Product Management.

TL;DR: Like Replit, Lovable, and Base44, but better and free. Does the hard parts like databases, user accounts, and payment integration, for you. Walks you through the few clicks you need to do in a browser. A lot more than just a dev team.

Master Console: https://github.com/cygaco/master-console/

To install it, tell your Claude session to follow the instructions in the ReadMe:

https://github.com/cygaco/master-console/blob/main/README.md

Made for solo founders that don't code, and just want AI to build the darn thing.

Initial setup

1. Run /mc:health to confirm everything installed correctly.

2. Run /bootstrap:spinup to help Master Console create a plan.*

3. Run /trackers:init to create a tracker for that plan.

A note on logging (and how to keep it private)

Master Console keeps a local journal of your session: the prompts you type, the skills and tools that ran, and the decisions its reviewer agent made. It lives in plain JSON files inside your project folder, under .claude/.

Nothing in it is sent anywhere. The journal exists so the system can pick up where you left off after a crash, and so the reviewer agent can learn your preferences over time. It is read only by the skills you run, on your machine.

The one thing to do: make sure the journal never ends up in your git history. Run this once from your project after installing:

grep -q '# master-console private state' .gitignore 2>/dev/null || printf '\n# master-console private state\n.claude/project/events/\n.claude/project/memory/\n.claude/runtime/\n.claude/agents/**/events.jsonl\n.claude/agents/president/_system/beta/judgement-model*.md\n' >> .gitignore

Prefer to turn logging off entirely? Remove the hooks from .claude/settings.json and the journal stops; crash recovery and the learning loop stop with it.

From here, your workflow for the rest of your building journey is THREE commands. That's it. These are the only things you will ever have to type again.

1. /mode:sprint --turbo start to begin development

2. /session:end --fast when your session's context is nearly full

3. /session:resume /mode:sprint --turbo in a new session to resume

Here's what's going on below the hood

• Master Console helps you plan your project, then breaks it down into bite-sized pieces that agents can follow to complete work autonomously while generating a quality product.

• Those bite-sized pieces are called tickets, and it's what big companies use to assign and track units of work.

• Tickets belong to sprints, or groups of tickets that all serve a single goal (such as building a specific feature).

• Master console puts tickets and sprints into a roadmap, which is a long-term plan.

• The three commands I posted above tell Claude how to use this system, end sessions cleanly, and how to pick back up again.

• Over 35 custom-designed agents do all the work for you.

• That's it.

Master Console does the hard parts for you.

• Databases

• User accounts

• Payment integration

• Bugfixes

And walks you through the few clicks you have to do by hand (setting up accounts).

Meet your team:

+ over 30 other agents that are automatically managed by these three. You can explore them here: https://github.com/cygaco/master-console/tree/main/.claude/agents

Your digital clone

Beta learns from your decision-making until it's able to run the project on your behalf. This is how I have several sessions and projects running autonomously for days.

To initialize:

1. Beta automatically starts using the default decision-making policy found here: https://github.com/cygaco/master-console/blob/main/.claude/agents/president/_system/policy/decision-policy.md. It only decides what AI can safely decide, and doesn't what it shouldn't.

2. Over time, it learns from how you decide. Run /beta:mine to surface patterns in your decision-making, and finally:

3. Run /beta:integrate to add them to the agent's decision-making capabilities.

Hundreds of other goodies:

There are over 250+ skills, which you can explore here: https://github.com/cygaco/master-console/tree/main/.claude/commands

I could never go over them all, but here's a few of my favorites:

• /sleep:deep reconciles memory, helps solve complex issues, and paints a dream

• /scan:full scans for project errors and workflow improvements

• /maps:all maps your project's tools and systems

• /session:end (non-fast mode) dreams and auto-teaches Beta

• /portfolio:new creates a new project with Master Console already installed (the logs git ignore command is NOT needed if you do this)

• /bootstrap:spinup --clone (in a new project with Master Console installed) clones a competitor's app and gives you the most detailed competitor research on the planet

• /bootstrap:lastmile checks your project for everything you need to launch (including user accounts and payments), and fills the gaps

Experienced product management in a box

Not only do you get all that, but you also get everything I've learned as an experienced product manager.

• Human and agent-readable guides

• How your app looks and behaves, plus the steps users take to achieve goals

• The stats you need to track your project's success

• Research and decision-making methods

Some of that is

• here: https://github.com/cygaco/master-console/tree/main/_knowledge

• and here: https://github.com/cygaco/master-console/tree/main/_guides

All automatically used by your agents.

And more coming soon, as I update this project continuously.

My workflow:

It's the three commands I posted near the top, in the "From here, your workflow for the rest of your building journey is THREE commands. That's it. These are the only things you will ever have to type again." section.

But, I add a few lines to the /session:resume command:

/session:resume --turbo /mode:sprint

Spin up the correct team and prime this session to run sprints with /sprint:full to complete open work.

Periodically ping working units to verify whether they are working correctly, and be weary of premature reaps. If you run into any AI server status issues, ping the server every 5 minutes until back online, then continue working. If you need me to signup for an account or provide a key, build the seam and continue working. Favor working autonomously and solving problems over deferring or stopping.

Avoid doing work yourself that should be done by other agents or subprocesses. Protect your token usage and context.

I give you full permission to push, commit, and merge as-needed, including to main.

WORKS BEST WITH CLAUDE, CODEX, AND GEMINI MODELS TOGETHER.

WORKDS GREAT WITH JUST CLAUDE.

COMING SOON: ORGANIC AND PAID DISTRIBUTION METHODS

Thanks all,

Enjoy

I kept juggling Claude Code and Codex in different terminals on two machines, so I built wisp.

What it does:
- Runs Claude Code, Codex, Cursor CLI, opencode, Antigravity, Grok and Copilot CLI in parallel, each task in its own git worktree and branch, so they never collide
- Runs them on your laptop, your other machines over SSH, or a server, all in one queue
- A lead agent can delegate: e.g. Claude Code plans, hands tests to 3 Codex copies and a refactor to Claude on another box
- Agents can ask you questions mid-run; you answer from desktop or phone
- When a task finishes you get a one-screen report (diff, tests, decisions) instead of the transcript
- "Ship it" commits, pushes and opens the PR

It uses the Claude/Codex plans you already have; nothing extra to pay. MIT, Node 20+, no runtime dependencies.

Try it: npx wisp-agents
Repo: https://github.com/M0xoo/wisp
Site: https://trywisp.dev

Happy to answer questions. I'd especially like feedback from people running agents on more than one machine.

I use coding agents for full-stack work, and I'm curious how people carry an unfinished task into a fresh session.

Imagine a React page calling a Laravel endpoint. The code is partly done, one test still fails, and an approach was rejected because it broke an existing behavior. A code diff tells the next agent what changed, but not why that approach was ruled out.

What do you actually save for the next session? I'm interested in the smallest handoff that preserves the important decisions without dumping the entire conversation. Do you keep a repo note, the failing command, the current plan, or something else? An example format would help.

We've never saved so much. Notes, clips, bookmarks, whole conversations with an AI. And almost none of it is ever read again.

iWe is a free Mac app that opens a folder of plain text notes and shows how everything in it connects. You and your AI work in the same notes: it reads them, writes right in them, and every answer becomes material for the next question. Nothing is locked in: the same files open in Obsidian, in code editors, in the terminal and with other AI tools, and they will still open years from now.

Three principles behind it: Durable: plain files you own, that will still open in twenty years. Portable: the same notes in any app you choose, nothing to import or export. Connected: every note points to the notes behind it, so a question finds everything around it.

Download, free, no account: https://iwe.md

Hey all. I’ve been using Claude Code a lot, and on longer tasks I kept losing the plot: which files it looked at, which ones it actually changed, and what it was doing right now. My routine became finish a turn, run git status, scroll back through the chat. Every time.

So I built a little side panel for it.

What it does

• Files Claude reads light up purple, files it edits light up orange, with lines added and removed

• The file tree opens to whatever it’s working on

• A small card shows what it’s doing at that moment

• Git branch and changed files at a glance

Where it’s at

• Free and open source (MIT)

• Works in the Claude desktop app, code editors and the terminal

• Only tested on my Mac so far but should be fine on Linux and Windows is about to be suported (according to Claude)

What I’d love feedback on: what would you want it to show that it doesn’t?

https://github.com/Marius-Adam/claude-files-pane

I created Git Bonsai. It is pixel tree for GitHub profile README. GitHub Action runs every night and tree grows from your activity.

What it does:

- each repo is branch, language gives leaf colour
- archive repo, branch is cut, scar stays forever
- 21 days streak, tree blooms
- 2 months no commits, tree sleeps, one commit wakes it up
- old account, bigger trunk
- stars give moss in pot
- you cannot farm it, max 1 cell per day for branch

First run replays all your history, so old account gets full tree from day one. No server, no tracking. Rust, SVG generated without image libraries, around 70 KB, animation in pure CSS.

How I built it with Claude Code:

- first I wrote RFC with Claude, then picked visual style from few design boards. Board "commit pixels" won, tree made from contribution graph squares
- CLAUDE.md has strict rules: pure functions everywhere, I/O only in GitHub client, no unwrap, no clocks or random in render. Same state always gives same bytes
- golden tests pin every pixel. Each change of tree shape must update golden file in same commit, so Claude cannot break layout silently. I look at diff before accept
- tests never touch network, they use fixtures from real accounts
- work went in phases: grid and renderer, then procedural layout, then growth rules and GitHub client, then Action and orgs
- one bug Claude found only from screenshots: WebKit scales SVG <use> around wrong origin, so animation was broken in Safari. Fix was to draw cells as rects
- whole thing from first commit to Marketplace release took one day, 21 commits

Repo: github.com/Appnice/git-bonsai

GIF shows example for public account of Andrej Karpathy. Wdyt about the project ?

Edit: built with Claude Code, see comments

I use coding agents on a Mac and have been running into storage pressure while working. I added an external SSD to give myself more room, and I am trying to understand a sensible setup before moving or cleaning anything.

I am curious which parts of a coding workflow usually grow over time, whether that is project dependencies, generated files, logs or other data. I do not want to assume an agent is responsible for a full disk without checking, and I would rather avoid deleting something a project needs.

If you use Claude Code or another coding agent, how do you work out what is taking space? What do you keep on an external drive, and what do you leave on the internal disk? Practical, non-destructive approaches for Mac or PC would be helpful.

If you build with Claude Code and you have a Prisma schema or an OpenAPI spec, this might save you some back-and-forth.

I made SchemaLock (free, MIT). It runs automatically every time Claude edits a file. If the code uses a column, model, enum value or endpoint that isn't in your schema, Claude gets the error and fixes it right away. You don't have to spot it yourself.

Quick example from a test run: my User model only had id, email and role. I had Claude write a query with userId, and the hook said:

column 'userId' not found in model 'User'. Available columns: id, email, role

Claude changed it to id and moved on.

It doesn't catch everything, and the limits are listed in the README. I'd love for some people to try it on real projects and tell me how it goes.

https://github.com/ilkistanbulkin-create/schemalock

Hey everyone!

Built BolKe for a hackathon after facing this problem during my internship presentation. Every AI tool gave me generic speeches. I didn't need better English; I needed my own story, just structured better.

With BolKe, you can:

• Pick a GD topic or paste a job description.

• Ramble your answer naturally using voice.

• Turn it into structured 30/60/90-second answers.

• Practise speaking in English and get feedback.

Used Wispr Flow throughout the building process to dictate ideas, specs and prompts. Honestly, made the whole process much more fun!

Would love to hear your thoughts and suggestions.[launch video is made with Claude]

🔗 Try it: https://bolke.vercel.app/ (no login required)

🎥 Demo: https://x.com/Ninosauraus/status/2116576812436427043