Audio classified
Collection
3 items • Updated
AI & ML interests
Connecting individuals with innovation: Emancipating and Truly Federalizing Private Intelligence
Recent Activity
fuzzy-mittenz
updated a
collection 4 days ago
fuzzy-mittenz
updated a
Space 5 days ago
fuzzy-mittenz
updated a
collection 11 days ago
fuzzy-mittenz
updated a
collection 15 days ago
fuzzy-mittenz
updated a
collection 30 days ago
Post
93
Released MAiRY Star, a companion/perosna Ai fine tuned with SFT Studio Pro dataset , no RLHF or reward optimization. Access at https://triadai.tech
Q-bert
authored a
paper 2 months ago
suayptalha
submitted a
paper to Daily Papers 2 months ago
suayptalha
authored a
paper 2 months ago
suayptalha
authored a
paper 3 months ago
Post
491
Shipped v0.1.2 of vtx — a minimalist coding agent for the terminal.
Most agentic CLIs ship 10k+ token system prompts. Vtx is ~2,200. Less prompt overhead means more room for your code in the model's context window.
Vtx is a from-scratch Python implementation of the design philosophy behind pi-mono — same principles, pure Python, no transpiled runtime.
What ships out of the box:
→ Textual TUI + headless CLI (vtx -p "fix the failing test")
→ 49 LLM provider gateways, all declared in a single provider.yaml
→ 5 core tools (read / edit / write / bash / find) plus web search and fetch
→ Session tree with compaction, handoff, and resume
→ AGENTS.md / CLAUDE.md auto-discovery
→ Skills system — drop SKILL.md files in .agents/skills/ and they become slash commands
→ Two OAuth flows (GitHub Copilot device flow, OpenAI Codex PKCE)
→ Two-mode permissions: prompt (default) or auto, with a safe-command allowlist
This release adds a proper extension system. Register new LLM-callable tools, intercept tool calls, hook lifecycle events, and add slash commands from a single register(api) function in a Python file under ~/.vtx/agent/extensions/. Extensions can override built-in tools by name and chain handler logic across subscribers.
Apache 2.0. uv tool install vtx-coding-agent and you're running.
GitHub: https://github.com/OEvortex/vtx-coding-agent
PyPI: https://pypi.org/project/vtx-coding-agent
Built in the open. Feedback, extensions, and PRs welcome.
Most agentic CLIs ship 10k+ token system prompts. Vtx is ~2,200. Less prompt overhead means more room for your code in the model's context window.
Vtx is a from-scratch Python implementation of the design philosophy behind pi-mono — same principles, pure Python, no transpiled runtime.
What ships out of the box:
→ Textual TUI + headless CLI (vtx -p "fix the failing test")
→ 49 LLM provider gateways, all declared in a single provider.yaml
→ 5 core tools (read / edit / write / bash / find) plus web search and fetch
→ Session tree with compaction, handoff, and resume
→ AGENTS.md / CLAUDE.md auto-discovery
→ Skills system — drop SKILL.md files in .agents/skills/ and they become slash commands
→ Two OAuth flows (GitHub Copilot device flow, OpenAI Codex PKCE)
→ Two-mode permissions: prompt (default) or auto, with a safe-command allowlist
This release adds a proper extension system. Register new LLM-callable tools, intercept tool calls, hook lifecycle events, and add slash commands from a single register(api) function in a Python file under ~/.vtx/agent/extensions/. Extensions can override built-in tools by name and chain handler logic across subscribers.
Apache 2.0. uv tool install vtx-coding-agent and you're running.
GitHub: https://github.com/OEvortex/vtx-coding-agent
PyPI: https://pypi.org/project/vtx-coding-agent
Built in the open. Feedback, extensions, and PRs welcome.
Post
3472
🙋🏻♂️ Hey there folks ,
Turns out : if we predict 🌏 earth we can save a lot of time looking for interesting things and less time looking at things that we expect to see.
Sentinel-2 imagery 🛰️basically takes a long time to download towards earth. so our "near real time" systems are quite far from that in practical terms.
meanwhile , if we "predict" what we will see , based on what we do see , we can send down much less data in a timely way , and prioritize 📡earth-bound response .
I'm talking about illegal fishing , logging , mining or building in nature reserves , the more of that we predict early the more we're able to stop it on time.
At least that's the concept !
check out the blog : https://huggingface.co/blog/Tonic/save-patagonia-by-predicting-earth
- Collection: https://huggingface.co/collections/NuTonic/earth-observation-with-temporal-and-general-understanding
- Code: https://github.com/Josephrp/Nutonic
- Dataset: NuTonic/sat-vl-sft-training-ready-v1
- Model: NuTonic/lspace
- Training: NuTonic/lspace-trackio
- Evals: NuTonic/Patagonia_Eval
Turns out : if we predict 🌏 earth we can save a lot of time looking for interesting things and less time looking at things that we expect to see.
Sentinel-2 imagery 🛰️basically takes a long time to download towards earth. so our "near real time" systems are quite far from that in practical terms.
meanwhile , if we "predict" what we will see , based on what we do see , we can send down much less data in a timely way , and prioritize 📡earth-bound response .
I'm talking about illegal fishing , logging , mining or building in nature reserves , the more of that we predict early the more we're able to stop it on time.
At least that's the concept !
check out the blog : https://huggingface.co/blog/Tonic/save-patagonia-by-predicting-earth
- Collection: https://huggingface.co/collections/NuTonic/earth-observation-with-temporal-and-general-understanding
- Code: https://github.com/Josephrp/Nutonic
- Dataset: NuTonic/sat-vl-sft-training-ready-v1
- Model: NuTonic/lspace
- Training: NuTonic/lspace-trackio
- Evals: NuTonic/Patagonia_Eval
- 3 replies
Post
220
Introducing
Its a very tiny model that reaches comparable results at PII classification thru viterbi BIOES decoding, harnessing 98%~ the original model performance while being a tiny fraction of the base model.
It doubles the performance tk/s, reduces the active params dramatically and the VRAM footprint.
The evaluation & benchmarking is within the model repository and can be reproduced. I trained it with an RTX4090 without issues and it is compatible with OpenMed suite and a in-place replacement for openai privacy-filter model.
fblgit/haremb-privacy-filter-opennemo
I'm looking for people who wants to co-author/contribute/endorse HarEmb research and the technical paper for the model.
Contact xavi@juanako.ai
HarEmb - PII a single-transformer-block distilled layer from OpenMed PII Privacy filter.Its a very tiny model that reaches comparable results at PII classification thru viterbi BIOES decoding, harnessing 98%~ the original model performance while being a tiny fraction of the base model.
It doubles the performance tk/s, reduces the active params dramatically and the VRAM footprint.
The evaluation & benchmarking is within the model repository and can be reproduced. I trained it with an RTX4090 without issues and it is compatible with OpenMed suite and a in-place replacement for openai privacy-filter model.
fblgit/haremb-privacy-filter-opennemo
I'm looking for people who wants to co-author/contribute/endorse HarEmb research and the technical paper for the model.
Contact xavi@juanako.ai
Sri-Vigneshwar-DJ
posted an update 5 months ago
Post
211
We ran Feather DB v0.8.0 on LongMemEval (ICLR 2025) — 500 questions across real multi-session conversations, up to 115K tokens each.
**Score: 0.693** · GPT-4o full-context baseline: 0.640
Full 500-question run with Gemini-Flash: **$2.40**
Per-axis breakdown:
→ Info-extraction: **0.942**
→ Knowledge-update: **0.714**
→ Multi-session: **0.606**
→ Temporal: **0.477** ← the hard one, Phase 9 addresses this
Architecture: Hybrid BM25+dense · adaptive temporal decay · embedded (no server) · p50 = 0.19ms · MIT
Raw results + audit JSONs: Hawky-ai/longmemeval-results
We ran Feather DB v0.8.0 on LongMemEval (ICLR 2025) — 500 questions across real multi-session conversations, up to 115K tokens each.
**Score: 0.693** · GPT-4o full-context baseline: 0.640
Full 500-question run with Gemini-Flash: **$2.40**
Per-axis breakdown:
→ Info-extraction: **0.942**
→ Knowledge-update: **0.714**
→ Multi-session: **0.606**
→ Temporal: **0.477** ← the hard one, Phase 9 addresses this
Architecture: Hybrid BM25+dense · adaptive temporal decay · embedded (no server) · p50 = 0.19ms · MIT
pip install feather-dbRaw results + audit JSONs: Hawky-ai/longmemeval-results
Post
4509
🙋🏻♂️ Hey there folks,
since everyone liked my previous announcement post ( https://huggingface.co/posts/Tonic/338509028435394 ) so much , i'm back with more high quality proceedural datasets in the Geospacial domain for SFT training !
Check this one out :
NuTonic/sat-bbox-metadata-sft-v1
the goal is to be able to train vision models on multiple images for remote sensing analysis with one shot .
hope you like it ! 🚀
since everyone liked my previous announcement post ( https://huggingface.co/posts/Tonic/338509028435394 ) so much , i'm back with more high quality proceedural datasets in the Geospacial domain for SFT training !
Check this one out :
NuTonic/sat-bbox-metadata-sft-v1
the goal is to be able to train vision models on multiple images for remote sensing analysis with one shot .
hope you like it ! 🚀
- 2 replies
Post
3758
🙋🏻♂️ Hey there folks ,
I'm sharing huggingface's largest dataset of annotated statelite images today.
check it out here : NuTonic/sat-image-boundingbox-sft-full
I hope you like it , the idea is to be able to use this with small vision models 🚀
I'm sharing huggingface's largest dataset of annotated statelite images today.
check it out here : NuTonic/sat-image-boundingbox-sft-full
I hope you like it , the idea is to be able to use this with small vision models 🚀
suayptalha
authored a
paper 6 months ago
Q-bert
authored a
paper 6 months ago
Post
186
I recently built https://github.com/fblgit/eLLMulator
A software emulator for Claude Code.
eLLMulator approach:
LLM agents become your software components. Each agent deeply studies its assigned source file, then interacts with other agents via synchronous MCP tool calls that mirror real function calls. The call graph emerges naturally from code control flow, producing traces that capture not just what happened, but why each component behaved as it did.
The Claude Agent SDK provides sessions, MCP provides the bus. The code itself is the routing layer.
https://github.com/fblgit/eLLMulator
A software emulator for Claude Code.
eLLMulator approach:
LLM agents become your software components. Each agent deeply studies its assigned source file, then interacts with other agents via synchronous MCP tool calls that mirror real function calls. The call graph emerges naturally from code control flow, producing traces that capture not just what happened, but why each component behaved as it did.
The Claude Agent SDK provides sessions, MCP provides the bus. The code itself is the routing layer.
https://github.com/fblgit/eLLMulator