Wednesday, September 16, 2026

How I Use AI Agents as a Data Scientist in 2026

 

How I Use AI Agents as a Data Scientist in 2026

Artificial intelligence is changing the way data scientists work. In 2026, AI agents are becoming useful partners for tasks that previously required hours of manual effort, from exploring datasets and writing code to monitoring machine-learning experiments and preparing reports.

An AI agent is more than a chatbot that answers questions. An agent can receive a goal, break it into smaller tasks, use tools, examine results, and take further actions based on what it discovers. For data scientists, this creates an opportunity to automate repetitive parts of the analytical workflow while keeping humans responsible for important decisions.

Here is how I would use AI agents throughout a modern data-science workflow.

1. Starting With a Data Question

Every data-science project begins with a question.

For example:

“Why did customer churn increase during the last quarter?”

Instead of immediately opening a notebook and manually exploring dozens of columns, I can give an AI agent a clearly defined analytical objective.

The agent can help turn the broad question into smaller tasks:

  • Identify relevant datasets.
  • Examine available columns.
  • Check data quality.
  • Calculate important statistics.
  • Look for unusual patterns.
  • Suggest possible hypotheses.
  • Prepare an initial analysis plan.

This does not mean accepting the agent's plan automatically. I treat it as a starting point and verify whether the proposed approach makes sense for the business problem.

2. Data Discovery and Profiling

Finding useful information in large datasets can consume significant time.

An AI agent can assist by examining schemas and generating a data profile containing information such as:

  • Number of rows and columns
  • Data types
  • Missing values
  • Duplicate records
  • Unique categories
  • Numerical distributions
  • Potential outliers
  • Relationships between variables

For example, if a dataset contains customer information, an agent might identify columns such as customer_id, subscription_type, monthly_spend, login_frequency and churn_status.

The agent can then suggest which variables may deserve further investigation.

However, I still verify the results because automated profiling can misunderstand the meaning of a column or overlook domain-specific problems.

3. Cleaning Data With AI Assistance

Data cleaning is one of the most time-consuming parts of data science.

AI agents can help generate code for common operations such as:

df = df.drop_duplicates()

df["age"] = df["age"].fillna(df["age"].median())

df["category"] = df["category"].str.strip().str.lower()

An agent can also identify suspicious values and suggest possible treatments.

For example, if most customer ages are between 18 and 80 but some records contain values such as 250, the agent can flag them for investigation.

The important distinction is that flagging a problem and deciding how to fix it are different tasks.

I would not allow an agent to blindly modify an important production dataset. Instead, I review the proposed transformations and maintain reproducible data-cleaning code.

4. Generating Exploratory Data Analysis

Exploratory data analysis, or EDA, helps uncover patterns before building a model.

AI agents can generate Python code for:

  • Histograms
  • Scatter plots
  • Correlation matrices
  • Box plots
  • Time-series charts
  • Grouped statistics
  • Distribution comparisons

For example:

import matplotlib.pyplot as plt

plt.hist(df["monthly_spend"])
plt.xlabel("Monthly Spend")
plt.ylabel("Customers")
plt.title("Customer Spending Distribution")
plt.show()

The agent can also suggest which visualisations might answer a particular analytical question.

This can speed up experimentation considerably. But visual interpretation remains important. A chart may reveal a correlation without proving that one variable causes another.

5. Writing and Debugging Python

One of my most practical uses for AI agents is programming assistance.

Instead of spending a long time searching for a syntax error, I can provide the agent with:

  • The code
  • The error message
  • The expected result
  • Relevant information about the dataset

The agent can then explain the problem and propose a correction.

It can also help create reusable functions, SQL queries and data-processing pipelines.

For example, I might ask an agent to create a function that calculates customer retention by month. I can then test the generated code against known results.

The agent becomes a coding assistant rather than an unquestioned programmer.

6. Working With SQL

Many data-science projects involve databases containing millions or billions of records.

AI agents can translate analytical questions into SQL.

For example:

SELECT
    subscription_type,
    COUNT(*) AS customers,
    AVG(monthly_spend) AS average_spend
FROM customers
GROUP BY subscription_type;

An agent can also explain complicated queries and suggest ways to improve readability or performance.

For large production systems, however, I would validate the generated query carefully. A syntactically correct query can still produce the wrong business result.

7. Feature Engineering

Feature engineering involves transforming raw information into useful model inputs.

An AI agent can suggest possible features based on the structure of a dataset.

For a customer-churn problem, examples could include:

  • Days since last login
  • Average monthly usage
  • Number of support requests
  • Spending trend
  • Subscription duration

The agent can generate candidate features and code for calculating them.

But feature selection should involve domain knowledge and statistical validation. Creating hundreds of automatically generated features can increase complexity and potentially introduce leakage or overfitting.

8. Building Machine-Learning Experiments

AI agents can also help organise machine-learning experiments.

Given a classification problem, an agent might prepare experiments involving:

  • Logistic regression
  • Decision trees
  • Random forests
  • Gradient boosting
  • Neural networks

It can create training scripts, evaluation functions and experiment configurations.

A simplified workflow could look like:

Dataset → Cleaning → Feature Engineering → Train/Test Split → Model Training → Evaluation → Experiment Tracking

The agent can automate repetitive portions of this process while I focus on interpreting the results.

9. Comparing Model Performance

When several models are trained, an AI agent can collect evaluation metrics and create comparison tables.

For classification, these might include:

  • Accuracy
  • Precision
  • Recall
  • F1 score
  • ROC-AUC

For regression:

  • MAE
  • MSE
  • RMSE

The agent can explain differences between experiments and identify which models deserve additional investigation.

Importantly, I don't select a model purely because an agent says it is “best.” The appropriate metric depends on the actual problem, business costs and consequences of errors.

10. Automating Repetitive Analysis

One of the biggest advantages of agents is their ability to handle multi-step workflows.

For example, a weekly sales-analysis agent could:

  1. Retrieve the latest approved dataset.
  2. Check for data-quality issues.
  3. Calculate predefined metrics.
  4. Generate charts.
  5. Compare results with previous periods.
  6. Flag unusual changes.
  7. Prepare a draft report.

This turns a repetitive manual workflow into a semi-automated process.

The human still reviews important outputs before they are distributed.

11. Monitoring Machine-Learning Models

Deploying a model is not the end of a data-science project.

Model performance can change as real-world data changes. AI agents can assist with monitoring by checking predefined indicators such as:

  • Prediction distributions
  • Input-data drift
  • Missing-value rates
  • Model performance
  • Error rates
  • Data pipeline failures

If an unusual change occurs, an agent can summarise what happened and create an alert for the responsible team.

For critical applications, automated alerts should not automatically trigger consequential decisions without appropriate human oversight.

12. Research and Documentation

Data scientists spend considerable time reading technical documentation and research papers.

AI agents can help organise this information by summarising concepts, comparing approaches and extracting implementation requirements.

For example, when investigating a new machine-learning technique, I can ask an agent to structure my research around:

  • What problem does the method solve?
  • What data does it require?
  • What assumptions does it make?
  • How computationally expensive is it?
  • What are its limitations?
  • How could it be tested?

This makes research more structured, although original papers and authoritative documentation should remain the source of truth for important technical details.

13. Creating Data Reports

Once an analysis is complete, communicating the results is just as important as performing the analysis.

An AI agent can help convert analytical outputs into a structured report containing:

  • Executive summary
  • Key findings
  • Supporting charts
  • Important limitations
  • Recommended areas for further investigation

I still check every important number before publishing the report. AI systems can occasionally produce plausible-looking statements that are not supported by the underlying data.

14. Using Agents Without Losing Control

The most important lesson is that AI agents should assist data scientists rather than replace analytical judgement.

I use a simple principle:

AI generates → AI checks → Human verifies → Human decides

This approach is especially important when working with sensitive information.

Before giving an agent access to a dataset, I consider:

  • Does the agent actually need the data?
  • Is personal information included?
  • Where will the data be processed?
  • Who can access the generated results?
  • What permissions does the agent have?
  • Can its actions be audited or reversed?

Limiting permissions is particularly important for autonomous systems.

15. My 2026 Data-Science Agent Workflow

A practical workflow can look like this:

Step 1: Define the analytical question.

Step 2: Give the agent access only to the required data and tools.

Step 3: Ask it to inspect and profile the dataset.

Step 4: Review the proposed data-cleaning process.

Step 5: Generate EDA code and visualisations.

Step 6: Develop candidate features.

Step 7: Run controlled machine-learning experiments.

Step 8: Evaluate the results using appropriate metrics.

Step 9: Ask the agent to document the experiment.

Step 10: Human review and final interpretation.

This workflow allows AI to handle repetitive tasks while keeping analytical responsibility with the data scientist.

Benefits of AI Agents for Data Scientists

The main advantages I see are:

Faster experimentation

Agents can generate boilerplate code and analytical workflows quickly.

Less repetitive work

Routine profiling, reporting and documentation can be partially automated.

Better accessibility

People can describe analytical goals in natural language before converting them into SQL or Python.

More systematic workflows

Agents can follow predefined procedures for recurring tasks.

Faster debugging

Coding errors and failed experiments can often be investigated conversationally.

Challenges to Keep in Mind

AI agents are powerful, but they are not automatically reliable.

Potential problems include:

  • Incorrect generated code
  • Misinterpretation of data
  • Hallucinated explanations
  • Poor statistical assumptions
  • Data leakage
  • Security risks
  • Privacy concerns
  • Excessive automation
  • Reproducibility problems

A particularly dangerous situation is when an agent produces a convincing explanation for an incorrect result.

That is why testing, validation and human review remain essential.

Conclusion

In 2026, I see AI agents as an additional layer in the data scientist's toolkit. They can help with data exploration, Python programming, SQL, feature engineering, machine-learning experiments, monitoring, research and reporting.

The biggest productivity gain does not necessarily come from allowing an agent to do everything autonomously. Instead, it comes from assigning agents well-defined tasks, giving them appropriate tools and permissions, and continuously checking their work.

The future data scientist may spend less time writing repetitive code and more time asking better questions, validating evidence, understanding business problems and making informed analytical decisions.

AI agents can automate parts of the workflow—but the responsibility for trustworthy data science still belongs to the human.

Top 5 Text-to-Speech Open-Source Models

 

Top 5 Text-to-Speech Open-Source Models

Text-to-speech (TTS) technology has changed rapidly with the development of modern artificial intelligence. Instead of producing robotic-sounding speech, newer AI models can generate voices with natural pronunciation, pauses, rhythm and expressive qualities.

Open-source and open-weight TTS models are particularly useful because developers can experiment with them locally, integrate them into applications and build customised speech systems without depending entirely on commercial APIs.

Here are five notable open-source or openly available TTS models worth exploring.

1. Kokoro

Kokoro is a lightweight text-to-speech model that has attracted considerable attention because of its combination of small size and speech quality. The model has 82 million parameters, making it considerably smaller than many large generative speech systems.

Kokoro's published model information lists Apache 2.0 licensing for its weights. The project has also provided ONNX versions, making it suitable for applications where efficient inference is important.

One of its interesting characteristics is that it can produce high-quality English speech without requiring a huge model. This makes Kokoro attractive for developers experimenting with local TTS applications.

Key features

  • 82 million parameters
  • Open-weight model
  • Apache 2.0-licensed weights
  • American and British English voices in the documented releases
  • ONNX support
  • Suitable for local and application-based TTS

Kokoro can be useful for narration, accessibility tools, educational applications and voice interfaces.

2. XTTS v2

XTTS v2 is a multilingual speech-generation model from the Coqui TTS ecosystem. It is particularly interesting for applications involving voice cloning and multilingual speech generation.

The model can use a short voice sample as a reference and generate speech that follows characteristics of that voice. This makes it useful for research into personalised speech interfaces, narration and conversational applications.

XTTS v2 is considerably larger than lightweight models such as Kokoro, with published comparisons listing approximately 467 million parameters.

Key features

  • Multilingual speech generation
  • Voice cloning capabilities
  • Speaker conditioning
  • Suitable for advanced TTS experiments
  • Can be integrated into Python-based workflows

Developers should carefully check the current model and voice licensing terms before using cloned voices commercially.

3. Piper

Piper takes a different approach from many large generative TTS models. It is designed around fast, local neural speech synthesis and is particularly useful when low resource consumption and offline operation are important.

The project provides a Python package and supports multiple platforms. Its available voice ecosystem covers numerous languages, although licensing can vary between individual voice models.

Because speech can be generated locally, Piper can be useful for applications where sending text to an external cloud service is undesirable.

Key features

  • Fast local speech synthesis
  • Offline operation
  • Python support
  • ONNX-based voice models
  • Large selection of language and voice models

Piper is a strong option for local assistants, accessibility software, embedded projects and other applications where efficiency matters.

4. Fish Speech

Fish Speech is a modern speech-generation project focused on producing natural and expressive synthetic speech. It has become part of the broader wave of open speech models that aim to approach the quality of commercial voice-generation systems.

The project's different releases and versions have changed over time, so developers should consult the current repository and model cards for the exact capabilities and licensing conditions of the version they intend to use.

Fish Speech can be particularly interesting for developers experimenting with expressive narration, multilingual systems and voice-related AI applications.

Key features

  • Neural speech generation
  • Expressive voice capabilities
  • Voice-related customisation
  • Research and application use
  • Open model ecosystem

As with other voice-cloning technologies, users should only work with voices and recordings for which they have appropriate permission.

5. Parler-TTS

Parler-TTS is an open text-to-speech project designed to generate speech from textual descriptions. Instead of simply selecting a predefined voice, users can describe characteristics of the desired speech, such as speaking style or voice attributes.

This makes the model interesting for researchers and developers who want greater control over generated speech.

Parler-TTS has also been used as an example of how open models can provide developers with more control over the speech-generation pipeline compared with closed commercial services.

Key features

  • Text-to-speech generation
  • Text-based voice descriptions
  • Customisable speech characteristics
  • Open research ecosystem
  • Useful for experimentation and prototyping

Its relatively large model size means hardware requirements should be considered before deploying it locally.

Open-Source TTS Models Compared

Model Main Strength Hardware Consideration Notable Use
Kokoro Lightweight, natural speech Relatively efficient Local TTS and narration
XTTS v2 Voice cloning and multilingual speech More demanding Personalised voice applications
Piper Fast local inference Lightweight Offline and edge applications
Fish Speech Expressive speech generation Depends on version Advanced speech experiments
Parler-TTS Controllable voice descriptions Relatively demanding Custom speech generation

Why Use Open-Source TTS?

Open TTS models provide several advantages over relying exclusively on cloud-based services.

1. Local Processing

Some models can run directly on a computer or other local hardware. This can reduce dependence on external APIs.

2. Greater Customisation

Developers can experiment with voices, inference settings and application workflows instead of being restricted to a fixed commercial interface.

3. Lower API Dependence

For projects generating large quantities of audio, local inference can eliminate or reduce per-character or per-minute API costs, although hardware and electricity still have costs.

4. Research Opportunities

Open models allow researchers and developers to examine architectures, experiment with fine-tuning and build new applications around speech synthesis.

5. Privacy Considerations

When a model operates locally, text does not necessarily need to be transmitted to a third-party cloud service. This can be useful for applications handling sensitive information, although the complete software stack should still be evaluated.

How to Choose the Right TTS Model

The best model depends on the project's requirements rather than simply the model's size.

If you want a relatively small model for local experimentation, Kokoro is worth investigating. If voice cloning and multilingual generation are central requirements, XTTS v2 may be more relevant.

For lightweight offline applications, Piper is particularly interesting. Developers experimenting with expressive speech can investigate Fish Speech, while Parler-TTS is notable for its text-based control over speech characteristics.

Before deploying any model commercially, check its current licence, the licence of the specific voice model, attribution requirements and any restrictions related to voice cloning.

Conclusion

Open-source text-to-speech technology is giving developers more choices for creating realistic and customisable voice applications. Models such as Kokoro, XTTS v2, Piper, Fish Speech and Parler-TTS demonstrate different approaches to speech synthesis, ranging from lightweight local inference to expressive and personalised voice generation.

The TTS landscape continues to evolve quickly. For developers, the most important factors are not just audio quality but also model size, supported languages, hardware requirements, inference speed, customisation options and licensing.

As open speech models continue to improve, they are likely to become increasingly useful for applications such as education, accessibility, digital assistants, content creation, software interfaces and AI-powered communication.

Tuesday, September 15, 2026

GDScript++: Exploring the Next Generation of Scripting for Game Development

 

GDScript++: Exploring the Next Generation of Scripting for Game Development

https://technologiesinternetz.blogspot.com


Game development has become more accessible than ever. Modern engines allow developers to create 2D and 3D games without building every technology from scratch. One of the languages closely associated with this movement is GDScript, the scripting language created for the Godot game engine.

The term “GDScript++” can be used informally to describe the idea of extending or modernizing GDScript with more powerful programming capabilities. It is important to clarify that GDScript++ is not an official programming language or official replacement for GDScript. GDScript itself remains the scripting language designed specifically for Godot.

With that distinction in mind, let's explore what a hypothetical or community-oriented “GDScript++” concept could mean and why developers may be interested in it.

What Is GDScript?

GDScript is a high-level programming language designed specifically for the Godot Engine.

Its syntax is influenced by languages such as Python, making it relatively approachable for beginners. The language integrates closely with Godot's scene system, nodes, signals and other engine features.

A simple GDScript example looks like this:

extends Node

func _ready():
    print("Hello, Godot!")

The extends Node line tells Godot that the script is attached to a Node-based object, while _ready() is called when the node enters the scene tree.

So, What Could GDScript++ Mean?

The “++” name suggests an enhanced version of an existing language.

In a hypothetical GDScript++ environment, developers might expect features such as:

  • More advanced type checking
  • Better performance
  • Improved tooling
  • Stronger object-oriented programming support
  • Better code organization
  • Enhanced debugging
  • More sophisticated generics
  • Improved interoperability with native code

However, these should be viewed as possible design ideas rather than official GDScript++ features.

GDScript itself has already evolved considerably, including optional static typing and other language improvements.

Why Would Developers Want an Enhanced GDScript?

Game development can involve thousands of lines of code.

A small project might contain scripts for:

  • Player movement
  • Enemy AI
  • Weapons
  • Inventory systems
  • Menus
  • Audio
  • Saving and loading
  • Multiplayer
  • Physics
  • Quests

As a project becomes larger, developers need tools that make code easier to maintain.

An enhanced scripting approach could potentially provide stronger safeguards while retaining the simplicity that makes GDScript attractive.

Static Typing

One of the most useful features available in modern GDScript is static typing.

For example:

var player_health: int = 100
var player_name: String = "Hero"
var speed: float = 5.0

Types tell the engine and the developer what kind of data a variable is expected to contain.

A function can also specify parameter and return types:

func calculate_damage(power: int, bonus: int) -> int:
    return power + bonus

This can make larger projects easier to understand and can help catch certain mistakes earlier.

Object-Oriented Game Programming

Game engines naturally involve objects.

A player can be represented by one object, an enemy by another, and a weapon by another.

A simple class might look like:

class_name Player

var health: int = 100
var speed: float = 200.0

func take_damage(amount: int) -> void:
    health -= amount

Other scripts can then interact with the Player class.

This approach makes it easier to organize complicated game systems.

Performance Matters in Games

Games often need to perform many operations every frame.

For example, a game running at 60 frames per second has approximately:

1000 ÷ 60 ≈ 16.7 milliseconds

available for each frame.

That time may need to cover rendering, physics, animation, input processing, audio and game logic.

This is why performance becomes increasingly important as games become more sophisticated.

An enhanced scripting model could focus on reducing unnecessary overhead while retaining developer-friendly syntax.

GDScript and Native Languages

Godot supports more than one programming approach.

Developers can use GDScript for general game logic while using other technologies where lower-level performance or specialized functionality is required.

A hypothetical GDScript++ ecosystem could potentially make this interaction more seamless.

For example:

GDScript
   ↓
Game Logic
   ↓
GDScript++-style Advanced Systems
   ↓
Native / Engine-Level Code
   ↓
Godot Engine

The idea would be to allow developers to choose the appropriate level of abstraction for each part of a game.

Better Developer Tools

Modern programming is not only about the language itself. Development tools are equally important.

An advanced GDScript ecosystem could emphasize:

  • Intelligent code completion
  • Static analysis
  • Better error messages
  • Refactoring tools
  • Performance profiling
  • Debugging support
  • Documentation integration
  • Automatic code suggestions

These features can save developers considerable time during large projects.

GDScript for Beginners

One of GDScript's biggest advantages is its relatively simple syntax.

For example:

var score: int = 0

func add_score(points: int) -> void:
    score += points

Even someone learning programming for the first time can understand the basic structure.

This makes GDScript particularly useful for students and aspiring game developers.

Building a Simple Player Script

Here is a basic example:

extends CharacterBody2D

@export var speed: float = 250.0

func _physics_process(delta: float) -> void:
    var direction := Input.get_vector(
        "ui_left",
        "ui_right",
        "ui_up",
        "ui_down"
    )

    velocity = direction * speed
    move_and_slide()

The script reads player input, calculates a movement direction and moves the character.

Although this example is small, the same principles can be expanded into much larger game systems.

Where an Advanced GDScript Could Be Useful

An enhanced scripting concept could be particularly valuable for projects such as:

Indie Games

Small development teams need languages that allow rapid development without creating excessive complexity.

2D Games

Godot is particularly popular for 2D development, where scripting handles gameplay mechanics, characters and interactions.

3D Games

Larger 3D projects can benefit from strong code organization and performance-conscious scripting.

Educational Projects

A simple syntax can help students learn programming through game creation.

Prototypes

Developers can quickly test gameplay ideas before investing in complex systems.

GDScript++ and AI-Powered Game Development

Another interesting possibility is combining game scripting with AI-assisted development.

AI coding assistants can help developers:

  • Generate basic scripts
  • Explain errors
  • Create gameplay prototypes
  • Suggest optimizations
  • Generate boilerplate code
  • Explain unfamiliar APIs

For example, a developer could describe:

“Create an enemy that follows the player but stops when it reaches a certain distance.”

An AI assistant could generate a starting GDScript implementation.

The developer would still need to test, understand and modify the generated code.

A Possible Future Architecture

A future game-development workflow might look like this:

Game Design
     ↓
AI-Assisted Development
     ↓
GDScript
     ↓
Advanced Typed Systems
     ↓
Godot Engine
     ↓
2D / 3D Game

Such a workflow could make sophisticated game development accessible to a wider range of creators.

Is GDScript++ a Real Replacement for GDScript?

No official GDScript++ replacement should be assumed simply because the term appears in articles, repositories or online discussions.

If you encounter the term “GDScript++,” check the specific project's documentation to determine whether it refers to:

  • A community project
  • A proposed language extension
  • A personal programming experiment
  • A tool or framework
  • A misunderstanding of GDScript's existing features

For actual Godot development, learning GDScript is the appropriate starting point.

Conclusion

The idea of GDScript++ represents an interesting vision: combining the simplicity of GDScript with stronger typing, better tooling, improved performance and more advanced programming capabilities.

However, it should not be confused with an official successor to GDScript. Developers interested in Godot should focus on learning modern GDScript and the Godot architecture first.

As game engines continue to evolve, scripting languages will likely become more powerful while remaining accessible. Whether through future improvements to GDScript, community tools or AI-assisted development, the goal remains the same: help developers turn game ideas into playable experiences faster and with less unnecessary complexity.

Combining Traditional Machine Learning with Agentic Reasoning: A Practical AI Architecture

 

Combining Traditional Machine Learning with Agentic Reasoning: A Practical AI Architecture

Artificial intelligence is moving beyond systems that simply make predictions. Modern AI applications are increasingly expected to understand a problem, make decisions, use tools, evaluate results, and take multiple steps toward a goal.

This is where agentic AI becomes important.

However, that does not mean traditional machine learning has become obsolete. In many real-world applications, classical machine-learning models remain excellent at specific tasks such as fraud detection, demand forecasting, classification, anomaly detection, recommendation, and risk scoring.

A powerful approach is therefore to combine traditional machine learning with agentic reasoning.

Instead of asking an AI agent to perform everything itself, developers can give it access to specialized ML models and allow the agent to decide when and how those models should be used.

What Is Traditional Machine Learning?

Traditional machine learning focuses primarily on learning patterns from historical data and producing predictions or classifications.

Common algorithms include:

  • Linear and logistic regression
  • Decision trees
  • Random forests
  • Gradient boosting
  • Support vector machines
  • K-means clustering
  • XGBoost
  • Neural networks

For example, imagine an online store wants to predict whether an order is potentially fraudulent.

A machine-learning model can examine features such as:

  • Transaction value
  • Customer history
  • Location
  • Device information
  • Purchase frequency
  • Previous chargebacks

The model might return:

Fraud probability: 0.87

This is extremely useful, but the model generally does not decide what should happen next.

An agentic system can take that prediction and reason about the next action.

What Is Agentic Reasoning?

Agentic reasoning refers to an AI system that can work toward a goal through multiple steps.

Instead of producing only one prediction, an agent can:

  1. Understand the user's objective.
  2. Break the problem into smaller tasks.
  3. Select appropriate tools.
  4. Collect additional information.
  5. Run models or queries.
  6. Evaluate the results.
  7. Decide what to do next.
  8. Produce an outcome.

For example:

"Investigate why sales dropped last month and recommend actions."

An agent might:

  • Retrieve sales data.
  • Ask a forecasting model for expected sales.
  • Compare actual and predicted values.
  • Run an anomaly detector.
  • Check inventory information.
  • Analyze customer segments.
  • Identify possible causes.
  • Recommend corrective actions.

The traditional ML models provide specialized intelligence, while the agent provides coordination and decision-making.

Why Combine the Two?

Traditional ML and agentic AI solve different parts of a problem.

Traditional ML Agentic AI
Excellent at prediction Excellent at task orchestration
Works with structured data Can work across multiple tools
Produces scores or classifications Can plan multiple actions
Usually task-specific Can handle broader objectives
Fast inference Dynamic decision-making
Easier to benchmark More flexible

The combination can provide the best of both worlds.

A machine-learning model might be better at calculating a credit-risk score than an LLM. Meanwhile, an agent might be better at deciding what information should be collected before presenting a recommendation.

A Simple Architecture

A practical architecture could look like this:

                    User Goal
                       │
                       ▼
                ┌─────────────┐
                │ AI Agent    │
                │ Reasoning   │
                └──────┬──────┘
                       │
             ┌─────────┼─────────┐
             ▼         ▼         ▼
        ML Models    Databases   APIs
             │         │         │
             ▼         ▼         ▼
        Predictions   Data      External
                                  Tools
             │         │         │
             └─────────┼─────────┘
                       ▼
                 Agent Evaluation
                       │
                       ▼
                  Final Decision

The agent acts as the orchestration layer.

The ML models act as specialized tools.

Step 1: Identify Tasks That Need Machine Learning

The first step is deciding which parts of the workflow should use conventional ML.

For example, in a retail application:

Prediction tasks

  • Sales forecasting
  • Customer churn prediction
  • Product recommendation
  • Fraud detection
  • Inventory forecasting

These tasks can be handled by dedicated ML models.

There is usually little reason to replace a highly optimized forecasting model with an LLM simply because an agent is being introduced.

Step 2: Turn ML Models into Tools

The next step is to make your ML models accessible to the agent.

Suppose you have a Python model:

def predict_churn(customer_data):
    probability = model.predict_proba(customer_data)[0][1]
    return {
        "churn_probability": float(probability)
    }

Instead of manually calling this function every time, expose it as an agent tool.

Conceptually:

Tool: predict_customer_churn

Input:
customer_id

Output:
churn_probability
risk_level
important_features

Now the agent can decide when this model is useful.

Step 3: Give the Agent Context

An agent should not blindly call every available model.

It needs relevant context.

For example:

Customer:
- 4 years with company
- Purchased 3 times last year
- No purchases in 90 days
- Support complaints increased

Churn model:
Probability = 0.82

The agent can combine the structured prediction with other information.

It might reason:

The churn model indicates high risk. The customer also has declining activity and increased complaints. The next useful step is to examine recent support interactions before recommending an intervention.

This is where agentic reasoning adds value.

Step 4: Allow Multiple Models to Work Together

A sophisticated agent can use several specialized models.

Imagine a manufacturing system.

It could have:

Model A — Predictive maintenance

Machine failure probability: 74%

Model B — Anomaly detection

Vibration anomaly: Detected

Model C — Production forecasting

Expected production loss: 11%

The agent can combine these outputs.

Instead of treating each model independently, it can construct a workflow:

Detect anomaly
      ↓
Check failure probability
      ↓
Estimate production impact
      ↓
Check maintenance schedule
      ↓
Recommend action

The agent becomes the decision layer connecting specialized models.

Step 5: Use Agentic Reasoning for Model Selection

One of the most interesting possibilities is allowing an agent to select the appropriate model.

Suppose your system has:

fraud_model
churn_model
forecast_model
anomaly_model
recommendation_model

A user asks:

"Which customers should our team contact this week?"

The agent identifies that churn prediction is relevant.

It can then call:

customer_database
        ↓
churn_model
        ↓
customer segmentation
        ↓
agent analysis
        ↓
contact recommendations

This avoids running every model unnecessarily.

Step 6: Keep Predictions Separate from Reasoning

A crucial design principle is to distinguish between model outputs and agent conclusions.

For example:

{
  "model": "churn_model",
  "probability": 0.82,
  "confidence": 0.91
}

The agent should treat this as evidence.

It should not silently change:

0.82

into:

Customer will definitely leave.

A probability is not a certainty.

This separation improves transparency and makes the system easier to audit.

Step 7: Let the Agent Evaluate Model Results

An agent can also act as a verification layer.

Suppose a forecasting model predicts:

Next month's sales = $850,000

The agent could check:

  • Historical performance
  • Seasonal patterns
  • Recent marketing campaigns
  • Inventory levels
  • Current orders
  • External business information

If something looks unusual, it could request another analysis.

This creates a workflow such as:

Prediction
    ↓
Agent evaluation
    ↓
Does result make sense?
   / \
 Yes  No
  ↓    ↓
Use   Investigate
       ↓
    Recalculate

Step 8: Build a Feedback Loop

Agentic systems become more useful when they can learn from outcomes.

Consider a recommendation system.

The agent recommends:

Contact Customer A with a retention offer.

Later, the system observes:

Customer responded: Yes
Customer purchased: Yes

That outcome can become feedback for improving future decisions.

A larger architecture might look like:

Historical Data
      ↓
ML Training
      ↓
Prediction Model
      ↓
Agent
      ↓
Action
      ↓
Real-World Result
      ↓
Feedback Data
      ↓
Model Improvement

This creates a continuous improvement cycle.

Python-Based Example

A simple architecture can be built using Python.

Imagine a traditional classification model:

from sklearn.ensemble import RandomForestClassifier

model = RandomForestClassifier(
    n_estimators=100,
    random_state=42
)

model.fit(X_train, y_train)

Create a prediction function:

def predict_risk(features):
    probability = model.predict_proba([features])[0][1]

    return {
        "risk_probability": float(probability)
    }

Then an agent can conceptually use this function as one of its tools:

tools = [
    predict_risk,
    search_customer_history,
    get_recent_transactions,
    create_report
]

The agent decides which tools are appropriate for the user's objective.

The important idea is not the particular agent framework. The important idea is the architecture:

ML models provide specialized predictions; the agent coordinates them.

Where This Architecture Works Well

Fraud Detection

A fraud model can generate risk scores while an agent investigates supporting information.

For example:

Transaction
   ↓
Fraud model
   ↓
Risk score
   ↓
Agent
   ↓
Check account history
   ↓
Check recent transactions
   ↓
Decision

Healthcare Analytics

Specialized models can assist with:

  • Risk prediction
  • Medical-image classification
  • Patient deterioration prediction
  • Appointment forecasting

An agent could organize information and assist professionals with analysis.

However, high-stakes healthcare decisions require strong human oversight. The agent should not independently make clinical decisions.

Financial Services

Traditional ML can perform:

  • Credit-risk prediction
  • Fraud detection
  • Default prediction
  • Market-data analysis

An agent can combine those outputs with financial information and generate structured reports.

Again, important financial decisions should have appropriate human review and controls.

E-Commerce

An agent can combine:

  • Recommendation models
  • Demand forecasting
  • Customer segmentation
  • Churn prediction

For example:

Customer request
      ↓
Agent
      ↓
Recommendation model
      ↓
Inventory model
      ↓
Customer preference data
      ↓
Final recommendation

Important Challenges

Combining ML and agents also introduces new problems.

1. Incorrect Reasoning

An agent can misunderstand a model's output.

A probability of 70% does not mean something is guaranteed.

2. Poor Tool Selection

An agent may call the wrong model.

Tool descriptions therefore need to be clear.

Bad:

predict()

Better:

predict_customer_churn()

3. Data Quality

Agentic reasoning cannot compensate for fundamentally bad data.

If the ML model receives incorrect or biased information, its predictions may also be unreliable.

4. Cost and Latency

Calling multiple models, databases and APIs can make an agentic workflow slower and more expensive.

Developers should monitor:

  • Number of tool calls
  • Inference time
  • Token usage
  • API costs
  • Failure rates

5. Security

Agents can potentially access sensitive tools and databases.

Use:

  • Authentication
  • Authorization
  • Tool-level permissions
  • Input validation
  • Logging
  • Rate limits
  • Human approval for sensitive actions

The agent should have only the permissions it actually needs.

A Better Design: Deterministic + Agentic

Not every decision needs an LLM.

A strong architecture often combines deterministic workflows with agentic reasoning.

For example:

             User Request
                  ↓
            Agent Planner
                  ↓
        ┌─────────┴─────────┐
        ↓                   ↓
 Deterministic          ML Models
 Workflow                   ↓
        ↓              Predictions
        └─────────┬─────────┘
                  ↓
             Agent Review
                  ↓
             Final Output

Use conventional code where rules are predictable.

Use ML where statistical prediction is required.

Use agents where flexible planning and tool selection are valuable.

This hybrid approach is often more practical than making everything agentic.

The Future of Hybrid AI

The future of AI applications is unlikely to be purely traditional ML or purely generative AI.

Instead, many systems will combine several specialized components:

LLMs
 +
Traditional ML
 +
Databases
 +
Search
 +
APIs
 +
Business Rules
 +
Human Oversight

An agent can act as the orchestration layer connecting these components.

Traditional ML remains valuable because specialized models can be faster, cheaper and more predictable for well-defined tasks. Agentic systems add flexibility by deciding how those capabilities should be combined.

Final Thoughts

Combining traditional machine learning with agentic reasoning is not about replacing one technology with another. It is about giving each technology the job it performs best.

Traditional ML can provide reliable predictions, classifications and numerical estimates. Agentic AI can interpret goals, select tools, coordinate multiple steps and turn individual predictions into useful workflows.

The resulting system can be thought of as:

ML for specialized intelligence + agents for orchestration + software for reliable execution.

For developers building practical AI applications, this hybrid architecture offers a compelling path toward systems that are not only intelligent, but also modular, measurable and useful in real-world environments.

How I Use AI Agents as a Data Scientist in 2026

  How I Use AI Agents as a Data Scientist in 2026 Artificial intelligence is changing the way data scientists work. In 2026, AI agents are ...