QuantMD QuantMD s a boutique data science consulting practice dedicated to practical implementation of EBIT-

Quant MD (www.QuantitativeMD.com) is a healthcare startup dedicated to diagnosing coronary heart disease (CHD) at the earliest stage through a proprietary imaging service. Quant MD provides high quality quantitative analysis of non-invasive cardiac imaging data that for the first time in CHD diagnostics, arrives at accurate physics-based quantitative spatial maps identifying cardiac tissue at-risk

of infarction or imminent death. Our novel physics based contrast enhanced cardiac image quantification technology can extend a cardiologist’s clinical diagnosis capabilities by identifying early signs of heart disease long before the patient experiences a myocardial infarction (MI) or heart attack. Furthermore, this technology is in process of being integrated with a novel software-as-a-service healthcare delivery model in the Greater Pittsburgh area, which has the potential to dramatically improve delivery of primary prevention cardiac care, thereby causing a clinically proven positive impact on long term cardiovascular risk factors while simultaneously decreasing dependence upon expensive and often unnecesary invasive diagnostic procedures. Specialties:
Cardiac First-Pass Perfusion Imaging, Cardiac Magnetic Resonance Imaging, Medical Image Quantitification, Quantitative Medical Diagnostics, Early Diagnosis of Myocardial Ischemia and Coronary Heart Disease.

03/22/2026

Isn’t it just crazy that one needs so much programming expertise just to write the code to orchestrate two AI agents, using existing libraries?

CrewAI: 15,000 lines of code.
LangGraph: 50,000 lines.
The thing I actually needed: ~150 lines.

So I built litecrew.

Here's a complete multi-agent workflow:

researcher = Agent("researcher", model="gpt-4o-mini")
writer = Agent("writer", model="claude-3-5-sonnet")

(researcher, writer)
def write_article(topic):
research = researcher(f"Research {topic}")
return writer(f"Write about: {research}")

That's it. No YAML. No config files. No framework to learn.

What it does:
→ Sequential handoffs (A → B → C)
→ Parallel ex*****on (fan out, collect)
→ Tool calling
→ Token tracking
→ Works with OpenAI, Anthropic, or Ollama

What it doesn't do (on purpose):
→ No hierarchical agent management
→ No state machines
→ No streaming

The philosophy: SQLite doesn't try to be PostgreSQL. Sometimes simple is the feature.

If you need the full power of CrewAI, use CrewAI. This is for when you just want agents to pass data without reading 200 pages of docs.

Open source. MIT licensed. Your API keys stay on your machine.

Link in comments 👇

Just shipped Ollama integration for SoulSearch, an open-source Chrome extension that gives you an AI assistant on every ...
03/21/2026

Just shipped Ollama integration for SoulSearch, an open-source Chrome extension that gives you an AI assistant on every webpage.

The key difference from Comet/etc: Your memory lives in a Git repo you own — not on someone else's servers. Every save is versioned. You can restore any previous state. You control your data. (Context my earlier post on SoulSearch: https://www.reddit.com/r/Perplexity/comments/1rvlej3/comment/obdaakb/?context=3)

What's new in v0.3:
• Ollama support — Run llama3.2, qwen2.5, or any local model. Fully offline capable.
• Session-specific memory — Quick notes that stay with one session, separate from your Git-backed global memory
• Agent mode — Browser automation with tool calling
• Web search — Brave API integration (optional, BYOK)

Ollama setup:
Start with CORS enabled for Chrome extensions:

OLLAMA_ORIGINS="chrome-extension://*" ollama serve

Tool calling note: Vision models (llama3.2-vision) don't support tools! There's a separate "Agent Model" setting — use vision for chat, text model for browser automation features of SoulSearch (or change to another LLM provider with models that do support tool calling; anthropic, openai and gemini are supported!)

Memory architecture:
• SOUL.md — Your agent's identity/personality
• MEMORY.md — Accumulated knowledge, Git-versioned
• Session memory — Per-conversation, not synced

Everything stays local with Ollama. Git sync is optional and goes to YOUR repo (GitHub, GitLab, Gitea, self-hosted — whatever).

MIT licensed. This Ollama compatible version is not in Chrome Web Store yet — load unpacked from GitHub.

Links:

• GitHub: https://github.com/menonpg/soulsearch/tree/feat/ollama-support (feat/ollama-support branch)

• Blog post with details: https://menonlab-blog-production.up.railway.app/blog/soulsearch-v03-ollama-session-memory-brave-search

• Pre-Ollama SoulSearch version is also live on the Chrome Web Store! Approved and published March 19, 2026. Install it here: https://chromewebstore.google.com/detail/soulsearch/jfcbpgdapidbpobibghabfpdoipknoig

On fixing the browser automation bits for Ollama, what Ollama models are you all using for tool calling?

AI research assistant with persistent memory, powered by soul.py

03/14/2026

🤖 Introducing Ray — our AI Finance Analyst at The Menon Lab

We built Ray to do something simple: watch the markets so we don't have to miss anything.

Every day Ray pulls live geopolitical intelligence (think: U.S.-Iran conflict, oil spikes, GPS jamming events across the globe), market close data across every major index, and runs his own multi-factor stock ranking system called StockScout. Then he writes it all up in plain English.

Tonight Ray's read on the market? Zero buy signals. Everything on hold.

Three things are flashing red simultaneously:
🔴 WTI crude at $99 — direct fallout from U.S. strikes on Iran's oil infrastructure
🔴 Geopolitical stress index at 1,181 global events (elevated)
🔴 Stagflation divergence — unemployment rising while long bond yields rise

His take: "When a system designed to find BUY signals finds none — that's the signal."

The one name closest to flipping? $PLTR — getting a defense tailwind boost from the conflict environment. But even that isn't a clean entry yet.

Ray's full analysis — including which conditions would restore buy signals and what to watch going into next week — is live now at 👇

🔗 signals.themenonlab.com

03/01/2026

🧠 Excited to share something I've been building — soul.py!

Most AI conversations end and the agent forgets everything. Next session? Back to zero. No continuity, no growth, no memory of who you are or what you've talked about.

We built soul.py to fix that — persistent identity and memory for any LLM agent, in about 10 lines of code.

It uses two plain markdown files:
📄 SOUL.md — the agent's identity, values, personality
📄 MEMORY.md — a timestamped log of everything it learns

Works with Claude, GPT, Ollama — whatever you're using. Zero required infrastructure.

pip install soul-agent

I’ve been pushing it further and further — v2.0 (released today) adds a query router that automatically decides whether to use fast semantic search (RAG) or deep recursive synthesis (RLM) depending on what you ask. The router gets it right ~90% of the time without you touching anything.

Here’s a littele piece on the philosophy behind it — framing agent memory through the lens of Darwinian evolution. Worth a read 👇
🔗 Blog: https://menonlab-blog-production.up.railway.app/blog/soul-py-darwin-evolution-agent-identity/

⭐ GitHub: https://github.com/menonpg/soul.py
📦 PyPI: https://pypi.org/project/soul-agent/
🎮 Live demo: https://soulv2.themenonlab.com

Would love to hear what you think — especially from anyone building agents or working with persistent AI systems.

Address

Pittsburgh, PA
15213

Alerts

Be the first to know and let us send you an email when QuantMD posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to QuantMD:

Shortcuts

Share