F4goals - Claude Integration! - Auto tasks on fly

Reddit post + Mendoop waitlist: F4Goals "Push to Claude"

Drafted 2026-09-22. One waitlist page and one Reddit post, doing three jobs at once:

| Goal | How this does it |

|---|---|

| Market Mendoop | The waitlist is a Mendoop page. Every public page has a "Create your own waitlist" button and a "Powered by Mendoop" footer, and the post names Mendoop once, as a disclosure |

| Market F4Goals | The post is about its newest feature, and the waitlist page links to f4goals.com |

| Start on Reddit | A feedback question rather than an ad: one subreddit, one link, and you answer every comment |

The waitlist doubles as the measurement. Its dashboard shows views, signups and conversion; the thread tells you the reasons.

Fill in before posting: {WAITLIST_LINK} (once the page exists) and the ...] in the Windows answer under [Replies you'll get.

---

Before you post

1. Read the rules of the sub you pick. I couldn't: Reddit is blocked for the tools I have here. Check self-promotion, required flair, links to your own project, and any account age or karma minimum. If promotion is only allowed in a megathread, put it there.

2. Comment in that sub for a few days first. Mendoop's channel doc says the same: a zero-history account posting a tool link is removed, and the removal costs you that sub for good.

3. Use a dark colour identity (Voltage, Transformative Teal, Warm Mahogany, Clubroom or Midnight Coral). On production today the five light ones render invisible titles and form fields. The fix (BUG-F08, v0.5.1) is on fix/wl-theme-text-colour and isn't merged to main.

4. Test a join from a private window, on a throwaway waitlist. Anonymous joins didn't work until Sept 12 (BUG-009). Use a throwaway because the dashboard can't delete a single subscriber, and a test signup on the real page would show as "1 person is already in".

5. Mendoop doesn't send email. The page promises to write to people. That means exporting the CSV and emailing them yourself.

6. Confirm the two facts the copy leans on. @f4goals/runner is still unpublished (private: true, and a 404 on npm when I checked on 2026-09-22). And other people can install the Android app (your plan lists the Play listing as unverified). If either changes, edit the "not public yet" lines, or say "web app" instead of "Android app".

7. After posting, reply to every comment in the first hour and log it in 12-pipeline-tracker.md.

1. The waitlist entry

Mendoop dashboard, then create a waitlist.

| Field | Value |

|---|---|

| Name | F4Goals: Push to Claude |

| Slug | f4goals-push-to-claude (what the name auto-generates) |

| Launch date | Leave blank. It hides the countdown, and you have no date to promise |

| Cover | Optional. A phone screenshot of the button works, and the cover is also the link-preview image |

| Collect phone | Off |

| Layout | Editorial (works with no cover, and gives the pitch the most room) |

| Colour | Midnight Coral (dark, and its indigo ground is close to F4Goals' blue), or Voltage |

Pitch. Paste this into the bio box exactly as it is:

`text

Tap Push to Claude on a task in F4Goals and Claude Code works on it on your own computer, on its own git branch. Nothing merges until you approve it.

Here's how it works

• You push a task from the Android app or the web app
• A small runner on your computer starts Claude Code on it, in its own worktree, and you follow progress in the app
• When it finishes, you tap Approve to merge it into main, or Reject to throw the branch away

Good to know

It runs on your machine, with your own Claude Code login. F4Goals doesn't upload your repo, and nothing runs until you push a task.

It is not a sandbox, so only link folders you would trust a contractor with.

It is early. The runner isn't public yet, and this list is how I find out whether anyone besides me wants it.

Join below with your email and I'll write to you when there's a build to try. I'll only use your email for that.

F4Goals is a free task manager where a task can be 60% done. It's an independent project, not affiliated with Anthropic.

`

Three things about how it's written:

• No blank lines, on purpose. Mendoop's markdown renderer turns blank-line-separated blocks into broken HTML (a <p> around every heading, and a stray </p> inside the list). One block per line renders cleanly. I ran this exact text through the real renderMarkdown to check.
• The first sentence is the link-preview description. The page builds its description from the first ~155 characters of the bio, so it opens with the hook. Keep that sentence first.
• No ?ref= on the waitlist link. Mendoop doesn't record it until analytics (T14) is merged. The F4Goals link on the page does carry ?ref=waitlist.

Use Preview in the create flow before you publish.

2. The Reddit post

Title (pick one):

• A (recommended): I can tap a task on my phone and Claude Code does it on my computer, on its own branch. Would you use this?
• B: Would you use a to-do app that hands tasks to Claude Code on your own machine? Nothing merges until you approve it
• C: Feedback wanted: pushing tasks from a to-do app to Claude Code (own branch, approve or reject from the app)

Body (paste in Markdown Mode):

`markdown

I built a task manager called F4Goals (a task isn't just done or not done, you slide it to 60%). Recently I added a feature I'm not sure anyone but me wants, and I'd like honest opinions before I put more time into it.

What it does

Every task has a Push to Claude button. I tap it (Android app or web) and Claude Code starts on that task on my own computer, on its own git branch in its own worktree. Nothing touches main until I tap Approve. Reject deletes the branch. Nothing runs on its own: I push tasks one at a time.

How it's set up

• A small runner on my computer connects out to the app, so there are no open ports or tunnels
• It uses my own Claude Code login. The app doesn't provide model access, and nothing runs on anyone else's machine
• Which folder a project can run in is decided on the computer with a link command, never from the app

What it isn't

• Not a sandbox. A session can reach outside its folder by relative path, so only link folders you'd trust a contractor with
• Not public yet. The runner isn't on npm, so you can't install it today

What I'd like to know

1. Would you use something like this? If not, why not?

2. What would you need to see before letting it near a real repo?

3. Is a to-do list a sensible place to start runs, or would you rather do it from somewhere else (issues, chat, the terminal)?

I know there are other ways to start Claude Code remotely. I'm trying to work out whether a task list adds anything, so blunt answers are welcome.

If you'd want early access, there's a waitlist: {WAITLIST_LINK}. The page is built with Mendoop, my other project (free to start), so it's a test of that too. Your comments help me more than a signup though.

I'm the solo dev behind both. More detail on how it works is in the first comment.

`

Attach a short screen recording if the sub allows media on text posts (tap Push to Claude, the branch appears, Approve). If it doesn't, link it in the first comment.

First comment. Post it yourself as soon as the thread is up:

`markdown

A few details for anyone who wants them.

Flow: Push to Claude on a task, and the runner (Node 20+, needs Claude Code installed and signed in) picks it up over a realtime connection, with a 15 second poll as backup. It creates a branch named f4goals/<task>-<id> off main in a sibling worktree folder, runs claude -p there with a small MCP server so the session can report progress, and commits on the branch. Then it waits for you.

Approve merges with --no-ff, only if the linked folder currently has main checked out, and aborts cleanly on a conflict. Reject removes the branch and worktree.

Defaults: the session can read, search and edit. Shell commands are off unless you add Bash to the allowlist. One run at a time, a 15 minute timeout, and each run is logged to handover.md in your repo.

What syncs to the app: run status and timestamps, the branch name, the local worktree path, the Claude session id, a progress number, and the session's summary (capped at 1,000 characters). Not the repo. Claude Code itself talks to Anthropic exactly as it does when you run it by hand.

The weak spot: linking is local, so a hijacked F4Goals account can't point it at a new folder. But it could push a task into a folder you've already linked, and Approve lives in the app too. That's why Bash is off by default. I'd like to hear what you'd want here (a confirmation on the computer? a second factor for Approve?).

`

Replies you'll get

Answers to adapt. They only claim what the code and the runner README support.

"How is this different from Claude Code on the web, remote sessions or GitHub Actions?"

Honestly, I don't know yet that it's better, and that's what I'm trying to find out. What's different: your own task list (with subtasks and progress) is the queue, it runs in your own checkout on your own machine, and Approve and Reject sit on the task. If you already work from issues or the built-in options, it may add nothing, and that's a useful answer for me.

"Isn't running an agent unattended dangerous?"

It can be. What's there: its own branch and worktree, nothing merges without Approve, shell off by default, one run at a time, a 15 minute cap. What isn't: a sandbox. Link a folder the way you'd give a contractor access.

"Does F4Goals see my code?"

No repo upload. The app gets run status and timestamps, the branch name, the local worktree path, the session id, a progress number and the session's summary (1,000 characters max).

"Do I have to pay you, or Anthropic?"

Nothing to pay me today. It drives your own Claude Code, so usage comes out of your own Claude plan.

"Windows? Mac? Linux?"

I use it on Windows. [Add anything else you've actually tested. Don't guess.]

"Why a waitlist instead of just releasing it?"

Releasing it means supporting other people's setups, and I'd like to know first whether it's worth that. A waitlist is the cheapest way to find out.

"Isn't this just an ad for your own tools?"

It's a feedback post, and yes, I built both things it links to, which is why I said so. Happy to take the waitlist link out if the mods prefer.

Where to post

• Best fit: a Claude-focused sub (r/ClaudeCode, then r/ClaudeAI). The question is about Claude Code workflows, and these are the people who can answer it.
• Keep r/SideProject for the posts your plan already gives it: the partial-progress GIF post, and Mendoop on Sep 29.
• One sub, one day. Cross-posting the same link to several subs in a day is on your own "Not doing" list. Let the thread play out first.
• If a mod objects to the Mendoop line, delete that sentence. The page still carries the Powered by Mendoop footer.

Rules from your plan that this copy follows

• No invented numbers, users or testimonials. Nothing here says how many people use or want this.
• Mendoop is "free to start", never "no paid tier", and the copy doesn't imply Mendoop sends email.
• F4Goals is described by what it does, not as an AI product. Claude Code is named only because it is the feature being asked about. Your plan says never to mention AI for F4Goals, so check that you're happy making an exception for this post.
• Nothing about the runner is promised beyond what exists. It is described as early and not public.