W
Waggle Reimagined · concept
A design concept for Waggle OS

The hive,
made calm.

Waggle is a genuinely powerful agent platform — persistent memory, model-agnostic orchestration, a swarm protocol. But today it speaks like an engineer and looks like a dashboard. This is a concept for making it feel premium, intuitive, and progressively revealed — calm for the knowledge worker, with every ounce of power one keystroke away.

◆ Refreshed Hive identity ◆ Landing page, Home, Chat & Workspace ◆ Dark + light · interactive
The read

What's working —
and what's in the way.

The bones are strong. The friction is in density, language, and surface noise. Five things stood out reading the live product.

01

The spine is overloaded

The left nav carries five zones and ~18 destinations before you've done anything. For a non-technical operator, that's a wall of choices — and the most important act, talking to your agent, is just one item among many.

observed18 nav items · 5 zones · always visible
02

It speaks fluent engineer

"Spawn agent", "Waggle-Dance", "MCPs", "GEPA", "consolidated memories". Power users get it; the operator you're designing for stalls. The product hides its own benefits behind its vocabulary.

observedjargon-first labels, no plain-language layer
03

Everything is small and the same size

The cockpit runs on 10–13px type with thin borders around every block. Nothing leads. It reads as a control panel, not a calm daily briefing — and it never feels premium at that density.

observedtext-[10px]…[13px] · border on every card
04

Five colors shouting at once

Blue, purple, green, orange, red all fire simultaneously across the briefing, layered over glass, a wallpaper, and a honeycomb texture. The eye has no rest and no hierarchy to follow.

observed5 semantic hues + glass + wallpaper + comb
05

The magic stays hidden

Memory that compounds, work that happens overnight, agents that coordinate — these are the reasons to choose Waggle. They're present but buried in counters and lists. The differentiators never get a hero moment.

observedbenefits expressed as small tallies
The response

Five principles
for the redesign.

Each one answers a finding above. They're the rules every screen in this concept follows.

01 ↦ findings 01·02

Calm by default,
powerful on demand

Show only what the moment needs. Swarm, MCPs, optimizer and the rest live behind one command bar — discoverable, never in the way. Progressive disclosure as the core mechanic.

02 ↦ finding 01

One clear spine

Collapse 18 destinations into a handful of plain-language places, anchored on the conversation. Everything else is reachable from ⌘K — the OS, not the sidebar, holds the breadth.

03 ↦ finding 05

Show the magic

Memory, overnight work and coordination get real estate and language a human understands. The differentiators become legible scenes, not tallies in a corner.

04 ↦ findings 03·04

Warm & crafted

A warm graphite hive, one honey accent used with intent, an editorial serif for moments that matter, and air between things. Premium is restraint plus a real type hierarchy.

05 ↦ finding 02

Speak human, reveal the expert layer

Lead with plain words — "Start a task", "Working while you're away", "Team of agents". The technical name ("waggle-dance", "MCP server") rides along as a quiet subtitle for the power user. One product, two reading levels.

Identity

A warmer hive.

Same DNA — honey, hexagons, the waggle dance — rebuilt for warmth and restraint. The cold blue-graphite becomes a warm graphite you'd want to live in; honey stops being decoration and becomes a precision accent; and one clean grotesk does the talking — simple, not bookish.

Surfaces · warm graphite → warm paper

Accent & refined semantics

Type — one humanist grotesk, used with a real scale · mono for the technical layer

Display
Hanken Grotesk 600
The hive, made calm.
Interface
Hanken Grotesk 400–600
Start a task, and Waggle remembers.One family, simple and modern — hierarchy comes from size and weight, not a second typeface.
Technical
JetBrains Mono
waggle-dance · 3 agents · mem://hive/2026-06 · ⌘K
The spine, in practice

Five places & a command bar.

The live version of the IA above. A calm five-item sidebar; press ⌘K and the whole platform is searchable — swarm, MCP servers, optimizer, vault — each named in plain language with the technical term underneath. Power users can pin the tools they live in.

A · Calm spine B · Pro (pinned tools) Try ⌘K inside ↓
Open full screen ↗
waggle · navigation & ⌘K
The public front door

The landing page, rewritten.

A full redesign of waggle-os.ai — new identity, new content. It leads with the real story: one local memory that feeds every model, the proof that the layer (not the model) does the work, and honest free-forever pricing. No cartoon bees; the hive is a precise idea.

◆ New hive-memory hero ◆ LoCoMo proof, made legible ◆ Dark + light
Open full screen ↗
waggle-os.ai
Screen 01 · Home

The morning briefing.

A calm scene that opens with one sentence of human language, surfaces what ran overnight as a story, and offers a single obvious next move.

A · Editorial briefing B · Focus / single-action C · Operator dashboard
Open full screen ↗
waggle · home
Screen 02 · Chat runtime

Where the work
happens.

The core surface. The conversation leads; the agent's thinking, tool calls, memory writes and approvals reveal progressively beside it — legible, never overwhelming.

A · Conversation-first B · Split work canvas
Open full screen ↗
waggle · workspace / chat
Screen 03 · Workspace

A place that remembers.

The workspace makes Waggle's memory tangible — what it knows, what it made, who's working on what — without drowning you in tabs.

A · Overview + tabs B · Memory-forward
Open full screen ↗
waggle · workspace
Screen 04 · Launcher · the feature I under-served

Bring your own agent.

Waggle can detect and launch Claude Code, Cursor, Codex, Hermes — and run them wired into this workspace's memory. The agent recalls what the hive knows and commits its work back, with provenance. The shipped screen calls itself “minimal-viable”; this makes it a first-class surface and explains the wiring.

A · Launch & manage B · How memory is shared
Open full screen ↗
waggle · launch external agents
Screen 05 · Storage · making the filesystem legible

Where your work lives.

A workspace can be Virtual (Waggle-managed), Local (a real folder on your machine), or Team (shared). Today that's invisible. This surface shows the exact path — memory db, files, artifacts — and what stays private, so “local-first” is something you can see.

A · Where it lives B · Files + provenance
Open full screen ↗
waggle · storage & files
Screen 06 · the long tail, cleaned up

Every power tool, one template.

The surfaces that used to be 15 bespoke, half-finished screens — Tools & connectors, Automations, Approvals, Vault, Usage — rebuilt on one consistent, functional pattern and tucked behind ⌘K. Switch with the rail; toggles, approvals, and renewals all work.

ToolsAutomationsApprovalsVaultUsage
Open full screen ↗
waggle · power surfaces (⌘K)
Screen 07 · answering “where are all my workspaces?”

The whole shelf.

Home greets you with the day; Workspaces is every space you have — with its storage type (local / virtual / team), memory count, and what's live. Searchable, filterable, and reachable from the rail, ⌘K, or any workspace's switcher.

GridTablesearch + storage filters
Open full screen ↗
waggle · all workspaces
Screen 08 · first run · the part I'd skipped

Two minutes to first value.

A five-step takeover: welcome → a little about you → import your history (locally) → pick a starting template → your first task. It ends inside the work, not on an empty screen. Step through it with the controls.

WelcomeAbout youImportTemplateFirst task
Open full screen ↗
waggle · first-run onboarding
Screen 09 · the second moat

Skills that improve & spread.

Beyond memory: skills re-optimize themselves against real outcomes (versioned, judged, roll-back-able) and diffuse across agents and workspaces — the waggle dance. Tool setups spread the same way. The whole hive compounds.

A · Skills that improveB · Skills & tools that spread
Open full screen ↗
waggle · skill evolution & diffusion
Screen 10 · Settings · calm, with a model gate

Settings that route themselves.

The whole settings surface rebuilt around progressive disclosure (Essential → Standard → Everything). The lead is Models: Waggle needs one working model, so it surfaces a failover chain — primary → fallback on error → a local/budget model when you hit your cap. The same model gate appears in onboarding, so first-run can't dead-end.

Model pilot + failoverEssential / Standard / EverythingPermissions · Plan · Backup
Open full screen ↗
waggle · settings
Screen 11 · Marketplace · made simple & agent-searchable

Capabilities, without the catalog.

Skills, connectors, and MCP tools were three separate, jargon-heavy surfaces. Now they're one shelf — and you don't browse 400 cards, you describe the job and the agent picks (a connector to reach your data, a skill to do the work, the tool they need). The same picker also appears inline in chat the moment a task needs something you don't have.

A · Browse & ask the agentB · Inline in chat
Open full screen ↗
waggle · marketplace
Screen 12 · Front door · Clerk

Getting in, kept simple.

Sign-in, sign-up, email verification, and SSO — clean and on-brand, with an honest twist: an account is optional. Waggle runs fully local without one; you sign in only to sync across devices or join a team.

Sign inSign upVerify (OTP)SSO / enterprise
Open full screen ↗
waggle · auth (clerk)
Screen 13 · Billing · Stripe

Upgrading, without friction.

Plans → checkout → success → manage, as a clean Stripe flow. Monthly/annual toggle, a trial-aware order summary, a real card form, and a billing portal with invoices. Honest pricing, no dark patterns.

PlansCheckoutSuccessManage & invoices
Open full screen ↗
waggle · billing (stripe)
The engagement layer · why it sticks

Built to pull you back.

A product that compounds deserves a habit loop. Trigger → action → variable reward → investment, made concrete with a daily streak, a compounding-memory counter, "while you were away" wins, and earned nudges. Momentum, not manipulation — every loop is anchored to real value, and all of it can be turned off.

StreakCompounding memoryVariable rewardGentle nudges
Open full screen ↗
waggle · the habit loop
Screen 14 · the queued surfaces, drawn

The rest of the hive.

The six remaining app routes, on one consistent rail: Agents (your team of specialists), Room (work alongside agents live), Artifacts (everything made, with provenance), Mission Control (the hive's health), Timeline (one activity stream), and Profile (what Waggle knows about you).

AgentsRoomArtifactsMission ControlTimelineProfile
Open full screen ↗
waggle · app surfaces
Positioning · benchmarking

They automate tasks.
Waggle remembers you.

An honest read against the field — Claude Code, Codex, Claude Cowork, Hermes, Odysseus. They're terminal task-agents for engineers; Waggle is a persistent, local-first memory layer that even launches them. Plus the one real head-to-head: the LoCoMo memory SOTA (87.66%).

A · Capability matrixB · Memory SOTA
Open full screen ↗
waggle · benchmarks
Platform · ships in Tauri · what's next

One hive, everywhere.

Waggle ships as a native Tauri desktop app for Windows & macOS — tiny, local, auto-updating. This covers the boot splash and 404 too, and lays out the roadmap: a browser extension in beta, and messaging (WhatsApp, Telegram) + mobile coming next.

Desktop (now)BootComing next404
Open full screen ↗
waggle · platform & roadmap
Monorepo coverage

The whole surface, mapped.

Every route in the app's router, every OS app, and the front-of-app + payment + auth surfaces — with honest status. Click any designed one to jump to it.

Designed — has its own screen here Covered inside another screen Coming next · messaging & mobile

The bones are strong.

This concept keeps everything Waggle can do and changes how it feels to do it. Pick the directions that resonate and I'll take them deeper.