Jaegis Agent

Enhanced Multi-agent Architecture & Dependency Specialist

A perpetual, active background monitor for project codebases that identifies, analyzes, and reports on dependencies affected by code modifications. e.J.A.E.G.I.S. ensures architectural integrity by autonomously creating and assigning tasks to the appropriate agents or human team members responsible for affected code segments.

🎯 Key Features

βœ… Environment Agnostic: Operates identically on local machines and remote CI/CD infrastructure βœ… Proactive Prevention: Identifies potential integration conflicts before they become bugs βœ… Seamless Integration: Functions as background process with minimal developer overhead βœ… Single Source of Truth: Version-controlled ownership ledger ensures clear accountability βœ… Real-time Monitoring: Instant detection and analysis of code changes βœ… Intelligent Impact Analysis: LLM-powered semantic analysis of code dependencies

πŸ—οΈ System Architecture

e.J.A.E.G.I.S. consists of five core, interconnected components:

Component
Capability
Implementation

Codebase Knowledge Graph

Real-time model of project architecture and dependencies

Neo4j graph database or in-memory representation

Ownership Ledger

Definitive registry mapping code components to owners

Version-controlled OWNERSHIP_LEDGER.json file

Active Monitoring Service

Dual-mode change detection service

File system watcher (local) + webhook service (remote)

Impact Analysis Engine

Core logic for tracing "ripple effects" of changes

Graph traversal + LLM-powered semantic analysis

Task Dispatch Router

Central hub for notifications and task routing

Multi-channel notification system (IDE, Slack, email)

πŸš€ Quick Start

Installation

# Install e.J.A.E.G.I.S.
pip install eJaegis-agent

# Or install from source
git clone https://github.com/JAEGIS-method/eJaegis-agent.git
cd eJaegis-agent
pip install -e .

Initialize Your Project

Basic Usage

πŸ“‹ Configuration

Ownership Ledger

e.J.A.E.G.I.S. uses a version-controlled OWNERSHIP_LEDGER.json file to map code components to their owners:

Contact Methods

  • ide_notification: Popup notifications in your IDE

  • slack: Slack channel or DM notifications

  • email: Email notifications

  • webhook: Custom webhook integration

πŸ”„ How It Works

1. Continuous Monitoring

e.J.A.E.G.I.S. watches your codebase for changes using efficient file system monitoring.

2. Instant Analysis

When a file changes, e.J.A.E.G.I.S.:

  • Updates the knowledge graph

  • Identifies all dependent components

  • Analyzes the impact level (low/medium/high/critical)

3. Smart Notifications

For each affected component, e.J.A.E.G.I.S.:

  • Finds the responsible owner from the ledger

  • Generates specific, actionable tasks

  • Sends notifications via the owner's preferred method

4. Example Workflow

πŸ› οΈ Advanced Features

Neo4j Integration

For large projects, e.J.A.E.G.I.S. can use Neo4j for advanced graph operations:

LLM-Powered Analysis

e.J.A.E.G.I.S. can integrate with LLMs for semantic code analysis:

CI/CD Integration

e.J.A.E.G.I.S. works in CI/CD environments via webhooks:

πŸ“Š Supported Languages

e.J.A.E.G.I.S. provides intelligent analysis for:

  • Python (Full AST analysis)

  • JavaScript/TypeScript (Import/export analysis)

  • Java (Package and class analysis)

  • C/C++ (Header and include analysis)

  • Go (Module and package analysis)

  • Rust (Crate and module analysis)

  • Ruby (Gem and module analysis)

  • Generic (Basic file-level tracking)

πŸ”§ IDE Integration

e.J.A.E.G.I.S. integrates with popular IDEs through Language Server Protocol:

VS Code

JetBrains IDEs

Install the e.J.A.E.G.I.S. plugin from the marketplace.

Vim/Neovim

Use the e.J.A.E.G.I.S. LSP client configuration.

🚨 Troubleshooting

Common Issues

e.J.A.E.G.I.S. not detecting changes:

Neo4j connection issues:

Permission errors:

Debug Mode

🀝 Contributing

We welcome contributions! Please see our Contributing Guide.

Development Setup

πŸ“„ License

MIT License - see LICENSE file for details.


e.J.A.E.G.I.S. - Ensuring your codebase architecture stays intact, one dependency at a time. πŸ›‘οΈ

Last updated