Skip to content

Conversation

@lotif
Copy link
Collaborator

@lotif lotif commented Feb 9, 2026

Summary

Switching the sqlite connection to a SQLAlchemy connection to take advantage of it being agnostic of database and the read only database connection implementation

Clickup Ticket(s): Link(s) if applicable.

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📝 Documentation update
  • 🔧 Refactoring (no functional changes)
  • ⚡ Performance improvement
  • 🧪 Test improvements
  • 🔒 Security fix

Changes Made

  • Added report generation and AML DB connections to the client manager
  • Refactored all the report generation scripts
  • Small refactoring on a couple of AML investigation agent functions

Testing

  • Tests pass locally (uv run pytest tests/)
  • Type checking passes (uv run mypy <src_dir>)
  • Linting passes (uv run ruff check src_dir/)
  • Manual testing performed (describe below)

Manual testing details:

Tested the Report Generation demo UI and the evaluation script

Checklist

  • Code follows the project's style guidelines
  • Self-review of code completed
  • Documentation updated (if applicable)
  • No sensitive information (API keys, credentials) exposed

@lotif lotif requested review from amrit110 and fcogidi February 9, 2026 22:22
@lotif lotif changed the title Report Generation Agent: sqitching to sqlalchemy Report Generation Agent: switching to sqlalchemy Feb 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant