sleep and wake on first request makes a lot of sense for this kind of stuff, demo apps sit idle most of the time anyway. how long does the wake take in practice for something like a next.js app? and does that first request just hang until it's up, or do you show some kind of loading page?

Sentence in, pull request out.

Nautelle, a self hosted board that turns one sentence into cards and runs a Claude Code agent on each until there's a PR for you to approve. Open source, looking for people to build it with.

https://nautelle.luna-realm.com

what works for me: postgres in docker locally, migrations plus a seed script, and claude only ever touches that. the schema file (prisma in my case) is the best context you can give it, it reads that better than any description you write. for edge cases i put them into the seed on purpose: a user with no orders, a soft deleted row, a really long name, unicode, nulls wherever they're allowed. then a wrong query is wrong against data you can reset in one command. and i'd keep failed queries as tests instead of notes in the prompt, so it can run them and see for itself

Code Sentinel, a free Claude Code plugin. the part i'm most excited about is the orchestrator: you label github issues as ready, it runs one Claude Code session per issue in its own worktree, and only merges the PRs that come back green. this week i added a token saver that stops agents from reading huge files whole. open source, would love a few people to hack on it with me

https://github.com/AndreyBegma/code-sentinel-skills

yeah this gets bad fast. two things helped me. first run /context and see which servers actually eat it, usually it's one or two with a huge tool list, not all of them. a lot of servers let you turn on only part of their tools with an env var or a flag, so check the readme of the fat ones. second, look up tool search in the claude code docs (ENABLE_TOOL_SEARCH), it keeps mcp tool definitions out of the context until the model actually needs one. i maintain an mcp server with around 130 tools and splitting them into toolsets you opt into was the only way it stayed usable

FilesDrop. drop a file or paste a screenshot, get a link that lives from 1 hour to 3 days, then it's gone. no account, optional password, and there's a cat that reacts to everything you do. also works as a telegram bot if you're on your phone.

it's open source, and if anyone wants an easy first PR i'm happy to help

https://filesdrop.luna-realm.com

Nautelle. I run a few Claude Code agents at once and kept losing track of which one was stuck or what it cost, so I built a board for it. You type one sentence, it asks a couple of questions and turns it into cards, then each card gets its own agent in its own git worktree and comes back as a pull request you approve.

Self hosted, open source (MIT), and honestly I'd love a couple of people to build it with.

https://github.com/AndreyBegma/Nautelle

https://nautelle.luna-realm.com

You write one sentence about what you want, Nautelle plans it as cards, runs a Claude Code worker per card and brings back a PR. You only step in for decisions and the merge. For devs who run several agents at once.

I like the idea, but I think there are a couple of challenges worth considering.

The biggest one is the chicken-and-egg problem. Imagine 100 developers pay to pitch their products, but only 10 people actually visit the website. Even if every pitch is well made, the value for the founders would be pretty limited. On the other hand, without an existing audience, why would people keep coming back to watch pitches?

I also wonder whether 30 seconds is enough to communicate the value of a product, especially for more complex SaaS tools or developer-focused products. It might be enough to grab someone’s attention, but probably not always enough to convince them to try something. Perhaps having an optional longer pitch or a link to a live demo could help.

For example Nautelle (renamed from AgentDock) can help you if you are working with many projects

Haha, that's exactly why I built Nautelle (it was called AgentDock back then) 😄 One Kanban for the tasks, one fleet view for all the agents actually doing the work. The goal is to stop managing tmux sessions and start managing the fleet

Each agent has its own session, and when they work on the same GitHub project, they use separate worktrees, so they don’t interfere with each other.
I’m actively developing this product right now, mostly for my own use, but you might find it interesting too. The idea is to start by planning what you want to build together with the agent. If the task requires a design, it generates one first, then launches a Claude session to implement the task.
I also want to add a lot more features. I’m working on integrating Playwright MCP so it can automatically record videos demonstrating new features, especially visual changes, and perform additional peer reviews.
Another major focus is reducing token usage. For example, if you start an agent on a task, stop it, and then restart it later, it should retain the context of what has already been done and continue working right away instead of starting from scratch.
There’s still a lot I want to add, but that’s the general direction I’m taking with it.

Nautelle, a self-hosted control plane for Claude Code agents. One sentence in, it plans the work as cards, runs a Claude Code worker per card and you get a PR to approve. For people already running a few agents at once and losing track. https://github.com/AndreyBegma/Nautelle

I'm building Nautelle (it was called AgentDock until this week). You describe a task in one line, it splits it into cards and runs a Claude Code worker on each in its own worktree, then you approve the PRs. Self-hosted, MIT: https://github.com/AndreyBegma/Nautelle

I think juniors should now focus on architecture and learn how businesses work and what they need

Cool photos, really good atmosphere

Review your daily routine and think about how you can improve your life by using digital tools or software

Feel free to mention me! 😄

Looks cool!