Skip to content

Project Tracker: Peggy — personal-assistant agent on glue #110

Description

@erain

This pinned issue is the durable progress keeper for Peggy, a long-running personal-assistant agent built on the glue framework. It tracks execution order, status, and acceptance for the OpenClaw/Hermes-inspired local assistant work.

Operating contract: no feature issue is closed without a merged PR that references it. See CONTRIBUTING.md for the per-issue workflow.

Product Goal

Peggy is a local-first personal-assistant agent that is:

  • reachable from multiple channels: CLI, local daemon clients, and Telegram today
  • durable across sessions through SQLite-backed memory and recall
  • capable of permission-gated coding work in trusted local workspaces
  • extensible through file-backed skills, roles, and MCP servers
  • a testbed for keeping glue clean: product policy lives in agents, not framework defaults

Inspirations: OpenClaw for channel multiplexing and Hermes-Agent for skills-as-files, FTS5 session search, and tools-as-RPC.

Current Phase

M7: Dual-track — Glue coding-agent binary + Peggy OpenClaw polish — in progress as of 2026-06-07.

🚀 Public launch (2026-05-27). The framework now has a homepage — https://glue-framework-site.vercel.app — backed by a first tagged release v0.1.0 (pre-1.0 stance: ADR-0013). Discussions and a security policy (SECURITY.md) are live; issue + PR templates wired. Social announcement still gated on a deliberate decision.

M1–M6 are shipped (see Shipped Milestones). Peggy is in owner/developer dogfooding on the peggy-dogfood Multipass VM. Work now runs on two parallel tracks, kept independently reviewable under the one-issue/one-PR contract:

  • Track A — Glue as a coding-agent binary (framework). Make cmd/glue an awesome coding agent in its own right. ADR-0012 established the boundary: Glue owns the reusable coding-tool bundle (tools/coding) and the binary's coding surface (glue run/serve --coding); Peggy is a thin consumer. The coding-tool surface and the interactive TUI are complete — provider choice + Pi-class tools (edit_file, list_dir, find_files, grep) + a bubbletea TUI with streaming text, tool cards, inline permission prompts, edit_file diff preview, and slash commands. glue run --provider codex --coding is now an interactive coding agent by default in a terminal. Only one Track A enhancement remains: the sandboxed Executor backend (container/VM) behind the existing seam.
  • Track B — Peggy as an OpenClaw-clone personal assistant (product). Harden the always-on assistant from concrete dogfood findings: proactivity, richer channel UX, and dashboard actions.

The architectural rule still holds (ADR-0005 §1): product concerns live in agents/peggy; reusable primitives live in glue / tools/*.

M7 Work Queue

Track A — Glue coding-agent binary

Harness quality — be the best Gemini + open-weight coding harness

Source-verified analysis of pi / Cline / Codex CLI / Gemini CLI distilled into docs/coding-harness-roadmap.md (#336). Implementation order (P0 first — all four harnesses converge on these):

🌐 Coding-agent homepage shipped (2026-06-09). New repo erain/glue-coding-agent-site (Astro+Tailwind, same design system as the framework site, terminal-green accent) → https://glue-coding-agent-site.vercel.app once imported in the Vercel dashboard. The framework site's §06/§07 now cross-link it.

Goal loop — "loop engineering" / /goal (ADR-0016)

Gemini harness hardening (being a first-class Gemini 3.x coding harness) — shipped in v1.8.0

All four landed as v1.8.0 (the gemini default-id fix that shipped as v1.7.0 was also promoted out of the changelog's Unreleased section).

Track B — Peggy OpenClaw polish

Repo hygiene (shipped)

Completed Dogfood Readiness Work

Dogfood Polish

Shipped Milestones

  • M1 — Peggy v0.1: "She remembers and you can text her". Shipped 2026-05-16. Foundation ADRs, Codex provider, SQLite/FTS5 store, memory tools, single-prompt CLI, and Telegram channel.
  • M2 — Peggy v0.2: "She can code". Shipped 2026-05-24. Executor/Permission/Hook interfaces, shell/fs/git tools, subagents, opt-in Peggy coding mode, and CLI/Telegram permission prompts.
  • M3 — Peggy v0.3: "Multi-channel daemon". Shipped 2026-05-24. HTTP+SSE daemon protocol, peggy serve, glue connect, Telegram daemon-client mode, and per-channel permission tiers.
  • M4 — Peggy v0.4: "Ecosystem". Shipped 2026-05-24. MCP stdio and Streamable HTTP clients, MCP tools/resources/prompts, daemon status/tools/inspect, and local peggy status.
  • M5 — Peggy v0.5: "Workflow/runtime". Shipped 2026-05-25. Workspace context, file-backed skills, roles, starter peggy init, usage summaries, daemon memory/recall controls, and Telegram daemon role/skill/memory/status commands.
  • M6 — Dogfood hardening and product shell. Shipped 2026-05-25. Doctor, quickstart, persistent permission grants, Telegram daemon UX, sessions, diagnostics, memory backup/restore, and local dashboard.

See agents/peggy/CHANGELOG.md for detailed release notes and PR history.

Known Product Gaps

The M6 dogfood blockers are complete; the active gaps are now tracked in the M7 Work Queue above. Additional Track B candidates not yet filed: packaged install flows, calendar / external-service triggers, and more realistic long-running personal-assistant evaluations. New gaps from daily dogfooding of peggy-dogfood should be filed as focused follow-up issues and linked under the M7 Work Queue.

Pacing

Sessions should check /status periodically and pause/resume around quota limits rather than forcing oversized turns. Keep PRs small enough to review and merge independently.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions