Issues Amplifier Bundle

Persistent issue tracking for Amplifier sessions with dependency management and priority-based scheduling.

What This Provides

• issue_manager tool - Create, list, update, and close issues with dependencies
• issue-aware bundle - Pre-configured session with issue management enabled

Usage

Quick Start

Add the issues bundle to your app configuration (always available):

amplifier bundle add git+https://github.com/microsoft/amplifier-bundle-issues@main --app

That's it! The issue manager is now available in all your Amplifier sessions.

Alternative: Per-Project Activation

If you prefer to enable issues only for specific projects:

# Add the bundle to your registry
amplifier bundle add git+https://github.com/microsoft/amplifier-bundle-issues@main

# Set it as active for the current project
amplifier bundle use issues

# Start an interactive session
amplifier

Then interact with issues:

You: "Create an issue to implement user authentication"
Assistant: [Creates issue with the issue_manager tool]

You: "What can I work on?"
Assistant: [Lists ready issues with get_ready operation]

You: "Work on issue <id>"
Assistant: [Updates status to in_progress and begins work]

Include in Another Bundle

Add to your bundle's includes: section:

includes:
  - bundle: git+https://github.com/microsoft/amplifier-bundle-issues@main

Manual Configuration

Add the tools to your own bundle:

tools:
  - module: tool-issue
    source: git+https://github.com/microsoft/amplifier-bundle-issues@main#subdirectory=modules/tool-issue
    config:
      data_dir: ~/.amplifier/projects/{project}/issues
      auto_create_dir: true
      actor: assistant

hooks:
  - module: hook-issue-auto-work
    source: git+https://github.com/microsoft/amplifier-bundle-issues@main#subdirectory=modules/hook-issue-auto-work
    config:
      priority: 100
      max_auto_iterations: 10
      inject_role: system

  - module: hook-issue-session-end
    source: git+https://github.com/microsoft/amplifier-bundle-issues@main#subdirectory=modules/hook-issue-session-end
    config:
      priority: 90

Then add instructions in your bundle context similar to what is found in the bundle.md.

Data Storage

Issues are stored in your home directory under a project-specific path:

~/.amplifier/
└── projects/
    └── {project}/
        └── issues/
            ├── issues.jsonl          # Issue records
            ├── dependencies.jsonl    # Issue relationships
            └── events.jsonl          # Change history

The {project} placeholder is automatically derived from your working directory.

This can be configured in your bundle (see the Manual Configuration section).

Issue Operations

The issue_manager tool supports:

• create - New issue with priority and type
• list - Filter by status, priority, assignee
• get - Show issue details
• update - Change status, priority, blocking notes
• close - Mark complete with reason
• add_dependency - Link issues with dependencies
• remove_dependency - Remove dependency links
• get_ready - Find work with no blockers
• get_blocked - See blocked issues
• get_sessions - Get all Amplifier sessions linked to an issue

Issue States

• open - Created, not yet started
• in_progress - Actively being worked on
• blocked - Waiting on dependencies
• closed - Completed
• completed - Done (alias: done)
• pending_user_input - Waiting for user response (alias: waiting)

Session Linking

Issues are automatically linked to Amplifier sessions. Every operation (create, update, close, etc.) records the session ID, enabling you to:

• Track which sessions worked on an issue - See the full history of sessions that touched an issue
• Resume sessions for follow-up questions - Use amplifier session resume <session_id> to revive context
• Understand issue history - See what each session did (created, updated, closed, etc.)

Query linked sessions:

You: "What sessions have worked on issue X?"
Assistant: [Uses get_sessions operation to show linked sessions]

You: "Resume the session that created this issue"
Assistant: [You can run: amplifier session resume <session_id>]

Priorities

• 0 - Critical
• 1 - High
• 2 - Normal (default)
• 3 - Low
• 4 - Deferred

Contributing

Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Contributor License Agreements.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.