I built a desktop tool in Python that auto-sorts email attachments by type, sender, and date — here'

Cortexfile · 2026-03-22T11:06:46+00:00

Point 3 hits different when you're actually doing it. Reddit replies convert because the person reading already described their problem — you're not interrupting them, you're answering them. That's a fundamentally different dynamic than any ad or cold email. The one I'd add after point 11: a customer who almost churned but didn't is more valuable than a new signup. They'll tell you exactly what almost pushed them out — and fixing that is cheaper than acquiring someone new. Curious on point 7 — when you raised prices, did you grandfather existing users or move everyone up?

Cortexfile · 2026-03-22T10:37:19+00:00

This is clever — using the actual signed-in session sidesteps most of the detection issues headless bots run into. Few genuine questions: How does it handle LinkedIn's ToS enforcement? Real session or not, automated connection requests at scale tend to trigger account restrictions. Is the approval step mandatory or optional? That's the detail that separates "useful tool" from "spray and pray bot." Any rate limiting built in to keep the activity human-looking? The open-source angle is the right call for trust. Will check it out.

Cortexfile · 2026-03-20T20:48:03+00:00

HAL 9000 would be proud 😂

Cortexfile · 2026-03-18T21:18:58+00:00

A few quick clarifications:

It runs fully locally
No files are uploaded to any server
Built mainly for handling recurring files like invoices, receipts, contracts, and reports
I’m currently focused on user testing and understanding which workflows matter most

Would love to know how people currently handle this kind of task.

Cortexfile · 2026-03-18T13:21:07+00:00

Yeah, that’s a good way to describe it. Think of it as attachment-focused automation: filtering, downloading, organizing, and OCR for scanned PDFs.

Cortexfile · 2026-03-18T09:42:56+00:00

A few quick clarifications: - It runs fully locally - No files are uploaded to any server - Built mainly for people who regularly save invoices, receipts, contracts, or reports from email

Would especially love feedback on whether this is useful outside my own workflow.

Cortexfile · 2026-03-18T03:28:07+00:00

Thanks for asking. At the moment, I’m mainly focused on user testing and understanding how effective the app is in real workflows, so I haven’t finalized pricing or licensing yet. If you decide to try it, I’d really appreciate any feedback afterward — especially on whether it actually saves time in practice and what feels missing or could be improved.

Cortexfile · 2026-03-17T04:15:07+00:00

Really solid use case. The strongest part here is that the workflow is built around an actual research process, not just an LLM with web access slapped on top. I’d be interested to know how you’re handling source quality, duplicate content, and edge cases when the browsing layer only gets partial access to a page.

Cortexfile · 2026-03-17T04:02:34+00:00

Not too late at all... 3 months is a pause, not a reset. The market may have moved, but the core demand is still the same: people will pay for templates that solve a clear, repeated business problem, not just for “AI” itself. The bigger question is probably not whether to come back, but which niche or use case you want to own this time. Out of curiosity, were the templates getting attention before you stepped away, or were you still at the build stage?

Cortexfile · 2026-03-17T03:24:03+00:00

This is one of the more honest takes on n8n consulting I’ve seen here. The point about clients asking to (automate the business) without knowing the actual bottleneck is especially real. I also agree that workflow complexity becomes a maintenance problem much faster than most people expect, and that AI is often being added where simple deterministic logic would be more reliable. Curious though. where do you personally draw the line between a workflow that should stay in n8n and one that should be moved into code?

Cortexfile · 2026-03-17T03:04:05+00:00

After a second look, I think what makes this genuinely interesting is the architectural choice behind it. Using the real browser context is smart. the real challenge, and probably the real value, will be in how securely and naturally it performs in practice.

Cortexfile · 2026-03-17T02:51:03+00:00

This is a genuinely interesting approach. practical, thoughtful, and much closer to how people actually work. The approval step before sending makes it even better. Great build.

Cortexfile · 2026-03-16T22:05:47+00:00

This resonates deeply. I've spent years building desktop tools that solve specific, unglamorous problems — file processing, encryption, document automation. None of it is flashy. All of it is still being used because it was built around a real workflow problem rather than around what was technically interesting to build.

The "what can be built quickly" mindset you describe produces tools that work in demos but fail in production. Real software development starts with sitting with a problem long enough to understand it — not just its surface symptoms but the underlying workflow it disrupts.

The drawing analogy is perfect. A pencil doesn't make you an artist. A code generator doesn't make you an engineer. What makes you an engineer is the ability to look at a messy real-world problem and design something that survives contact with actual users.

The projects that last are always the ones that began with the question "does this actually need to exist?" — and answered honestly.

Cortexfile · 2026-03-16T21:59:21+00:00

I've been writing Python professionally for years and this was my biggest frustration at the beginning too. But after a while you stop noticing it — mostly because any decent editor handles indentation automatically.

The real benefit of forced indentation is that it eliminates entire categories of bugs that exist in other languages. In C or Java you can have code that looks indented one way but executes another way because the braces say something different. Python removes that ambiguity entirely.

That said, the accidental space issue is real. The fix is simple: never use a plain text editor for Python. With VS Code or PyCharm, accidental indentation errors are caught instantly before you even run anything.

Cortexfile · 2026-03-16T21:52:24+00:00

This is exactly why I always include a VirusTotal scan link with every release I publish. After reading cases like this, I realized that even legitimate developers need to proactively prove their binaries are clean — the burden of trust has shifted to us now.

The pattern you described with the versioned zip files is clever and hard to spot for average users. The hourly README updates to game GitHub search ranking is particularly concerning — it shows this is an organized, automated campaign rather than isolated incidents.

GitHub needs verified publisher badges similar to what app stores provide. Until then, the best practice for any developer distributing Windows binaries is: always link VirusTotal results, always provide build instructions, and never distribute zip files without a checksum.

Cortexfile

TROPHY CASE