NAME
Langertha::Raider - Autonomous agent with conversation history and MCP tools
VERSION
version 0.200
SYNOPSIS
use IO::Async::Loop;
use Future::AsyncAwait;
use Net::Async::MCP;
use MCP::Server;
use Langertha::Engine::Anthropic;
use Langertha::Raider;
# Set up MCP server with tools
my $server = MCP::Server->new(name => 'demo', version => '1.0');
$server->tool(
name => 'list_files',
description => 'List files in a directory',
input_schema => {
type => 'object',
properties => { path => { type => 'string' } },
required => ['path'],
},
code => sub { $_[0]->text_result(join("\n", glob("$_[1]->{path}/*"))) },
);
my $loop = IO::Async::Loop->new;
my $mcp = Net::Async::MCP->new(server => $server);
$loop->add($mcp);
async sub main {
await $mcp->initialize;
my $engine = Langertha::Engine::Anthropic->new(
api_key => $ENV{ANTHROPIC_API_KEY},
mcp_servers => [$mcp],
);
my $raider = Langertha::Raider->new(
engine => $engine,
mission => 'You are a code explorer. Investigate files thoroughly.',
);
# First raid — uses tools, builds history
my $r1 = await $raider->raid_f('What files are in the current directory?');
say $r1;
# Second raid — has context from first conversation
my $r2 = await $raider->raid_f('Tell me more about the first file you found.');
say $r2;
# Check metrics
my $m = $raider->metrics;
say "Raids: $m->{raids}, Tool calls: $m->{tool_calls}, Time: $m->{time_ms}ms";
# Reset for a fresh conversation
$raider->clear_history;
}
main()->get;
DESCRIPTION
Langertha::Raider is an autonomous agent that wraps a Langertha engine with MCP tools. It maintains conversation history across multiple interactions (raids), enabling multi-turn conversations where the LLM can reference prior context.
Key features:
Conversation history persisted across raids
Mission (system prompt) separate from engine's system_prompt
Automatic MCP tool calling loop
Cumulative metrics tracking
Hermes tool calling support (inherited from engine)
History management: Only user messages and final assistant text responses are persisted in history. Intermediate tool-call messages (assistant tool requests and tool results) are NOT persisted, preventing token bloat across long conversations.
engine
Required. A Langertha engine instance with MCP servers configured. The engine must compose Langertha::Role::Tools.
mission
Optional system prompt for the Raider. This is separate from the engine's own system_prompt — the Raider's mission takes precedence and is prepended to every conversation.
history
ArrayRef of message hashes representing the conversation history. Automatically managed by raid/raid_f. Can be inspected or manually set.
max_iterations
Maximum number of tool-calling round trips per raid. Defaults to 10.
metrics
HashRef of cumulative metrics across all raids:
{
raids => 3, # Number of completed raids
iterations => 7, # Total LLM round trips
tool_calls => 12, # Total tool invocations
time_ms => 4500.2, # Total wall-clock time in milliseconds
}
clear_history
$raider->clear_history;
Clears conversation history while preserving metrics.
reset
$raider->reset;
Clears both conversation history and metrics.
raid
my $response = $raider->raid(@messages);
Synchronous wrapper around raid_f. Sends messages, runs the tool loop, and returns the final text response. Updates history and metrics.
raid_f
my $response = await $raider->raid_f(@messages);
Async tool-calling conversation. Accepts the same message arguments as simple_chat (strings become user messages, hashrefs pass through). Returns a Future resolving to the final text response.
SUPPORT
Issues
Please report bugs and feature requests on GitHub at https://github.com/Getty/langertha/issues.
CONTRIBUTING
Contributions are welcome! Please fork the repository and submit a pull request.
AUTHOR
Torsten Raudssus <torsten@raudssus.de> https://raudss.us/
COPYRIGHT AND LICENSE
This software is copyright (c) 2026 by Torsten Raudssus.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.