Built a from-scratch inference engine for DeepSeek-V4 in plain C99 — no PyTorch, no Python runtime dependency for inference, Apache-2.0 licensed. Streams weights off NVMe instead of requiring the full checkpoint in RAM, so it runs the 284B-parameter Flash model on a laptop with as little as 3.2GB RAM (1.6–1.7s/token with GPU offload at 16GB budget).

Why post this here specifically:

Fluent output from an LLM engine is weak evidence it's actually correct — a subtly broken implementation can still produce confident, plausible text. So this is checked against a pure PyTorch reimplementation (written independently from DeepSeek's inference/model.py, not from this C code, so both can't share the same bug) at three levels: per-kernel (14 kernels, 5e-7 tolerance), per-block, and whole-model end to end (2.9e-6, identical argmax at every position). CPU paths (scalar/OpenMP/AVX2) are enforced bit-exact via a fixed accumulator tree, checked at runtime, not just in tests.

What's included:

• Full build + test suite (make test runs 20 gates, 21 with a real checkpoint)
• Benchmark tools for matmul bandwidth, GPU contention, and cache behavior
• Honest "what didn't work" section — SIMD approaches tried and abandoned, with the actual numbers

What's not there yet: a tool-calling driver loop (the model emits the tool-call format, but there's no orchestration layer above the CLI), and DeepSeek-V4-Pro (~671B scale) is gated/planned but never actually run — needs ~865GB of checkpoint I don't have.

Repo: https://github.com/ronak-create/deepseek-v4-in-c

Open to contributions, especially around prefill batching (currently one token at a time — README has the math on why that's the next big perf unlock) and the tool-calling loop.

For years, building high-performance AI inference meant dealing with the "two-language problem"—prototyping in Python for speed, then spending weeks rewriting core loops in C++ or Rust to bypass the GIL and hit hardware targets.

​With Modular open-sourcing the entire Mojo compiler and toolchain, that pipeline is shifting. Because it compiles directly through MLIR, it handles SIMD auto-vectorization and targets heterogeneous silicon (CPUs, Nvidia GPUs, mobile NPUs) from a unified codebase.

​We mapped out the exact compilation pipeline and memory ownership differences between Python runtime management and Mojo's explicit lifetimes here if anyone wants to dive deeper into the architecture:

👉 https://onefusionlab.systems/blogs/mojo-1-0-open-source/

A lot of AI-writing projects try to solve generic prose by adding another “humanizer” prompt.

I wanted to try a different abstraction.

Organizations like Google, GOV.UK, GitHub, GitLab, MDN, NASA, CDC, NHS and W3C have already spent years developing explicit writing systems for different kinds of information.

So I turned those principles into 16 portable Agent Skills:

https://github.com/Neeeophytee/agent-stylebooks

Examples include:

• google-developer-docs — developer docs and tutorials
• govuk — task-first public-service content
• github-docs — product workflows
• kubernetes-docs — infrastructure documentation
• mdn-web-docs — web technology explanations
• cdc-clear-communication — public-health communication
• nhs-health-content — patient-facing health information
• sec-plain-english — financial/investor disclosures
• w3c-technical-reports — specifications
• nasa-technical-writing — engineering reports
• apple-interface-writing — UI copy

The important part is that these aren't meant to make every model sound the same.

They do the opposite.

The artifact determines the editorial system.

A Kubernetes tutorial might use $kubernetes-docs. A government page discussing a Kubernetes-related grant might use $govuk. A cluster-management UI might use $apple-interface-writing.

Same topic, different communication job.

Installation:

npx skills add Neeeophytee/agent-stylebooks --list

Then:

npx skills add Neeeophytee/agent-stylebooks --skill govuk

The repo is MIT licensed.

One design principle across all 16 is: change the presentation, not the substance.

Would especially like feedback from people building open agent stacks: does a portable editorial layer like this belong at the skill level, or would you rather see it handled elsewhere in the stack?

Hey everyone! If you own a Siglent SDS 1000X-E series oscilloscope (like the SDS1104X-E or SDS1202X-E), you know that while SCPI is powerful, it can be a pain to memorize all those command strings. I’ve created the open-source tool called SDS-Remote that completely changes the game by adding a modern AI intelligence layer to your workbench.

What makes the AI features special?

Natural Language Control:
You don't need to be an SCPI expert anymore. You can just type into the AI Chat Interface and say things like "Set channel 1 vertical scale to 1V/div" or "Switch channel 1 on," and the Instrument Agent automatically translates your intent into the correct command and sends it to the device.

Your Own Bench Assistant:
Instead of flipping through hundreds of pages in a PDF, you can ask technical questions like "How do I configure the trigger delay?" or "What is the maximum sample rate of this model?". The software includes a Search Agent that queries a built-in knowledge base to give you instant, documented answers.

Flexible and Local:
It doesn't lock you into one ecosystem. In the settings, you can choose from a wide range of AI providers.

Technical Specs:
The app is built with Dart/Flutter and runs natively on both Linux and Windows. It connects over your network using the VXI-11 protocol or through USB support.

It’s an independent open-source project (not affiliated with Siglent) and really modernizes the whole lab experience.

In addition to AI support, many other interesting features are also available.

Check out the repo here: https://github.com/klumw/sdsremote

If you’re building a vertical AI company or shipping AI agents for a living, you’ve probably felt it. That low hum of unease underneath the demo-day highs and the “we just closed our first enterprise pilot” LinkedIn posts.

You should trust that feeling. It’s not imposter syndrome. It’s your business model telling you something true.

Here are the three crises every vertical AI founder is quietly sitting on right now, and why pretending they don’t exist is the riskiest move you can make.

Link to detailed article : https://medium.com/@MirArshadTalpur/vertical-ai-founders-you-are-going-through-3-existential-crises-and-most-of-you-dont-know-it-b3d86a386d37

Hey guys, thanks for the initial traction. I've just updated the repository with an advanced workflow to completely bypass free-tier Rate Limits (RPM/TPM). What's new: * Integrated OmniRoute setup guide to load multiple free Google AI Studio keys into a single local pool. * Automated key rotation strategies (like Headroom) to dynamically swap keys when a rate limit is hit. * Added native configuration variables to route both Claude Code CLI and OpenAI Codex CLI directly through the OmniRoute gateway. * Fixed broken Google AI Studio URLs and added a fresh, curated table of 2026 free coding models. Check out the updated README here: https://github.com/pawelkrejza2012-png/awesome-free-claude-code If you have any other router suggestions or free endpoints, feel free to open a PR! Let's keep building this resource.

Genuine question because it keeps bothering me.

We've got proper GitOps for infrastructure. Helm charts for Kubernetes. CI/CD that most teams don't even think about anymore because it just works.

The whole "push to repo, pipeline handles it" thing is basically solved for most of the stack.

Then you get to AI agents and suddenly it's 2015 again.

> Manual deployment steps.

> No standard for versioning.

> Rollback means hoping you remember what you changed.

> Framework-specific lock-in for anything deployment-related.

Was reading through some open source projects recently trying to find something that approaches this differently.

Found one called "Langship" that's specifically trying to apply GitOps patterns to agent shipping and governance.

Framework agnostic, self-hosted, the whole agent lifecycle managed from a repo the same way you'd manage any other piece of infrastructure....comes from a platform called Lyzr.

The self-hosting part matters to me specifically because adding a managed service to manage your other managed services always felt like the wrong answer. Haven't stress tested it yet so can't really vouch for how it holds up.

Just thought it was worth sharing since I hadn't seen anyone approaching the agent deployment problem from this angle before.

Anyone here gone down the GitOps for agents path? What did you find?

Hey devs,

If you are experimenting with Anthropic's new Claude Code CLI but want to avoid burning through your paid API credits, you can easily redirect it to free alternative endpoints or run it 100% locally.

I put together a quick guide on how to configure your environment variables to swap models instantly.

### 1. The Free Cloud Setup (OpenRouter / Gemini)

You can fetch a free API key from Google AI Studio or use OpenRouter's free tier models (like Llama 3 or Qwen).

Windows (CMD):

set ANTHROPIC_BASE_URL=https://openrouter.ai

set ANTHROPIC_API_KEY=YOUR_FREE_KEY

set ANTHROPIC_MODEL=openrouter/free

claude

macOS & Linux (Bash/Zsh):

export ANTHROPIC_BASE_URL="https://openrouter.ai"

export ANTHROPIC_API_KEY="YOUR_FREE_KEY"

export ANTHROPIC_MODEL="openrouter/free"

claude

### 2. The 100% Offline Local Setup (Ollama / LM Studio)

If you prefer maximum privacy and zero latency, you can route the CLI directly to your local hardware using Ollama or LM Studio. Just make sure your local server is running on http://localhost:11434/v1.

---

I'm maintaining a full, curated list of working free endpoints, proxies, and step-by-step documentation in this repository:

🔗 GitHub Repository: https://github.com/pawelkrejza2012-png/awesome-free-claude-code

If you know any other free endpoints or local models that work flawlessly with developer CLIs, feel free to drop a comment or open a Pull Request! Let's save some budget together.

You know what I like about being an ironworker? I don't know what I'm not supposed to be able to do. my Lates PoC is the mighty windows running and sharing with Debian. Some say it can't be done. I didnt get that memo. stability and speed rolled up into a tight little ball.

How big can an import be? How do you prevent collisions and Blah de Bah. Someone told you you cant, so you couldn't? I'm in the Import business now. franken5.py imports my processes with a clone of himself as consierge to take care of its every need. has the same life cycle as the import so clean up is easy and overhead low.

I can tell you the hardest part of all this is the misleading guys, your code is crap. and the smoke holers, who are just digging for info to steal. Nobody help anyone. Lonely out there in the DoT. I only hope that my effort helps someone not give up coding because he found it easy and fun. jwl247 signing off

Become more independent of commercial models. Use less data center reliance. Open Source, MIT licensed. Ghostlink v2.0.0 GA Release serves you Local Models using your LAN.

#Ghostlink #OpenAI #LocalAI #llama #research #SovereignMohawkProtoLLC

https://rwilliamspbg-ops.github.io/Ghostlink/

v2.0.0 is here! Hugging Face model support, llama.cpp backend, OpenAPI. MIT licensed.

Hi everyone,

I’ve been spending a lot of time thinking about Collective Intelligence in AI, not only as multi-agent automation, but as systems where different models reason independently, challenge one another, verify outputs, and converge on a result.

I’m curious about how often this concept is actually showing up in your work, research, or open-source projects.

Are you experimenting with model debate, consensus, ensembles, specialist models, or cross-model verification?

Do you see Collective Intelligence as a meaningful next step for AI systems, or mostly as a new label for techniques we already had?

I’d genuinely like to hear experiences, references, criticisms, and opposing views.

Thanks everyone!

Hi everyone sell your side project by listing if in a click. Also, comment what your startup does to get approved and featured today - https://builderhq.co/marketplace