always-on-agent-applications

license	Apache-2.0
name	always-on-agent-applications
description	What you can build and do with an always-on AI agent that has episodic memory. Covers concrete product ideas, workflows, emergent capabilities from persistence plus memory, and real-world examples of deployed persistent agents. Helps you go from "I have the architecture" to "here's what it actually does for me." Activate on: "what can an always-on agent do", "persistent agent use cases", "agent applications", "proactive agent ideas", "what to build with episodic memory", "always-on agent product", "personal AI assistant ideas", "/always-on-agent-applications". NOT for: building the architecture (use always-on-agent-architecture), designing inputs (use always-on-agent-inputs), safety and privacy (use always-on-agent-safety).
allowed-tools	["Read","Write","Edit","Bash","Glob","Grep","Task","WebSearch","WebFetch"]
metadata	{"category":"AI & Agents","tags":["always-on","applications","use-cases","proactive-agents","personal-assistant","product-ideas","emergent-capabilities"],"pairs-with":[{"skill":"always-on-agent-architecture","reason":"Architecture is the foundation; applications are what you build on it"},{"skill":"always-on-agent-safety","reason":"Every application has safety implications that must be designed in"},{"skill":"tech-entrepreneur-coach-adhd","reason":"Many applications are product opportunities worth evaluating"},{"skill":"agentic-patterns","reason":"Application design requires solid agent loop fundamentals"}]}
category	Agent & Orchestration
tags	["always","agent","applications","ai","workflow","design"]

/always-on-agent-applications — What Persistence + Memory Actually Unlocks

You are helping someone figure out what to build with an always-on AI agent that has episodic memory. This is the "so what?" skill — the architecture exists, the inputs are flowing, now what does it actually do that a stateless chatbot can't?

Decision Points

1. Always-On vs Session-Based Decision Tree

Evaluate task requirements:
├─ Task needs memory across sessions?
│  └─ No → Use session-based agent (cheaper, simpler)
│  └─ Yes ↓
├─ Task benefits from proactive behavior?
│  └─ No → Use scheduled agent with memory
│  └─ Yes ↓
├─ [Persistence ROI] > [Infrastructure Cost]?
│  └─ No → Start with session-based, upgrade later
│  └─ Yes ↓
├─ Domain narrow enough for quality memory?
│  └─ No → Narrow scope (meetings-only, code-only)
│  └─ Yes → Build always-on agent

ROI Calculation:

• Persistence ROI = (Task frequency × Time saved per task × User value per hour)
• Infrastructure Cost = (Server cost + Memory storage + Development time)

If ROI > 3x cost: Build always-on If ROI 1-3x cost: Start session-based, prove value first If ROI < 1x cost: Use existing tools

2. Application Category Selection

User asks "What should I build?":
├─ Primary workflow is coding?
│  └─ Yes → Developer Companion pattern
│  └─ No ↓
├─ Primary need is meeting/communication overhead?
│  └─ Yes → Personal Chief of Staff pattern
│  └─ No ↓
├─ Primary goal is learning/knowledge work?
│  └─ Yes → Learning Journal pattern
│  └─ No ↓
├─ Focus is health/habits tracking?
│  └─ Yes → Health Observer pattern (high safety sensitivity)
│  └─ No → Project Orchestrator or Ambient Intelligence

3. Scope Boundaries Decision

User proposes multi-domain agent:
├─ Is this their first persistent agent?
│  └─ Yes → Force single vertical (pick strongest ROI)
│  └─ No ↓
├─ Do they have >6 months development time?
│  └─ No → Single vertical only
│  └─ Yes ↓
├─ Can they define success metrics for each domain?
│  └─ No → Reduce scope until they can
│  └─ Yes → Allow multi-domain with staged rollout

4. Proactive Behavior Calibration

Configure agent interruption frequency:
├─ User work style is deep focus blocks?
│  └─ Yes → Batch notifications, respect focus signals
│  └─ No ↓
├─ User explicitly requests high-touch assistance?
│  └─ Yes → Allow real-time interruptions with relevance threshold
│  └─ No ↓
├─ Default to: 80% reactive, 15% passive proactive, 5% active proactive

Failure Modes

1. Hallucinated Memory Syndrome

Symptoms: Agent confidently references conversations or events that never happened : If agent claims specific quotes/dates/facts but can't provide exact source timestamp : Poor memory boundaries between retrieved context and generated responses : Implement strict memory citation requirements - agent must link every claim to specific memory entry with timestamp