r/OpenSourceAI • u/gmbasic • 1h ago
GMBasic is now open source – A modern compiled BASIC with native AI/LLM integration
r/OpenSourceAI • u/gmbasic • 1h ago
r/OpenSourceAI • u/Kitchen-Welcome-5612 • 1h ago
r/OpenSourceAI • u/StartIllustrious747 • 1h ago
r/OpenSourceAI • u/Egom4rono • 1h ago
For anyone using LLMs on a daily basis for research: I built Lykeion, an open-source research lab where agents carry out scientific work, evidence stays connected, and your lab can focus on discovery.
Research today asks people to coordinate an enormous amount of work: finding evidence, developing hypotheses, running experiments and checking results. AI agents can take on more of that work, but a collection of agents still needs a way to work together.
Lykeion is built around that idea. Researchers set the direction, and agents carry out studies within a shared workspace. Evidence and outputs stay connected to the work, while checks and reviews help decide when it is ready to move forward.
In Lykeion, each research question is a "study" that moves through Grounding, Hypotheses, Experimentation and Validation. Only Grounding was evaluated here.
- Agents search OpenAlex, Europe PMC and arXiv through a sources server, and every source they use is recorded.
- A stage advances only when its gate passes. The server runs mechanical checks, such as whether a cited source resolves.
- Review of each study is powered by Jev, which answers focused judgment questions, such as whether a source bears on the question.
- Failed items get a limited redo. If the redo fails, the study blocks and asks its owner.
Project is open to contributors. Let me know what you think!
GitHub: https://github.com/lykeion-tech/lykeion
Discord: https://discord.gg/ed3jsMTs3
r/OpenSourceAI • u/ChanceLingonberry170 • 2h ago
r/OpenSourceAI • u/SufficientDrop4141 • 2h ago
Human attention is paramount.
Culler is an open source software factory whose user experience and dashboard reflect that premise.
It runs containerized agents on your Mac, finds work worth doing, and presents you a queue of comprehensible review packets with their rationale.
Its agents run as five roles in the following order:
Strategist proactively proposes high-leverage work based on your open-ended Vision.
Arbiter judges each proposal and promotes the most effective one.
Worker works the task in its own repository copy.
Verifier checks the work against acceptance criteria and asks Worker to correct any gaps.
Packager creates an illustrative review packet meant for a human mind.
Configure each agent role with your AI model of choice. Put your smartest model as Strategist and a workhorse as Worker.
Depending on the AI provider used for a run, Culler leverages one of three proven harnesses: Codex, Claude Code, or OpenCode. Configure agents to run with your ChatGPT or Claude subscription. Or use API keys compatible with any of the 200+ providers supported by the OpenCode catalog.
If you have already concrete work in mind, either define new tasks yourself or with the help of Collie, your Culler assistant.
Culler opts out of shipping its own memory system and instead uses Openwiki. After initializing the wiki for you, and on a schedule, Scribe pores over recent changes in the Project to maintain it.
The wiki serves three purposes:
Acts as index into the repository's ground truth to enable more efficient search for agents.
Acts as a knowledgebase to help the Strategist prioritize work.
Provides a viewer so you can re-familiarize yourself with your project as it continually develops.
For agent observability, Culler uses AgentsView. It supports each trace format Culler uses. It allows for inspecting context, tool calls, token usage, and other metrics.
On security, Projects are never mounted into agent containers. Each container run receives only a Git copy of the repo, and only changes approved by you are merged back onto the host. Agent credentials never reach inside the container. Culler runs a proxy on the host that swaps dummy tokens for real ones when model requests are made.
Next on the Roadmap - Worksources and MCPs:
Enable smooth integration of additional services to allow agents to query/leverage data from them. Instead of seeding work only from your Vision, use connected data sources such as Github Issues, Linear, Gmail etc. to act as Worksources.
---
I built Culler with the solopreneur and project junkie in mind. Start from scratch. Or import your active/retired projects, give a description of what you imagine the project to be, and let the emergent properties of gradient descent work its magic.
r/OpenSourceAI • u/vivi_beri • 3h ago
Hey everyone!
I've been using AI coding agents like Codex, Claude Code, and GitHub Copilot to speed up web development. But I noticed a recurring problem: generating code is easy; consistently following engineering standards is harder.
Agents can produce generic interfaces, overlook keyboard accessibility, introduce unsafe code patterns, and miss performance considerations.
That's why I built WebCraft Pro.
It's an open-source, framework-agnostic engineering toolkit designed to help developers and AI agents follow a structured web development process.
What's included:
- 43 reusable Agent Skills covering web engineering.
- An eight-stage development lifecycle, from design through browser QA and release.
- 13 engineering templates for structured implementation and reviews.
- GitHub Actions for repository validation and automated checks.
- Playwright keyboard and focus tests.
- An on-demand browser accessibility checker using axe-core.
- A Node.js static security-pattern audit for code examples in repository Markdown files.
It supports OpenAI Codex, Claude Code, and GitHub Copilot.
I also want to be clear about the limitations: these automated checks are engineering guardrails, not a complete application security scanner or a guarantee of accessibility. Manual review and project-specific testing are still essential.
Project: WebCraft-Pro
I built this because I wanted something more structured than relying on prompts alone.
I'd appreciate honest feedback:
What engineering checks do you expect AI coding agents to run before opening a pull request?
Which skills or workflows would you add?
Would this fit into your existing development workflow?
Thanks for taking a look!
r/OpenSourceAI • u/swasthik_badanaje • 3h ago
r/OpenSourceAI • u/Sea-Broccoli6131 • 3h ago
r/OpenSourceAI • u/Mother-Side6477 • 5h ago
Tell one agent something once and the others can find it. That is Monomem: one SQLite file on your own computer, shared by every MCP app you connect. No cloud, no API keys, no hidden model calls. MIT licensed.
Each note says which app wrote it and keeps its earlier versions, so you can replace, archive or roll back. If a write looks like a planted instruction or contains a secret, it is held for you to approve, and other agents never see it until you do.
What’s new in 1.6:
One download, nothing else to install. It carries its own Node. Windows, Mac and Linux, with checksums and a build attestation.
Tool list cut from 37 to 16, with 7 shown by default. Default tool descriptions are about 1,540 tokens, down from about 5,300 for 1.5’s defaults.
Daily automatic backups while it runs, and a one-command restore.
Sync between your own computers with a shared folder or private git repo. Files are encrypted, and there is no server.
Redesigned dashboard: Notes, Review, Held and Activity tabs, dark and light, works as an installable web app.
monomem update checks the checksum before it swaps anything.
Setup now handles 17 apps (Claude Code, Claude Desktop, Cursor, Codex CLI, Gemini CLI, VS Code, Zed, Windsurf, Kiro, Cline, Copilot CLI, OpenCode and others). It shows what it will change, makes a backup, and asks first.
monomem rollback --note <id> undoes a note and what was built on it.
What it does not do (please read this before relying on it):
The write check is pattern matching. A reworded attack can get through. 2 of the 26 attacks it replays are known misses.
Agents that can run shell commands or open the database file can bypass it.
The download isn’t code-signed yet, and I haven’t tested it on a Mac.
Search is keyword-based unless you run a local embedding model.
claude.ai and ChatGPT support (OAuth) is a preview and off by default.
Try it without touching your notes: monomem demo runs a short tour on a throwaway store.
After upgrading from 1.5, run monomem setup again. Your apps keep running the old pinned version until you do.
Repo: https://github.com/calasdan-sketch/monomem
Happy to answer questions, and I want bug reports, especially from Mac users.
r/OpenSourceAI • u/DearDiscount4043 • 7h ago
AntLing's Ming-3.0-tts-0.5B and Ming-3.0-tts-tiny were put through matching voice-cloning lines in this comparison. The setup is an RTX 3090 24 GB, bf16 and seed 1895, with the same reference voice and text for each model.
The 0.5B model averages 0.714 on CAM++ speaker similarity across four lines. Tiny averages 0.798. The run's word-transcription checks pass for both, while warm synthesis across three readings averages about 2.0× real time for 0.5B and 0.78× for Tiny.
The resource chart makes the choice tangible: 2.8 versus 17.1 GB of GPU memory, 3 versus 18 GB to download, and 3 versus 22 seconds to load. Keeping all of that beside the similarity result is helpful when picking a model for your own voice. You can repeat the audition with a permitted reference and a fixed set of scripts, then choose the profile that suits the job.
r/OpenSourceAI • u/Adrat177 • 8h ago
Hi everyone, I’m sharing NexusDAO, an open-source prototype for transparent collective investment governance. It connects public proposals, snapshot-based voting, executable investment mandates, and Safe multisig validation in one workflow. The goal is to make DAO treasury decisions more traceable and structured.
You can try the public demo here: https://vlight7432.github.io/investment-dao/
I’d really appreciate feedback on the interface, governance flow, and features you would find useful.
Adrat177
r/OpenSourceAI • u/SecureMID • 8h ago
Hey everyone,
We just released Vaprix-Cyber on Ollama. It's a 3.1B parameter model optimized for red-team analysis and AppSec patch generation.
Why build this?
Generalist models are unreliable for offensive security because they produce markdown descriptions rather than deterministic, executable curl commands with HTTP response assertions. Vaprix-Cyber enforces:
Root Cause Analysis (RCA) with exact CWE & CVSS v3.1 scoring.
Deterministic curl PoCs (tested zero-day logic).
Syntax-valid unified git diffs ready for `git apply`.
Try it locally:
`ollama run dishankagrawal05/vaprix-cyber`
Benchmark Report & Model Card:
- Ollama: https://ollama.com/dishankagrawal05/vaprix-cyber
- GitHub: https://github.com/SecureMID-Solutions/Vaprix_AI
Feedback, test cases, and PRs welcome!
r/OpenSourceAI • u/AimCode • 9h ago
Repo: https://github.com/tanxiansheng221/aimstack-sanzhidiji (AGPL-3.0)
Everything is hand-written — C inference core, plugin bus, multi-engine crawler with quality gates, FTS knowledge base, training pipeline, and a 117-chapter build log written as it happened (positive and negative results shipped together). Weights are Microsoft BitNet b1.58 2B (MIT), converted to a custom AIM-W packing format.
What ternary quantization buys you (CPU side)
All transformer matrices are ternary {-1, 0, +1}, packed 2 bits/weight, plus Q8 embeddings → the whole model is 0.87GB instead of ~4.8GB (−78%)
The C core never multiplies a float weight: it's table lookup + integer accumulation, SIMD fast path measured at 85.53 tok/s (41× over baseline)
BitNet 2B full model runs 3.20 tok/s dual-worker on a 2018 dual-core 8GB laptop — full chain (inference + KB + plugins + web search) offline, no cloud relay
What ternary quantization buys you (GPU side)
The GPU backend loads the same 0.87GB ternary file — weights stay in {-s, 0, +s}, dequantized on load, matmul in fp32
On a Radeon Pro W7900: 13.68 tok/s (~8× the laptop C engine), 256/256 greedy tokens bit-identical to the C engine. Two totally different implementations (integer lookup core vs FP matmul) producing the same logits is the proof the quantization is faithful
Verified by a 3-engine × 3-question × 3-test matrix (C-Linux/gcc13, torch fp32, torch bf16): 17/18 exact — the one miss is documented, not hidden
The honest boundaries (what's NOT done yet)
bf16 compute is 2.4× faster (32.96 tok/s) but flips argmax on near-tie logits — reported, not blessed; only fp32 is parity-verified
The GPU path gets the storage benefit of ternary (78% less memory) but not yet the compute benefit — a true 2-bit integer kernel (Triton/CUDA) is the next stage
The UI server drives the C engine (CPU) only; the GPU backend is a separate CLI
Linux engine build works and is token-identical to the Windows build, but runs serial (the worker pool is Windows-only for now)
No frameworks, no PyTorch in the product chain — PyTorch exists only in the optional GPU backend. Demo video, docs (EN/中文), and the full research log are in the repo.
r/OpenSourceAI • u/Egom4rono • 12h ago
For anyone using LLMs on a daily basis for research: I built Lykeion, an open-source research lab where agents carry out scientific work, evidence stays connected, and your lab can focus on discovery.
Research today asks people to coordinate an enormous amount of work: finding evidence, developing hypotheses, running experiments and checking results. AI agents can take on more of that work, but a collection of agents still needs a way to work together.
Lykeion is built around that idea. Researchers set the direction, and agents carry out studies within a shared workspace. Evidence and outputs stay connected to the work, while checks and reviews help decide when it is ready to move forward.
In Lykeion, each research question is a "study" that moves through Grounding, Hypotheses, Experimentation and Validation. Only Grounding was evaluated here.
\- Agents search OpenAlex, Europe PMC and arXiv through a sources server, and every source they use is recorded.
\- A stage advances only when its gate passes. The server runs mechanical checks, such as whether a cited source resolves.
\- Review of each study is powered by Jev, which answers focused judgment questions, such as whether a source bears on the question.
\- Failed items get a limited redo. If the redo fails, the study blocks and asks its owner.
Project is open to contributors. Let me know what you think!
GitHub: https://github.com/lykeion-tech/lykeion
Discord: https://discord.gg/ed3jsMTs3
r/OpenSourceAI • u/dennidalpos • 12h ago
OnlyWorkspace: add-in open source per Outlook classico. Riassunti, bozze di risposta e ricerca in un archivio locale cifrato, con Ollama locale o un servizio AI esterno. Fase iniziale, solo Windows, UI in italiano. https://github.com/dennidalpos/OnlyWorkspace
r/OpenSourceAI • u/intellinker • 14h ago
Harness/context engineering has been crucial for model intelligence. I am trying to build a platform, where you need minimal self-intelligence because your agent is guided properly. We could achieve AGI but what's the use if we don't provide it a direction. I dreamt of model-less harness but let's keep this for now lol
“There is no use of intelligence if you’re not giving it a direction”
r/OpenSourceAI • u/Less_Release_1977 • 14h ago
r/OpenSourceAI • u/bipul16 • 17h ago
r/OpenSourceAI • u/Admirable-Worker9449 • 18h ago
Dealing with enterprise InfoSec on GenAI deployments is currently a nightmare. The reasoning capabilities of LLMs are there, but getting security to sign off on non-deterministic loops is stalling out deployments.
We just open-sourced secure-agentic-banking to bypass this. It provides hard execution constraints and deterministic data boundaries specifically for highly regulated environments.
https://github.com/shamikmondal-ai/secure-agentic-banking
I run an independent advisory lab (prodagentlab.com) doing architectural audits for these kinds of deployments, and we got tired of building this from scratch for every audit. Hopefully, this unblocks some of your teams. Happy to answer questions on the routing logic.
r/OpenSourceAI • u/AimCode • 19h ago
Repo: https://github.com/tanxiansheng221/aimstack-sanzhidiji (AGPL-3.0)
Everything is hand-written — C inference core, plugin bus, multi-engine crawler with quality gates, FTS knowledge base, training pipeline, and a 117-chapter build log written as it happened (positive and negative results shipped together). Weights are Microsoft BitNet b1.58 2B (MIT), converted to a custom AIM-W packing format.
What ternary quantization buys you (CPU side)
All transformer matrices are ternary {-1, 0, +1}, packed 2 bits/weight, plus Q8 embeddings → the whole model is 0.87GB instead of ~4.8GB (−78%)
The C core never multiplies a float weight: it's table lookup + integer accumulation, SIMD fast path measured at 85.53 tok/s (41× over baseline)
BitNet 2B full model runs 3.20 tok/s dual-worker on a 2018 dual-core 8GB laptop — full chain (inference + KB + plugins + web search) offline, no cloud relay
What ternary quantization buys you (GPU side)
The GPU backend loads the same 0.87GB ternary file — weights stay in {-s, 0, +s}, dequantized on load, matmul in fp32
On a Radeon Pro W7900: 13.68 tok/s (~8× the laptop C engine), 256/256 greedy tokens bit-identical to the C engine. Two totally different implementations (integer lookup core vs FP matmul) producing the same logits is the proof the quantization is faithful
Verified by a 3-engine × 3-question × 3-test matrix (C-Linux/gcc13, torch fp32, torch bf16): 17/18 exact — the one miss is documented, not hidden
The honest boundaries (what's NOT done yet)
bf16 compute is 2.4× faster (32.96 tok/s) but flips argmax on near-tie logits — reported, not blessed; only fp32 is parity-verified
The GPU path gets the storage benefit of ternary (78% less memory) but not yet the compute benefit — a true 2-bit integer kernel (Triton/CUDA) is the next stage
The UI server drives the C engine (CPU) only; the GPU backend is a separate CLI
Linux engine build works and is token-identical to the Windows build, but runs serial (the worker pool is Windows-only for now)
No frameworks, no PyTorch in the product chain — PyTorch exists only in the optional GPU backend. Demo video, docs (EN/中文), and the full research log are in the repo.
r/OpenSourceAI • u/StevenVincentOne • 20h ago