nomic-ai/nomic-embed-text-v1.5
Sentence Similarity
•
0.1B
•
Updated
•
3M
•
747
Alexander
AlexanderKyng
Benson's profile picture
DualityAI-RebekahBogdanoff's profile picture
Amazing-Productions's profile picture
·
AI & ML interests
Deeply passionate in all things AI. Junior Data Scientist.
Recent Activity
liked
a model
12 days ago
nomic-ai/nomic-embed-text-v1.5
updated
a model
19 days ago
AlexanderKyng/Devstral-Small-2-24B-Instruct-2512-exl3-4.5bpw-optimized
Organizations
None yet
liked
a
model
12 days ago
Missing file preprocessor_config.json?
2
#1 opened 17 days ago
by
atisharma
updated
a
model
19 days ago
published
a
model
19 days ago
liked
a
model
19 days ago
liked
a
model
21 days ago
reacted to
Kseniase's
post with ❤️
28 days ago
Post
6225
9 Recent advances in Multi-Agent Systems (all open-source)
The idea to split tasks across multiple agents instead of relying on one universal agent is now seen as one of the most effective ways to build an AI stack. Concepts like “agent swarms” were highlighted at the AI Engineer Code Summit in NYC (Nov 20–21) as the winning architecture. And this trend is not only about coding and software. It applies across all AI domains.
So here is some recent research that helps keep multi-agent systems (MAS) better and up-to-date:
1. LatentMAS → Latent Collaboration in Multi-Agent Systems (2511.20639)
AI agents share their hidden "thoughts" directly in latent space instead of talking through text. This makes collaboration and reasoning way faster and accurate (no extra training needed)
2. Puppeteer → Multi-Agent Collaboration via Evolving Orchestration (2505.19591)
Uses a “puppeteer” LLM that dynamically decides which agents (“puppets”) to call and in what order. By learning this orchestration with reinforcement learning (RL), the system solves complex tasks more efficiently and with fewer compute costs
3. MADD → MADD: Multi-Agent Drug Discovery Orchestra (2511.08217)
A MAS with 4 agents for drug discovery. It lets researchers describe a drug discovery task in plain language. Then MADD automatically builds and runs the full hit-identification pipeline, making AI-driven drug design a simple end-to-end workflow
4. Multi-Agent Tool-Integrated Policy Optimization (MATPO) → Multi-Agent Tool-Integrated Policy Optimization (2510.04678)
Lets one LLM act as multiple agents (like a planner and a worker) by using different prompts and training them together with RL. So you get the benefits of a multi-agent system without needing multiple models
If you're interested in trends in multi-agent for software development of the future, explore my article with the emergent playbook. This is super interesting → https://www.turingpost.com/p/aisoftwarestack
Also, subscribe to the Turing Post: https://www.turingpost.com/subscribe
Read further below ⬇️
The idea to split tasks across multiple agents instead of relying on one universal agent is now seen as one of the most effective ways to build an AI stack. Concepts like “agent swarms” were highlighted at the AI Engineer Code Summit in NYC (Nov 20–21) as the winning architecture. And this trend is not only about coding and software. It applies across all AI domains.
So here is some recent research that helps keep multi-agent systems (MAS) better and up-to-date:
1. LatentMAS → Latent Collaboration in Multi-Agent Systems (2511.20639)
AI agents share their hidden "thoughts" directly in latent space instead of talking through text. This makes collaboration and reasoning way faster and accurate (no extra training needed)
2. Puppeteer → Multi-Agent Collaboration via Evolving Orchestration (2505.19591)
Uses a “puppeteer” LLM that dynamically decides which agents (“puppets”) to call and in what order. By learning this orchestration with reinforcement learning (RL), the system solves complex tasks more efficiently and with fewer compute costs
3. MADD → MADD: Multi-Agent Drug Discovery Orchestra (2511.08217)
A MAS with 4 agents for drug discovery. It lets researchers describe a drug discovery task in plain language. Then MADD automatically builds and runs the full hit-identification pipeline, making AI-driven drug design a simple end-to-end workflow
4. Multi-Agent Tool-Integrated Policy Optimization (MATPO) → Multi-Agent Tool-Integrated Policy Optimization (2510.04678)
Lets one LLM act as multiple agents (like a planner and a worker) by using different prompts and training them together with RL. So you get the benefits of a multi-agent system without needing multiple models
If you're interested in trends in multi-agent for software development of the future, explore my article with the emergent playbook. This is super interesting → https://www.turingpost.com/p/aisoftwarestack
Also, subscribe to the Turing Post: https://www.turingpost.com/subscribe
Read further below ⬇️
- 2 replies
liked
3
models
about 1 month ago
updated
a
model
about 1 month ago
published
a
model
about 1 month ago
liked
a
model
about 1 month ago
reacted to
TravisMuhlestein's
post with 🔥
about 2 months ago
Post
1403
Building Smarter AI Agents: A Tool-Based Architecture for Modularity and Trust
Over the past year, our AI engineering team at GoDaddy has been rethinking how to make agent systems more modular, transparent, and production-ready. Instead of viewing an AI agent as a monolithic process, we’ve decomposed it into four core tools that separate decision-making from execution — a design that’s proving critical for scale and observability:
🧩 MemoryTool – maintains persistent context and user continuity
✅ CompletionTool – determines when a task is truly complete
💬 UserInteractionTool – manages clarifications, approvals, and confirmations
🔁 DelegationTool – enables agents to hand off tasks to other agents or humans
This approach makes every step of an agent’s workflow explicit, testable, and auditable, allowing us to scale AI systems in production with higher confidence. We see this as a step toward a more open, composable agent ecosystem — one where frameworks can interoperate and agents can build trust through transparency and version control.
Read the full write-up here → Building AI Agents at GoDaddy – An Agent’s Toolkit https://www.godaddy.com/resources/news/building-ai-agents-at-godaddy-an-agents-toolkit
We’d love to collaborate and exchange ideas with the community:
- How are you designing modular agent architectures?
- What design patterns or abstractions have helped you manage agent complexity?
Let’s build smarter, safer agents together.
#AI #Agents #Architecture #MachineLearning #OpenSource #AgentFrameworks #TrustInAI
Over the past year, our AI engineering team at GoDaddy has been rethinking how to make agent systems more modular, transparent, and production-ready. Instead of viewing an AI agent as a monolithic process, we’ve decomposed it into four core tools that separate decision-making from execution — a design that’s proving critical for scale and observability:
🧩 MemoryTool – maintains persistent context and user continuity
✅ CompletionTool – determines when a task is truly complete
💬 UserInteractionTool – manages clarifications, approvals, and confirmations
🔁 DelegationTool – enables agents to hand off tasks to other agents or humans
This approach makes every step of an agent’s workflow explicit, testable, and auditable, allowing us to scale AI systems in production with higher confidence. We see this as a step toward a more open, composable agent ecosystem — one where frameworks can interoperate and agents can build trust through transparency and version control.
Read the full write-up here → Building AI Agents at GoDaddy – An Agent’s Toolkit https://www.godaddy.com/resources/news/building-ai-agents-at-godaddy-an-agents-toolkit
We’d love to collaborate and exchange ideas with the community:
- How are you designing modular agent architectures?
- What design patterns or abstractions have helped you manage agent complexity?
Let’s build smarter, safer agents together.
#AI #Agents #Architecture #MachineLearning #OpenSource #AgentFrameworks #TrustInAI
reacted to
mike-ravkine's
post with 🔥
about 2 months ago
Post
2770
There is no anxiety quite like powering up 2KW of basement compute after rewiring it all. Small bit of trouble with the horizontal 3090 because I misread my motherboard manual, but otherwise so far so good.. Next we see if I've built up enough cooling to hit my target TDP on those 3-slot nvlinked cards especially. The 4-slot bridges are much easier to work with but their prices went bananas and I couldn't acquire a second, so gotta get a little creative with intakes.
- 5 replies
reacted to
codelion's
post with 🔥
about 2 months ago
Post
3607
On this day in 2019, OpenAI released the final GPT-2 model as part of their staged release. I still remember that November well - so much was happening, but GPT-2's release felt like a watershed moment for the field. It showed us what was possible with carefully trained language models.
To recreate some of that GPT-2 magic, I recently tackled an interesting challenge: can you pretrain a language model with just 1 billion tokens - roughly 1/10th of what GPT-2 used - and still get comparable performance? After 50+ systematic experiments testing different dataset mixtures, the answer is yes.
The result is codelion/gpt-2-70m, which achieves over 90% of GPT-2's benchmark performance despite being trained on 10x less data. The key was finding the optimal dataset composition: 50% high-quality textbook PDFs, 30% filtered web content, and 20% educational resources. It even beats GPT-2 on TruthfulQA (47.31% vs 40.69%).
If you're interested in the full story of how we discovered this optimal mixture and why curriculum learning catastrophically failed, check out the complete article: https://huggingface.co/blog/codelion/optimal-dataset-mixing
Sometimes less really is more - when you mix it right.
To recreate some of that GPT-2 magic, I recently tackled an interesting challenge: can you pretrain a language model with just 1 billion tokens - roughly 1/10th of what GPT-2 used - and still get comparable performance? After 50+ systematic experiments testing different dataset mixtures, the answer is yes.
The result is codelion/gpt-2-70m, which achieves over 90% of GPT-2's benchmark performance despite being trained on 10x less data. The key was finding the optimal dataset composition: 50% high-quality textbook PDFs, 30% filtered web content, and 20% educational resources. It even beats GPT-2 on TruthfulQA (47.31% vs 40.69%).
If you're interested in the full story of how we discovered this optimal mixture and why curriculum learning catastrophically failed, check out the complete article: https://huggingface.co/blog/codelion/optimal-dataset-mixing
Sometimes less really is more - when you mix it right.
- 1 reply
reacted to
abidlabs's
post with 👍
about 2 months ago
Post
8748
Why I think local, open-source models will eventually win.
The most useful AI applications are moving toward multi-turn agentic behavior: systems that take hundreds or even thousands of iterative steps to complete a task, e.g. Claude Code, computer-control agents that click, type, and test repeatedly.
In these cases, the power of the model is not how smart it is per token, but in how quickly it can interact with its environment and tools across many steps. In that regime, model quality becomes secondary to latency.
An open-source model that can call tools quickly, check that the right thing was clicked, or verify that a code change actually passes tests can easily outperform a slightly “smarter” closed model that has to make remote API calls for every move.
Eventually, the balance tips: it becomes impractical for an agent to rely on remote inference for every micro-action. Just as no one would tolerate a keyboard that required a network request per keystroke, users won’t accept agent workflows bottlenecked by latency. All devices will ship with local, open-source models that are “good enough” and the expectation will shift toward everything running locally. It’ll happen sooner than most people think.
The most useful AI applications are moving toward multi-turn agentic behavior: systems that take hundreds or even thousands of iterative steps to complete a task, e.g. Claude Code, computer-control agents that click, type, and test repeatedly.
In these cases, the power of the model is not how smart it is per token, but in how quickly it can interact with its environment and tools across many steps. In that regime, model quality becomes secondary to latency.
An open-source model that can call tools quickly, check that the right thing was clicked, or verify that a code change actually passes tests can easily outperform a slightly “smarter” closed model that has to make remote API calls for every move.
Eventually, the balance tips: it becomes impractical for an agent to rely on remote inference for every micro-action. Just as no one would tolerate a keyboard that required a network request per keystroke, users won’t accept agent workflows bottlenecked by latency. All devices will ship with local, open-source models that are “good enough” and the expectation will shift toward everything running locally. It’ll happen sooner than most people think.
- 8 replies
reacted to
nouamanetazi's
post with 🤗
about 2 months ago
Post
4132
After training 𝐒𝐦𝐨𝐥𝐋𝐌𝟑 on 𝟑𝟖𝟒 𝐇𝟏𝟎𝟎𝐬 for nearly a month, I've come to realize something most people overlook: 𝐢𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐢𝐬 𝐭𝐡𝐞 𝐦𝐚𝐤𝐞-𝐨𝐫-𝐛𝐫𝐞𝐚𝐤 𝐟𝐚𝐜𝐭𝐨𝐫 𝐢𝐧 𝐋𝐋𝐌 𝐭𝐫𝐚𝐢𝐧𝐢𝐧𝐠. 🔥
Everyone talks about model architecture and data quality. And yes, those matter immensely. But here's what nobody tells you: when your training run fails at 2 AM because of mysterious 𝐍𝐂𝐂𝐋 𝐞𝐫𝐫𝐨𝐫𝐬, or when your expensive GPU cluster is running at 𝟔𝟎% 𝐞𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐜𝐲, the problem isn't your model. It's most probably a 𝐦𝐢𝐬𝐮𝐬𝐞 𝐨𝐟 𝐭𝐡𝐞 𝐡𝐚𝐫𝐝𝐰𝐚𝐫𝐞. 🛠️
Questions that seemed simple but had no clear answers: Why is 𝐌𝐨𝐄 𝐭𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐬𝐥𝐨𝐰𝐞𝐫 𝐭𝐡𝐚𝐧 𝐝𝐞𝐧𝐬𝐞 𝐦𝐨𝐝𝐞𝐥𝐬? Which 𝐍𝐂𝐂𝐋 𝐟𝐥𝐚𝐠𝐬 should we actually set? How often should we checkpoint without killing throughput?
That's why we built 𝐓𝐡𝐞 𝐒𝐦𝐨𝐥 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐏𝐥𝐚𝐲𝐛𝐨𝐨𝐤 📖: a complete guide covering everything from model architecture and data curation to the SmolLM3 training marathon, post-training techniques, and crucially, the 𝐢𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐥𝐚𝐲𝐞𝐫 that most teams get wrong.
We validated real vs theoretical bandwidth across the entire stack: 𝐇𝐁𝐌𝟑 𝐡𝐢𝐭𝐭𝐢𝐧𝐠 𝟑 𝐓𝐁/𝐬, 𝐍𝐕𝐋𝐢𝐧𝐤 𝟒.𝟎 𝐫𝐞𝐚𝐜𝐡𝐢𝐧𝐠 𝟕𝟖𝟔 𝐆𝐁/𝐬, 𝐏𝐂𝐈𝐞 𝐆𝐞𝐧𝟒 𝐚𝐭 𝟏𝟒.𝟐 𝐆𝐁/𝐬. Then we ran collective operations across 𝟏𝟐𝟖 𝐆𝐏𝐔𝐬 (16 nodes, 8xH100s each) and measured how performance degrades at scale: all-reduce drops from 𝟒𝟖𝟎 𝐆𝐁/𝐬 on a single node to 𝟑𝟐𝟎-𝟑𝟓𝟎 𝐆𝐁/𝐬 across 16 nodes.
If you've ever wondered why your training runs are slower than they should be, or you're planning to scale up and want to avoid expensive mistakes, this guide might save you weeks of debugging.
𝐓𝐡𝐞 𝐒𝐦𝐨𝐥 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐏𝐥𝐚𝐲𝐛𝐨𝐨𝐤: https://lnkd.in/e5MKXUHS
Shared with ❤️ by the HuggingFace team
Everyone talks about model architecture and data quality. And yes, those matter immensely. But here's what nobody tells you: when your training run fails at 2 AM because of mysterious 𝐍𝐂𝐂𝐋 𝐞𝐫𝐫𝐨𝐫𝐬, or when your expensive GPU cluster is running at 𝟔𝟎% 𝐞𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐜𝐲, the problem isn't your model. It's most probably a 𝐦𝐢𝐬𝐮𝐬𝐞 𝐨𝐟 𝐭𝐡𝐞 𝐡𝐚𝐫𝐝𝐰𝐚𝐫𝐞. 🛠️
Questions that seemed simple but had no clear answers: Why is 𝐌𝐨𝐄 𝐭𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐬𝐥𝐨𝐰𝐞𝐫 𝐭𝐡𝐚𝐧 𝐝𝐞𝐧𝐬𝐞 𝐦𝐨𝐝𝐞𝐥𝐬? Which 𝐍𝐂𝐂𝐋 𝐟𝐥𝐚𝐠𝐬 should we actually set? How often should we checkpoint without killing throughput?
That's why we built 𝐓𝐡𝐞 𝐒𝐦𝐨𝐥 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐏𝐥𝐚𝐲𝐛𝐨𝐨𝐤 📖: a complete guide covering everything from model architecture and data curation to the SmolLM3 training marathon, post-training techniques, and crucially, the 𝐢𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐥𝐚𝐲𝐞𝐫 that most teams get wrong.
We validated real vs theoretical bandwidth across the entire stack: 𝐇𝐁𝐌𝟑 𝐡𝐢𝐭𝐭𝐢𝐧𝐠 𝟑 𝐓𝐁/𝐬, 𝐍𝐕𝐋𝐢𝐧𝐤 𝟒.𝟎 𝐫𝐞𝐚𝐜𝐡𝐢𝐧𝐠 𝟕𝟖𝟔 𝐆𝐁/𝐬, 𝐏𝐂𝐈𝐞 𝐆𝐞𝐧𝟒 𝐚𝐭 𝟏𝟒.𝟐 𝐆𝐁/𝐬. Then we ran collective operations across 𝟏𝟐𝟖 𝐆𝐏𝐔𝐬 (16 nodes, 8xH100s each) and measured how performance degrades at scale: all-reduce drops from 𝟒𝟖𝟎 𝐆𝐁/𝐬 on a single node to 𝟑𝟐𝟎-𝟑𝟓𝟎 𝐆𝐁/𝐬 across 16 nodes.
If you've ever wondered why your training runs are slower than they should be, or you're planning to scale up and want to avoid expensive mistakes, this guide might save you weeks of debugging.
𝐓𝐡𝐞 𝐒𝐦𝐨𝐥 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐏𝐥𝐚𝐲𝐛𝐨𝐨𝐤: https://lnkd.in/e5MKXUHS
Shared with ❤️ by the HuggingFace team
liked
a
Space
about 2 months ago
reacted to
TravisMuhlestein's
post with ❤️
about 2 months ago
Post
1333
Smarter AI Starts with Consensus
The next frontier in AI isn’t about bigger models — it’s about smarter collaboration.
At GoDaddy, we’re exploring Consensus of LLMs (CoL) — an orchestration approach that brings multiple Large Language Models together to reach agreement before producing an answer.
By combining diverse perspectives from different models — GPT, Claude, Gemini, Llama, and others — CoL helps us:
✅ Reduce hallucinations in AI-generated outputs
✅ Increase factual accuracy and transparency
✅ Make AI safer for real-world, high-stakes business decisions
From customer support bots to security guidance and website content creation, this approach is making AI more reliable, explainable, and aligned with customer trust.
Read more from Jay Gowdy on how GoDaddy is pioneering trustworthy AI at scale 👇
👉 Consensus of LLMs: Scaling Accuracy Beyond a Single Model https://www.godaddy.com/resources/news/consensus-of-llms-scaling-accuracy-beyond-a-single-model
💬 Curious to hear from the AI community: could consensus between models be the key to more trustworthy systems? Share your thoughts — we’d love to continue the conversation.
The next frontier in AI isn’t about bigger models — it’s about smarter collaboration.
At GoDaddy, we’re exploring Consensus of LLMs (CoL) — an orchestration approach that brings multiple Large Language Models together to reach agreement before producing an answer.
By combining diverse perspectives from different models — GPT, Claude, Gemini, Llama, and others — CoL helps us:
✅ Reduce hallucinations in AI-generated outputs
✅ Increase factual accuracy and transparency
✅ Make AI safer for real-world, high-stakes business decisions
From customer support bots to security guidance and website content creation, this approach is making AI more reliable, explainable, and aligned with customer trust.
Read more from Jay Gowdy on how GoDaddy is pioneering trustworthy AI at scale 👇
👉 Consensus of LLMs: Scaling Accuracy Beyond a Single Model https://www.godaddy.com/resources/news/consensus-of-llms-scaling-accuracy-beyond-a-single-model
💬 Curious to hear from the AI community: could consensus between models be the key to more trustworthy systems? Share your thoughts — we’d love to continue the conversation.
- 1 reply