memory
Persistent Memory System
Overview
Memory lives in .aiter/memory/ relative to the project root. Each file has a specific format and purpose. Files use Markdown with YAML frontmatter for metadata.
Core principle: Memory files are the single source of truth for agent state. All agents (orchestrator, heartbeat, support-responder, monitor) read and write to the same memory files. This enables cross-layer composability.
Directory Structure
.aiter/
└── memory/
├── tasks.md # Pending, in-progress, completed tasks
├── knowledge.md # Learned facts and preferences
├── contacts.md # IM channels and people
├── journal.md # Activity log
More from within-7/aiter
notifications
Multi-target notification system. Send app, IM, and webhook notifications with priority levels, quiet hours, and history tracking.
2tunnels
Tunnel lifecycle management. Create, monitor, and close tunnels for sharing local services publicly. Integrate with file servers for report and preview sharing.
1aiter-control
Control AiTer terminal client via CLI commands. Create projects, manage terminals, read/write terminal output, and coordinate multi-agent workflows.
1reporting
Report generation and distribution. Gather data from multiple sources, format structured reports, and distribute via IM, notifications, or shared tunnel URLs.
1orchestration
Multi-project orchestration patterns. Plan format, inter-agent communication protocol, dispatch workflow, task templates, monitoring loops, and persistent state tracking via memory files.
1platform-core
Foundation skill for the AiTer Agent Platform. Provides identity framework, autonomous decision rules, environment detection, full AiTer CLI command reference across all 11 namespaces, and persistent memory basics.
1