Pull down to go back
Building a Multi-Agent Framework in Public for 5 Weeks—Here's What I've Learned
opensourcereddit

Building a Multi-Agent Framework in Public for 5 Weeks—Here's What I've Learned

我花 5 週在公開場合打造多代理 AI 框架，這是我的心路歷程

I've been building AIPass in the open for 5 weeks using Claude Code, and it's finally coming together. Here's the deal: AIPass is a local CLI framework that gives AI agents something they usually lack—persistent identity, memory, and the ability to actually communicate with each other. Instead of sandboxed isolation, agents share the same filesystem, project, and files. Install it with pip, run two commands, and your agent remembers exactly where it left off the next day. The real problem I was solving: AI can remember things, but it forgets context between sessions. This changes that.

Read original →

Keywords

multi-agentAI agentspersistent memorylocal frameworkfilesystemopen source development

Related Articles

TRELLIS.2 image-to-3D now runs on Mac (Apple Silicon) - no NVIDIA GPU needed
Open SourceRead

TRELLIS.2 image-to-3D now runs on Mac (Apple Silicon) - no NVIDIA GPU needed

I ported Microsoft's TRELLIS.2 to run on Apple Silicon via PyTorch MPS. The original depends on five CUDA-only compiled extensions (flex_gemm, flash_attn, o_voxel, cumesh, nvdiffrast) that have no Mac equivalent. Wrote replacement backends from scratch: Pure-PyTorch sparse 3D convolution (replacing flex_gemm), Python mesh extraction using spatial hashing (replacing CUDA hashmap ops in o_voxel), SDPA attention for sparse transformers (replacing flash_attn), and GPU-accelerated trilinear interpolation (replacing cumesh and nvdiffrast).

Reddit
Show HN: Run TRELLIS.2 Image-to-3D generation natively on Apple Silicon
Open SourceRead

Show HN: Run TRELLIS.2 Image-to-3D generation natively on Apple Silicon

I ported Microsoft's TRELLIS.2 (4B parameter image-to-3D model) to run on Apple Silicon via PyTorch MPS. The original requires CUDA with flash_attn, nvdiffrast, and custom sparse convolution kernels: none of which work on Mac. I replaced the CUDA-specific ops with pure-PyTorch alternatives: a gather-scatter sparse 3D convolution, SDPA attention for sparse transformers, and a Python-based mesh extraction replacing CUDA hashmap operations. Total changes are a few hundred lines across 9 files.

Hacker News
157
Which Qwen 3.6 Quantization Works Best for M5 Pro with 24GB RAM?
Open SourceRead

Which Qwen 3.6 Quantization Works Best for M5 Pro with 24GB RAM?

A user with an M5 Pro machine featuring 24GB of RAM is trying to figure out the best quantization level for running Qwen 3.6 via Ollama. They're unsure whether to go with Q4 (4-bit quantization) but can't find a solid Q3 (3-bit) alternative. They're looking for recommendations on which version would run smoothly on their setup without compromising too much on quality.

Reddit