### Configure Automation Output

Source: https://docs.nimbalyst.com/session-management/automations

Example configuration for defining how automation results are saved to the filesystem.

```yaml
output:
  mode: new-file
  location: nimbalyst-local/automations/standup-summary/
  fileNameTemplate: "{{date}}-output.md"
```

--------------------------------

### Configure Automation Schedules

Source: https://docs.nimbalyst.com/session-management/automations

Examples of different schedule types for automation execution.

```yaml
schedule:
  type: daily
  time: "09:00"
```

```yaml
schedule:
  type: weekly
  days: [mon, wed, fri]
  time: "14:00"
```

```yaml
schedule:
  type: interval
  intervalMinutes: 60
```

--------------------------------

### Import Mermaid Diagram Syntax

Source: https://docs.nimbalyst.com/visual-editors-powered-by-ai/excalidraw

Example of Mermaid syntax that can be imported into the Excalidraw editor.

```mermaid
graph TD
    A[Start] --> B{Decision}
    B -->|Yes| C[Action]
    B -->|No| D[End]
```

--------------------------------

### Create Automation via Slash Command

Source: https://docs.nimbalyst.com/session-management/automations

Use the slash command to quickly generate a new automation file with a default configuration.

```text
/automation summarize my git commits every weekday morning
```

--------------------------------

### Define Automation File Structure

Source: https://docs.nimbalyst.com/session-management/automations

The standard format for an automation file, including YAML frontmatter for scheduling and output settings, followed by the prompt body.

```markdown
---
automationStatus:
  id: standup-summary
  title: Daily Standup Summary
  enabled: false
  schedule:
    type: weekly
    days: [mon, tue, wed, thu, fri]
    time: "09:25"
  output:
    mode: new-file
    location: nimbalyst-local/automations/standup-summary/
    fileNameTemplate: "{{date}}-standup.md"
  runCount: 0
---

# Daily Standup Summary

Review the git log and recent file changes in this workspace since the previous business day. Summarize:

1. **What was accomplished** - List completed work based on commits and file changes
2. **What's in progress** - Identify files with uncommitted changes or recent branches
3. **Any blockers** - Note any error logs, failing tests, or stale branches

Format as a concise standup update suitable for sharing with the team.
```

--------------------------------

### Weekly Project Status Report Automation

Source: https://docs.nimbalyst.com/session-management/automations

Configure a weekly automation to generate a project status report. Ensure the schedule and output settings are appropriate for your needs.

```markdown
---
automationStatus:
  id: weekly-status
  title: Weekly Project Status
  enabled: true
  schedule:
    type: weekly
    days: [fri]
    time: "16:00"
  output:
    mode: new-file
    location: nimbalyst-local/automations/weekly-status/
    fileNameTemplate: "{{date}}-status.md"
  runCount: 0
---

# Weekly Project Status

Generate a weekly status report for this project:

1. **Summary** - One paragraph overview of the week's progress
2. **Completed** - List all merged PRs and completed features this week (check git log)
3. **In Progress** - List open branches and their status
4. **Metrics** - Count commits, files changed, and lines added/removed
5. **Next Week** - Based on open branches and TODOs, suggest priorities

Format as a clean markdown report.
```

--------------------------------

### Specify AI Provider and Model

Source: https://docs.nimbalyst.com/session-management/automations

Optional configuration to override the default AI provider and model for an automation.

```yaml
provider: claude-code    # "claude-code", "claude", or "openai"
model: claude-code:sonnet # optional: specific model ID
```

--------------------------------

### Define Tracking Item Structure

Source: https://docs.nimbalyst.com/task-management/inline-and-chat-item-tracking

Use this YAML structure to define the metadata for tracked items, including status, priority, and assignment details.

```yaml
---
trackingStatus:
  itemId: [type]-[unique-id]        # e.g., bug-001, task-042, idea-015
  title: [Short Description]
  type: [bug|task|idea]
  status: [status]                   # See status values below
  priority: [priority]               # low | medium | high | critical
  assignee: [username]               # Person responsible
  tags:                              # Relevant tags
    - [tag1]
    - [tag2]
  created: "YYYY-MM-DD"
  updated: "YYYY-MM-DDTHH:MM:SS.sssZ"
  resolvedDate: "YYYY-MM-DD"         # When resolved (optional)
---
```

--------------------------------

### Define Session Data Structure

Source: https://docs.nimbalyst.com/open-safe-private-secure/session-and-window-state-storage

Represents the schema for the ai_sessions table stored in the local PGLite database.

```typescript
{
  id: string;              // Unique session ID
  workspacePath: string;   // Workspace this session belongs to
  provider: string;        // AI provider (claude, openai, etc.)
  model: string;           // Model ID
  sessionType: string;     // 'chat' or 'agent'
  messages: Message[];     // Conversation history
  documentContext: object; // Document that was active
  metadata: object;        // Custom metadata
  title: string;           // Session name
  draftInput: string;      // Unsaved user input
  createdAt: number;       // Creation timestamp
  updatedAt: number;       // Last update timestamp
}
```

--------------------------------

### Query Automation History

Source: https://docs.nimbalyst.com/session-management/automations

Natural language command to request run history from the AI agent.

```text
What's the run history for my standup-summary automation?
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.