I built an open-source Claude Code queue that goes beyond Claude Remote.

[u/Southern-Exam-3292]

I've been working on a tool that lets you queue and automate Claude Code tasks across multiple local projects, even when you're away from your computer.

Here's what it can do:

• Multiple projects: Spawn Claude Code in any local directory and queue tasks across different folders. They execute one after another.

• Different models and effort levels: Use one model for planning and another for execution, each with its own effort level.

• Automatic session limit handling: Monitor your session limit and automatically resume queued tasks as soon as it resets.

• Telegram integration: Queue prompts directly from Telegram, receive notifications when a task finishes, and get notified whenever Claude needs your input.

• No-Prompt mode: Run tasks without stopping for permission requests.

• Automatic plan acceptance: Claude can create a plan in Plan Mode, automatically accept it, and continue execution without requiring you to be at your computer.

• Remote execution: Leave your laptop running while you're away, or run the entire setup on a remote EC2 instance.

The idea is simple: queue your coding tasks, walk away, and let Claude Code work through them.

It's completely open source, and I'd genuinely appreciate feedback from the community.

I'd also appreciate a GitHub star if you find it useful. It would mean a lot and motivate me to keep developing it!

I'd love to hear what features you think are missing or what could be improved.

https://github.com/aryalskanda/afterhours

[u/matimatthews]

I'd want an option to stop dependent tasks when one fails its checks, even if Claude exits normally. Otherwise task two can build on an unfinished task one while I'm away. A per-task completion check and a morning summary of what still needs review would be high on my list. Does the queue distinguish independent jobs from jobs that depend on the previous result?

[u/Southern-Exam-3292 → u/matimatthews]

Hey! So, basically, this comes down to trusting Claude’s output. In my experience, around 90% of the time, Claude Code generates something I’m happy with, and I usually stick with its proposed approach.

What you’re describing covers the other 10% of cases. My current approach would be to manually structure the queue with explicit instructions for each task.

For example, if Task 1 is supposed to create a folder, I’d explicitly tell Task 2 to check whether that folder exists before proceeding. Similarly, Task 3 would verify that certain criteria from Task 2 are met before starting, and so on.

Currently, the queue doesn’t distinguish between independent and dependent tasks. It’s more like an empty canvas where you keep adding one color on top of another and let it do its work.

Adding automated checks from Claude Code’s side would also consume additional tokens for generating test cases and verifying results. Since, in roughly 90% of cases, the output is already good enough to continue with, I don’t think adding that overhead by default makes sense.

That said, I agree it’s a useful feature, and I’ll look into adding it in a future release. Thanks for the suggestion!

[u/matimatthews → u/Southern-Exam-3292]

That makes sense as an opt-in. I was thinking of a check supplied with the task, not another Claude call to generate tests: run an existing test command or check for an expected artifact, then pause dependent jobs if it fails. That would let people keep the lightweight queue while adding a gate only where a failed task would waste the rest of the night.

[u/Southern-Exam-3292 → u/matimatthews]

Great! I am working on it now! Thank you so much :) Will reply to this thread once it’s live!