I want everything local – Building my offline AI workspace
TL;DR Highlight
Building a fully offline AI workspace with LLM chat, code execution, and web browsing using Ollama, Apple Container, and Playwright — no cloud dependency. A meaningful attempt at replicating ChatGPT-level workflows while keeping personal data local.
Who Should Read
Developers who want to process sensitive personal data (photos, documents) with AI but don't want to upload to the cloud. Apple Silicon Mac users looking to set up their own local LLM environment.
Core Mechanics
- Goal: replicate ChatGPT/Claude's 3 capabilities (LLM chat, code execution, web access) entirely locally. Uses Ollama for LLM, Apple Container (independent VM per container) for code execution, Playwright for browser automation.
- Initially tried building a native Mac app with a0.dev but it was too iOS-focused, so pivoted to a Next.js web app — which worked much better for this use case.
- Complete data privacy — nothing leaves the local machine. Personal photos, documents, and conversations stay private.
- Hardware is the biggest bottleneck — 80B+ parameter models need large amounts of fast RAM. Even Mac Mini with sufficient RAM costs $2K+.
Evidence
- Hardware was the most-discussed bottleneck. Running 80B+ models requires massive high-speed RAM — Mac Mini with enough RAM exceeds $2K. Framework desktop (128GB unified RAM) at $2-2.5K was mentioned as an option.
- Berkeley research team's LEMO system was referenced as another open-source local AI workspace approach.
- Apple Container provides VM-level isolation per code execution, addressing security concerns about running LLM-generated code.
How to Apply
- For AI processing of personal photos/videos/documents without cloud exposure: Ollama + Apple Container keeps all data local. Just add the coderunner URL to mcpServers config for code execution from Claude Desktop too.
- For local LLM tool-calling needs: Llama 3.3 70B via Ollama provides decent tool-calling support. Pair with MCP servers for file system, database, and web access.
- Budget carefully — local AI that matches cloud quality requires significant hardware investment ($2K+ for a usable setup).
Code Example
// Configure coderunner MCP connection in Claude Desktop or Gemini CLI
{
"mcpServers": {
"coderunner": {
"httpUrl": "http://coderunner.local:8222/mcp"
}
}
}Terminology
Related Papers
Show HN: adamsreview – better multi-agent PR reviews for Claude Code
Claude Code에서 최대 7개의 병렬 서브 에이전트가 각각 다른 관점으로 PR을 리뷰하고, 자동 수정까지 해주는 오픈소스 플러그인이다. 기존 /review나 CodeRabbit보다 실제 버그를 더 많이 잡는다고 주장하지만 커뮤니티에서는 복잡도와 실효성에 대한 회의론도 나왔다.
How Fast Does Claude, Acting as a User Space IP Stack, Respond to Pings?
Claude Code에게 IP 패킷을 직접 파싱하고 ICMP echo reply를 구성하도록 시켜서 실제로 ping에 응답하게 만든 실험으로, 'Markdown이 곧 코드이고 LLM이 프로세서'라는 아이디어를 네트워크 스택 수준까지 밀어붙인 재미있는 사례다.
Show HN: Git for AI Agents
AI 코딩 에이전트(Claude Code 등)가 수행한 모든 툴 호출을 자동으로 추적하고, 어떤 프롬프트가 어느 코드 줄을 작성했는지 blame까지 가능한 버전 관리 도구다.
Principles for agent-native CLIs
AI 에이전트가 CLI 도구를 더 잘 사용할 수 있도록 설계하는 원칙들을 정리한 글로, 에이전트가 CLI를 도구로 활용하는 빈도가 높아지면서 이 설계 방식이 실용적으로 중요해지고 있다.
Agent-harness-kit scaffolding for multi-agent workflows (MCP, provider-agnostic)
여러 AI 에이전트가 서로 역할을 나눠 협업할 수 있도록 조율하는 scaffolding 도구로, Vite처럼 설정 없이 빠르게 멀티 에이전트 파이프라인을 구성할 수 있다.
Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem
AI 에이전트가 실제 프로덕션 데이터를 건드려도 롤백할 수 있는 격리된 샌드박스 환경을 제공하는 도구로, GitHub/S3/Google Drive를 하나의 버전 관리 파일시스템으로 묶어준다.
Related Resources
- https://instavm.io/blog/building-my-offline-ai-workspace
- https://github.com/yichuan-w/LEANN
- https://arxiv.org/abs/2405.08051
- https://github.com/exo-explore/exo
- https://github.com/assistant-ui/assistant-ui
- https://hypersonic.chat/
- https://kasmweb.com/
- https://developer.apple.com/documentation/FoundationModels