惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

宝玉的分享
宝玉的分享
H
Hackread – Cybersecurity News, Data Breaches, AI and More
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
小众软件
小众软件
月光博客
月光博客
D
DataBreaches.Net
L
LangChain Blog
美团技术团队
S
SegmentFault 最新的问题
MyScale Blog
MyScale Blog
大猫的无限游戏
大猫的无限游戏
博客园 - 司徒正美
aimingoo的专栏
aimingoo的专栏
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
H
Help Net Security
阮一峰的网络日志
阮一峰的网络日志
Y
Y Combinator Blog
I
InfoQ
U
Unit 42
Microsoft Azure Blog
Microsoft Azure Blog
J
Java Code Geeks
博客园 - 三生石上(FineUI控件)
腾讯CDC
Martin Fowler
Martin Fowler

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
AI Desk Meter: Building a Local-First Runtime Dashboard T...
Gary Doman/T · 2026-05-15 · via DEV Community

Gary Doman/TizWildin

AI Desk Meter: Building a Local-First Runtime Dashboard Toward MuseMeter

I’m building AI Desk Meter, an open-source local-first runtime dashboard for AI status, runtime state, and companion-style desktop visibility.

The project is also the open-source foundation leading toward MuseMeter, a future second-brain / Neural Synth / AI buddy product.

The core idea is simple:

local runtime state → JSON source of truth → dashboard sync → native/app/hardware display

Enter fullscreen mode Exit fullscreen mode

AI Desk Meter is meant to stay lightweight, inspectable, and useful without requiring a server.

What AI Desk Meter is

AI Desk Meter is a local-first dashboard project that displays runtime state from a JSON-backed source of truth.

It is designed as a visible companion surface for an AI/runtime system, showing state in a way that can eventually connect to:

  • local AI agents
  • runtime monitors
  • desktop companion apps
  • small hardware displays
  • Raspberry Pi / ESP32 style companion builds
  • native app shells
  • future MuseMeter hardware/software releases

The current project is focused on making the foundation clean, open, and usable.

Why I’m building it

Most AI interfaces are either chat boxes, dashboards, or cloud services.

AI Desk Meter is aimed at a different interaction pattern: a small visible runtime companion that can sit on your desktop, show what the system is doing, and eventually become a bridge between AI status, local memory, agent state, and companion hardware.

The long-term direction is MuseMeter:

  • second-brain style companion
  • local-first AI buddy
  • Neural Synth-inspired visual interface
  • desktop/runtime visibility
  • optional companion hardware
  • open-source foundation before the commercial 3.0 product line

Local-first design

The project is intentionally built around a no-server default.

That means:

  • no required cloud backend
  • dashboard state comes from local files/runtime output
  • JSON can act as the source of truth
  • the system can be inspected directly
  • future native/hardware layers can read the same state model

This keeps the project simple, portable, and easier to reason about.

Current release direction

The current AI Desk Meter direction includes:

  • runtime dashboard sync
  • JSON-backed state updates
  • local-first/no-server architecture
  • support/funding links
  • open-source project foundation
  • future native app holster direction
  • future companion hardware direction
  • roadmap toward MuseMeter 3.0

The small pixel companion character and “Musing...” state are intentional.

Right now, Musing... represents an active response/action/loading state. Later versions may split this into more specific runtime states such as:

  • responding
  • loading
  • thinking
  • idle
  • action running
  • waiting for input
  • agent task active

Why JSON as source of truth

The dashboard is built around a JSON state model because it gives the project a clean bridge between layers.

A JSON runtime state can be read by:

  • the web dashboard
  • a native app wrapper
  • Python CLI tools
  • hardware companion displays
  • future agent runtimes
  • test scripts
  • docs and demos

This makes the dashboard more than a static UI. It becomes a visible surface for a local runtime.

Where MuseMeter fits

AI Desk Meter is the open-source foundation.

MuseMeter is the larger product direction.

The plan is:

AI Desk Meter open-source foundation
→ runtime dashboard stability
→ native app shell / holster
→ real Muse/agent connection
→ companion hardware support
→ MuseMeter 3.0 commercial package

Enter fullscreen mode Exit fullscreen mode

Everything leading up to the commercial 3.0 direction is meant to preserve the open-source foundation while proving the runtime/dashboard concept in public.

Repo

https://github.com/GareBear99/ai-desk-meter

What I’m looking for

I’m looking for feedback from:

  • AI developers
  • local-first app builders
  • Python developers
  • web dashboard developers
  • hardware/display builders
  • Raspberry Pi users
  • ESP32/Arduino experimenters
  • people interested in AI companion interfaces
  • open-source maintainers

Useful feedback includes:

  • dashboard layout issues
  • JSON runtime state suggestions
  • native app packaging ideas
  • hardware display ideas
  • local-first architecture feedback
  • UI/UX suggestions
  • install/run issues
  • roadmap feedback

Long-term vision

The long-term goal is a small, useful, local-first AI companion surface that can grow from a web dashboard into a native app and eventually into hardware.

AI Desk Meter is the foundation.

MuseMeter is the product horizon.

I’m building it in public so the runtime, dashboard, and companion architecture can be tested, improved, and documented as it grows.