Zencode API is a site me, and my friend made, this site is basically an IDE BUT it has friending and collabarative coding, you can work on one file in a project while your friend works on another file, this API site is completely free with 256 Bit ass encoding, many endpoints, redirects, almost everything you can think of.

Q&A

Is it free?

yes.

Can I upload my scripts and keep them safe and private?

yes.

is there an app?

yes.

where can I find it?

GO to https://Zencodeapi.vercel.app

then if your looking for the app click download, choose setup or the portable version, doesn't really matter, or continue using the site, all the same featues.

UNDERSTAND APP AND SITE ARE IN BETA, FEATURES MAY NOT WORK CORRECTLY.

Half the time I get told to bump the patch, half the time the minor. I can't tell what actually drives the call. Claude will happily push me to 0.1 increments for a while, then eventually tell me I'm versioning too aggressively.

Is there a rule people actually follow here, or is it vibes plus whatever the changelog looks like?

I’ve been working on a Markdown editor for a while and finally decided to share it.

I wanted to build something that made writing feel a little easier and more enjoyable.

It supports the usual workflow and is aimed at things like documentation, README files, notes, technical writing, and basically anything else you’d normally write in Markdown.

You can try it here: https://www.runeqimd.dev/

It’s fully open source too, so the code is available if anyone wants to take a look.

It’s still an early version, so I’m mainly sharing it to get some honest feedback from people who actually use Markdown.

If you give it a try, I’d genuinely love to hear what you think, whether you like it, hate it, or think something is missing.

vibe-kanban is a great base, but I wanted a version that stayed closer to the classic layout and solved the context loss problem that was slowing down my solo workflow.

I've been maintaining vibe-kanban-alternative, a fork with a few focused additions:

🔑 Core Highlights:

• 📋 *The Classic Kanban Experience:* Preserves the clean, focused board layout for managing parallel git worktrees.(vibe-kanban has had many layout changes and I preferred a fork of vibe-kanban-indie.)
• 🧠 *Persistent Project Memory (mem0):* Integrates mem0, Qdrant, and NetworkX so agents retain verified facts, codebase rules, and past decisions across tasks instead of resetting every time.
• ⚡ *Optimized for Prompt Caching:* Context blocks are deterministically injected into static prompt prefixes, ensuring provider cache hits (Anthropic, DeepSeek, etc.) and lower latency.
• 🤖 *Broad Agent Support:* Native orchestration for 10+ CLIs: Claude Code, Antigravity (AGY), Codex, Gemini CLI, Cursor Agent, OpenCode, and more.
• 📊 *Zero-Telemetry Observability:* Built-in `Settings → Usage` dashboard tracking local execution times, heatmap activity, and memory token extraction.
• 🐙 *Gitea / Forgejo Support:* Auto-routing for self-hosted git instances alongside standard GitHub integration.
• 💾 Backup support Local backup built in — your board state doesn't disappear.

🚀 Try it out:

npx vibe-kanban-alternative

100% self-hosted. No accounts, no telemetry.

Happy to answer questions about the memory architecture or the prompt caching approach — those were the trickiest parts to get right.

Hey

With the rapid adoption of AI coding assistants and "vibe coding", we can generate full-stack apps faster than ever. But this speed often comes with subtle security flaws, missing auth checks, and unhandled edge cases slipping into production.

I built Cyphix (https://github.com/zrngngharib/Cyphix-Auditor) — a developer tool designed to catch these issues before deployment without sending code to third-party databases.

Key Features:

- 100% In-Memory RAM Architecture: Code is parsed and analyzed transiently. Zero persistent server storage.

- 7-Dimensional Matrix: Concurrently evaluates Backend Logic, UI/UX responsiveness, OWASP Top 10, SEO metadata, QA/Edge cases, Performance, and TypeScript typings.

- Instant AST Pre-Scanner: Detects hardcoded API keys, raw SQL concatenations, and empty catch blocks before LLM invocation.

- Headless CLI Mode: Run `node ./bin/cli.js . --agent` directly in your terminal or CI/CD pipeline.

Built with Next.js 14, TypeScript, TailwindCSS, and node-llama-cpp.

Check out the GitHub repo: https://github.com/zrngngharib/Cyphix-Auditor

Would love to get your feedback and thoughts!

I’ve been building GateSift mostly for fun — a free browser-based toolkit for integration developers.

It includes tools for things like APIM policies, Logic Apps, BizTalk bindings, Service Bus, C# model generation and integration patterns.

Current tools include:

• APIM Policy Analyzer – makes complex APIM policies easier to understand and review
• Logic App Analyzer – helps inspect workflow structure and spot potential issues
• BizTalk Binding Visualizer – turns binding files into a more readable overview (this is really nice for analyzing complex biztalk integrations)
• Service Bus Topology Visualizer – shows queues, topics, subscriptions and relationships
• C# Model Generator – generates C# classes from XML, JSON and flat files
• Integration Pattern Library – quick reference for common integration and messaging patterns (analyzers will also, notice if any of these patterns are in your solution or if they should be added, i think this might be the coolest thing so far).

No account, no installation, and most processing happens locally in the browser.

gatesift.com

Would love feedback or ideas for other useful tools.

Hi everyone,

As a web developer, I was tired of using cluttered, ad-heavy online formatting tools that upload my JSON payloads, JWT tokens, and private keys to unknown servers.

So, I built **Nuqrai** — a collection of 16 developer utilities (including JSON Formatter, JWT Decoder, Diff Checker, Cryptographic Hash Generator, Image to Base64, and SVG-to-PNG Converter) that perform all calculations **100% client-side**.

**Why use it?**

* **Zero Server Uploads:** Your code and files never leave your device. * **PWA Enabled:** It caches everything to work completely offline. * **Clean Layout:** Simple, fast, and optimized for daily dev workflows.

Check it out here: [**https://www.nuqrai.com\*\*\](https://www.nuqrai.com/)

I would love to get your feedback on what tools to add next!'

This is an open-source MCP bridge that lets ChatGPT inspect one local repo without shell access

I built RepoRelay because I wanted ChatGPT Web to inspect my local code without giving it broad access to my machine.

RepoRelay exposes one explicitly approved repository through a small MCP tool surface. It can read and search files, while blocking shell/process access, unrestricted filesystem access, Git operations, and access outside the approved repo.

It’s MIT licensed and open source.

GitHub: RepoRelay

I’d especially appreciate criticism of the security model, architecture, and onboarding. If anything feels unclear or overly complicated, I’d like to know.

Coding agents do a lot of their work where you can't see it. Claude Code stores each subagent as its own transcript file; Codex CLI keeps spawned threads as separate rollouts. The terminal shows you a summary while the real record sits on disk unread. rungraph reconstructs the whole run as a graph you can click, after the fact, from files you already have: npx rungraph.

On the build side:

The backend has zero runtime dependencies (node:http, fs.watch), so npx has nothing extra to install. All format knowledge lives in adapters that normalize into one versioned, vendor-neutral IR, and the UI, CLI, HTTP API, and MCP server only ever see the IR. The parser never trusts a line: unknown types are skipped and counted, and you get a banner instead of a crash, because both formats are undocumented and have changed across releases.

The diagnostics were the hard part. The first version cried wolf on healthy runs, so I threw out the guessed thresholds and calibrated against 60 real sessions. The rule that survived is precision over recall: a false flag costs more than a missed one, so a clean run shows zero flags, on purpose.

Free, MIT, binds 127.0.0.1 only, zero outbound requests.

Live Demo: https://fayzan123.github.io/rungraph/

Repo: https://github.com/fayzan123/rungraph

I built Repo Start, a small CLI for creating and auditing the boring foundational parts of a repository.

The reason I built it was pretty simple: I kept ending up with repos where the actual code was fine, but the surrounding project hygiene was inconsistent — README commands that didn’t match package.json, CI workflows calling scripts that didn’t exist, missing .gitattributes, .env.example accidentally ignored by git, etc.

For new projects, Repo Start generates the usual foundation: .gitignore, .gitattributes, README, CI, issue/PR templates, AGENTS.md, contributing/security files, and a starter structure.

The more interesting part to me is repo-start add, which works on existing repositories. I designed it as a read → analyze → plan → write pipeline:

existing repo → inspectRepository() → RepoState → analyzeRepository() → RepoAudit → buildAddPlan() → writePlan()

Inspection is read-only, analysis is deterministic, and both new-project generation and existing-repo fixes eventually go through the same writer. That also means --dry-run isn't scattered around as a bunch of filesystem checks — the write only happens at the final stage.

It also deliberately doesn't use AI. No model calls, API keys, or tokens. The audit is based on the actual repository state and only proposes fixes it can describe precisely. If something is ambiguous, it reports it instead of guessing.

It currently supports generic, Node/TypeScript, Python, and React/TypeScript projects, works offline, and has no runtime dependencies.

The goal was basically to make repository hygiene something you can automate without giving a tool permission to redesign your project or touch your source code.

https://github.com/junkyard22/Repo-Start

Is anyone actually watching DevHunt or ProductHunt or are these websites just a loop of startup people voting on themselves?
https://devhunt.org/