OpenClaw
Personal-agent runtime. Heartbeat monitors check for meaningful changes; automations and incoming events can activate work.
Projects & code
Open repositories, working implementations, and project pages.
/
Hermes Agent
Agent harness with memory/skills and scheduled tasks delivered through messaging channels.
Letta Code
Stateful agent harness supporting always-on operation, persistent memory, and self-managed schedules.
Proactivity SDK
Framework adapter layer with durable goals, cross-wake state, model-selected cadence, and event-driven waking.
MineContext
Screenshots and desktop context → background summaries, tips, todos, and resurfaced information.
GAIA
Connected services → automatic inbox triage, meeting briefings, and schedule/event-driven workflows.
memUBot
Persistent user/team context → recurring automations and message, keyword, or platform-event-triggered skills.
Proactive Agent
Predicts tasks and assistance opportunities from activity/event streams.
ContextAgent
Uses open-world sensory context to decide on assistance and tool use.
PASK
IntentFlow detects latent needs and chooses silence, fast intervention, or deeper assistance with hierarchical user/workspace/global memory.
OpenAI dot
Always-on ongoing responsibility; background research, proactive connected-app review and memory formation, suggestions, and scheduled checks between conversations.
memU
Shared personal memory across sessions, agents, and devices; scheduled background memorization and later retrieval.
Screenpipe
Desktop screen/audio history, workflow mapping, and context for agents/automations.
Live VLM WebUI
WebRTC camera interface for connecting and comparing VLM inference backends.
Projects & Products
README · Applications · Personal Agents · Streaming Proactivity · Research Map · Benchmark Matrix
This guide covers implemented resources alongside research papers. Entries are grouped by activation mechanism and role, so a scheduler, a trained intervention policy, a product, and a memory library can be compared without conflating their evidence.
Last checked: 2026-10-04. Sources are official repositories, READMEs, and documentation. This is a documentation-based curation, not an installation test or an independent performance comparison. Release and access statements describe the checked snapshot.
Persistent Runtimes and Activation SDKs
| Project | Role and activation mechanism | Available resources | Boundary / what to inspect | Official sources |
|---|---|---|---|---|
| OpenClaw | Personal-agent runtime. Heartbeat monitors check for meaningful changes; automations and incoming events can activate work. | Runtime source and operational docs. | Monitor activation and notification suppression are runtime mechanisms; downstream helpfulness depends on the configured agent and standing instructions. | Repository · Heartbeat · Automation |
| Hermes Agent | Agent harness with memory/skills and scheduled tasks delivered through messaging channels. | Source, CLI/gateway, and cron documentation. | Include as scheduled activation: a user-defined recurring job does not by itself demonstrate discovery of an unstated need. | Repository · Scheduled tasks |
| Letta Code | Stateful agent harness supporting always-on operation, persistent memory, and self-managed schedules. | Source, CLI, and scheduling/permissions docs. | Memory persistence and scheduled execution are distinct from calibrated intervention timing. | Repository · Schedules |
| Proactivity SDK | Framework adapter layer with durable goals, cross-wake state, model-selected cadence, and event-driven waking. | TypeScript SDK, adapters, examples, and governance primitives. | Inspect cadence, goal continuity, idempotency, and action caps. These controls describe orchestration, not a trained streaming model or benchmark result. | Repository |
Ambient and Personal Assistants
| Project | Observed context → proactive behavior | Available resources | Boundary / what to inspect | Official sources |
|---|---|---|---|---|
| MineContext | Screenshots and desktop context → background summaries, tips, todos, and resurfaced information. | Desktop application, context-processing source, configuration, and releases. | Ambient information delivery is the relevant behavior. Broader multi-source inputs described as future support should remain separate from current capabilities. | Repository |
| GAIA | Connected services → automatic inbox triage, meeting briefings, and schedule/event-driven workflows. | Application source and self-hosting instructions. | A concrete personal-workflow reference; source is under PolyForm Noncommercial, so record it as source-available. Proactive utility is described by the project, not independently measured here. | Repository · License |
| memUBot | Persistent user/team context → recurring automations and message, keyword, or platform-event-triggered skills. | Assistant source built around memU. | Treat the assistant and its memory layer separately. Enterprise-readiness and cost-reduction claims in the README are not validated by this list. | Repository |
Research Implementations
| Project | Proactive mechanism | What to reuse | Evidence boundary | Official sources |
|---|---|---|---|---|
| Proactive Agent | Predicts tasks and assistance opportunities from activity/event streams. | Event collection, data generation, agent/reward checkpoints, and evaluation pipeline. | ICLR 2025 method + ProactiveBench; distinguish generated training scenarios from real-user deployment outcomes. | Paper · Repository · Notes |
| ContextAgent | Uses open-world sensory context to decide on assistance and tool use. | Inference, SFT, tools, prompts, and sensory-context data layout. | NeurIPS 2025 research system; inspect sensing assumptions and the context-to-assistance policy. | Paper · Repository · Notes |
| PASK | IntentFlow detects latent needs and chooses silence, fast intervention, or deeper assistance with hierarchical user/workspace/global memory. | Official repository, project page, system descriptions, and client download links. | Technical report and preliminary user evidence. Public client/documentation links do not establish that every training component or model weight is released; no installation or evaluation was repeated here. | Paper · Repository · Project · Notes |
Streaming research implementations have a dedicated model and framework matrix, including JoyAI-VL-Interaction, MOSS-VL-Realtime, OneStreamer, Proact-VL, Response-G1, Eyes Wide Open, MiniCPM-o 4.5, and Gander.
Product Reference
| Product | Documented initiative | Evidence and access boundary | Official source |
|---|---|---|---|
| OpenAI dot | Always-on ongoing responsibility; background research, proactive connected-app review and memory formation, suggestions, and scheduled checks between conversations. | Official product documentation. User-defined rules and pause controls govern activity. No open implementation or independent proactive benchmark is established by this documentation; plan/region rollout can change. | Getting started with your dot |
Supporting Components
| Component | Role in a proactive system | What it does not establish by itself | Official sources |
|---|---|---|---|
| memU | Shared personal memory across sessions, agents, and devices; scheduled background memorization and later retrieval. | Memory formation is not an intervention policy. The current README emphasizes a shared wiki and host adapters; use memUBot for the assistant layer. | Repository |
| Screenpipe | Desktop screen/audio history, workflow mapping, and context for agents/automations. | Capture and workflow discovery require an integrated agent to choose whether and when to help. Source-available, with separate licensing terms. | Repository · License |
| Live VLM WebUI | WebRTC camera interface for connecting and comparing VLM inference backends. | A live interface does not make a conventional model natively streaming or give it a learned speak/silence gate. | Repository |
How to Add a Project
Record the resource type, activation source, context input, observable behavior, release/access status, source, and checked date. Link a concrete heartbeat/scheduler, event hook, intervention gate, or documented product workflow. Keep a component in its supporting role unless its own implementation selects user-facing interventions.
Prefer canonical upstream repositories over mirrors and forks. A paper implementation belongs here when it offers reusable code; retain its bibliographic record and decision card in the paper collection.