BoxLang AI vs Microsoft Agent Framework

BoxLang AI 71

Framework reading. A reference page for each built-in function with its arguments, and tool schemas generated from typed function arguments with required fields since 3.3.1. BoxLang is dynamically typed and no published API reference was found, though the repository builds DocBox API docs (15 of 25). llms.txt with about 150 entries and a Markdown copy of every page (10). The FAQ says when to use aiChat() or aiAgent() and the security guide says which guards to use when, though some FAQ links still say coming soon for pages that exist (14 of 20). Tool arguments are typed with required lists, and stdio options a server doesn't have throw InvalidArgument (11 of 15). About 100 example scripts in the repository and a gallery on ai.boxlang.io, but the production guide catches RateLimitException, TimeoutException and AuthenticationException, which the module's source never throws, and there is no exception reference (9 of 15). Keep a Changelog and a release-history page per version, but the 3.6.0 page still read unreleased on 1 November and two old versions appear twice in the changelog (12 of 15). 71 in all.

Microsoft Agent Framework 95

Typed in both languages, with py.typed markers and API references for Python and .NET on Microsoft Learn (25). Learn returns each docs page as Markdown when asked with an Accept header. No llms.txt was found (10). The overview has a table for when to use an agent or a workflow, and says to write a function instead where one would do (20). Tools are Python functions typed with Annotated and Pydantic Field, or AIFunction in .NET (15). Samples for every area and a typed exception hierarchy in the source, but we found no exception reference in the docs pages we read (12). A dated Python changelog and four upgrade guides. No changelog file was found for .NET (13).

BoxLang AI 71

Framework reading. 30 for what leaves the machine and credentials, 20 for approvals and sandboxing, 15 for prompt injection, 15 for audit and 20 for the security programme. No telemetry in the module's source, requests go only to configured providers, keys come from settings or environment variables, and request logging is off by default. 3.4.0 fixed a Gemini key leaking into logs through the request URL (27 of 30). Approval is enforced in code by HumanInTheLoopMiddleware with five policies, GuardrailMiddleware blocks tools by name and argument pattern, and stdio commands never use a shell. All of it is opt-in. allowedCommands allows any executable by default, FileSystemTools allows any path without allowedPaths, and the MCP server has no authentication unless configured (12 of 20). Unicode hygiene and fencing of ${context} are on by default, with opt-in input sanitiser, LLM judge and output guard. Streaming guards detect after the fact, which the changelog says (14 of 15). About 70 interception points, LoggingMiddleware, FlightRecorderMiddleware and MCP server statistics, with no OpenTelemetry export (11 of 15). CONTRIBUTING.md asks for reports to security@ortussolutions.com and the Slack #security channel. No security.txt (410), no bounty, and no published advisory found, while 3.6.0 lists a SQL injection fix in MySQL vector memory under Fixed (7 of 20). 71 in all.

Microsoft Agent Framework 93

Framework reading, so SOC 2 isn't scored. A package and version User-Agent goes out on client requests by default, with a feature-usage token on Foundry and Azure OpenAI paths. Both are documented with opt-out variables, and the observability module says the framework contacts no external system itself, with message content in traces off by default (25). approval_mode on function and MCP tools, an MCP tool allow-list, and Hyperlight and Monty sandboxes for model-written code in beta. Tools run without approval unless set (20). An Agent Safety page treats model-supplied arguments as untrusted, and FIDES labels content and enforces policy before sensitive tools run, though it is experimental and Python only (15). OpenTelemetry traces, metrics and logs to any exporter (15). SECURITY.md routes reports to MSRC with a bounty programme and coordinated disclosure, CodeQL runs in CI and three advisories were published with fixed versions on 7 October 2026. Microsoft's security.txt still carries an Expires of 23 September 2026 on 1 November. On 1 November the repository's advisories list showed none to our reader, while the GHSA-9f26-7mqc-9vc4 page still loads as published on 7 October, so no advisory after 17 October was found (18).

BoxLang AI 70

Apache-2.0, OSI approved, though the licence file sits in src/main/resources rather than the repository root (30). The FAQ says prompts and history go to the chosen cloud provider and that Ollama keeps data local, and we found no telemetry in the source, but there's no statement for the module of what, if anything, Ortus receives. Ortus's privacy policy covers its website and customers and says data is collected when you use its products without naming which (15 of 30). Migration notes are dated in the changelog, and default models were moved off a Groq model on its removal date, but there's no written deprecation policy or support window (10 of 20). No telemetry statement either way in the docs (10 of 20). 65 in all.

Microsoft Agent Framework 85

MIT (30). The core README says what the User-Agent and feature token are, and a design spec in the repository says the token goes only to Foundry and Azure OpenAI pipelines and not to third-party providers. That spec is still marked proposed on 1 November, and we found no statement of how long Microsoft keeps the data and no privacy document for the framework (22). Package lifecycle states are published per package, experimental APIs raise warnings, breaking changes are dated in the Python changelog and there are upgrade guides, but we found no written support window (14). Telemetry is disclosed with two opt-out variables (20).

BoxLang AI 74

Framework reading, scored on what a tool-calling agent with MCP takes. An agent with an MCP server is one aiAgent() call with mcpServers, and toolFilter and prefix limit what each server adds. Skills can load lazily, but autoLoadSkills is on by default and injects every SKILL.md under /.agents/skills into every agent (20 of 25). MaxToolCallsMiddleware caps tool calls, window and summary memory bound history by messages or tokens, withMaxResponseBytes caps MCP answers and listTools( cursor ) pages tools (17 of 20). Named exceptions (ProviderError, UnsupportedCapability, InvalidArgument, MCPCommandRefused, BXAI.SecurityViolation) but no reference page, and the changelog says a timed-out call still surfaces as a JSON parse error (12 of 20). RetryMiddleware with exponential backoff, approval resumes that don't replay the model call or rerun executed tools, and a stdio client that never repeats an in-flight call. MCP tool annotations such as readOnlyHint aren't read (15 of 20). An agent needs a name and works with defaults, and a mock provider runs with no key, but it is one language (10 of 15). 74 in all.

Microsoft Agent Framework 87

The documented Python agent with one MCP server is about 12 lines with MCPStdioTool from the core package, and allowed_tools, load_tools and progressive disclosure limit what reaches the model (25). The function loop stops at 40 iterations by default with a max_function_calls option, and compaction has its own docs page (20). A typed exception hierarchy, and the loop stops after three consecutive tool errors by default. We didn't find MCP failures documented (16). Workflows resume from checkpoints and sessions serialise, but we found no retry setting for model calls in the core client (14). An agent needs a client and instructions. Python and .NET are stable, Go is in preview, and the quickstarts assume a Microsoft Foundry project (12).

BoxLang AI 66

Read with the local-software lines. Official package on ForgeBox, installed with install-bx-module bx-ai or box install bx-ai, with BoxLang 1.14.0 or later in box.json and JDK 21 in CONTRIBUTING.md, but the 3.6 announcement says BoxLang 1.18 or later (18 of 20). tests.yml runs about 140 test classes against Ollama and the vector stores in Docker Compose, and against paid providers on development and releases, on pull requests and pushes to development. Whether runs pass wasn't read, since WebFetch refused github.com (15 of 25). Open issues and replies weren't read for the same reason. The changelog closes issues #182 to #259 in 3.3.1 to 3.4.0, and bugs also go to Ortus's Jira (10 of 25). Keep a Changelog with semantic versioning stated and Migration sections, but breaking changes ship in minor releases (8 of 15). 3.6.0, past 1.0 (15). 66 in all.

Microsoft Agent Framework 78

Read with the local-software lines. Official packages on PyPI (Requires-Python >=3.10 in the repository, though 1.24.0 makes Python 3.11 the supported baseline and says the next release drops 3.10) and NuGet (net8.0 to net10.0, netstandard2.0, net472) (20). Of the 15 most recent .NET build and test runs on 1 November 2026, 10 passed, 2 were cancelled and 4 wait for approval on a pull request, with none failed, and the scheduled runs on main passed on 31 October and 1 November (25). 610 open issues and 229 open pull requests on 1 November, up from 575 and 201 on 8 October. Closures and bug labels weren't re-counted (10). The Python changelog follows Keep a Changelog and states semantic versioning, and marks breaking changes, but they keep shipping in minor releases of released packages, such as agent-framework-core in 1.22.0 on 15 October and 1.23.0 on 22 October 2026 (8). Python 1.24.0 and .NET 1.27.0, with the root and core packages classed 5 - Production/Stable (15).

BoxLang AI 50

Self-hosted rule, scored on the paid option. No payment protocol (0). BoxLang runtime plans are public without a login, Starter $749 a year and BoxLang+ and BoxLang++ from $1,999 to $4,999 a server or node a year, plan pricing rather than per unit (10). The Apache-2.0 module installs with no card (20) and no account or sign-up (20). 50 in all.

Microsoft Agent Framework 60

Read with the self-hosted rule. No payment protocol (0). The package is free under MIT, and Foundry hosted agents, the managed option, has per-unit prices in Azure's public retail price API ($0.0994 a vCPU-hour and $0.0118 an hour for memory in East US). Those meters are per the 17 October check, not re-read on 1 November. The pricing web page still showed placeholders to our reader on 1 November (20). The packages install with no card (20) and no account, and run local models through the Ollama and Foundry Local connectors (20).