boxlang-application-descriptor

Configure and debug Application.bx lifecycle callbacks and scope isolation in BoxLang.

Updated May 6, 2026

Search Tags:#debugging #application #scope #lifecycle #multi-application

Ready to run

npx skills add https://github.com/sosensible/buck --skill boxlang-application-descriptor-sosensible

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: boxlang-application-descriptor
Source: https://github.com/sosensible/buck/tree/main/.agents/skills/boxlang-application-descriptor
Command: npx skills add https://github.com/sosensible/buck --skill boxlang-application-descriptor-sosensible

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables designing and debugging Application.bx behavior, focusing on application discovery, lifecycle management, and scope isolation within the BoxLang runtime.

Core Features & Use Cases

Application Lifecycle Management: Configure start and end events, session handling, and request processing.
Multi-application Support: Set distinct this.name for isolated application environments.
Debugging & Troubleshooting: Verify app discovery, session hooks, and async scheduler/watcher setup.
Use Case: Developers troubleshooting app startup issues or testing multi-tenant setups can use this Skill to understand application behavior and configuration.

Quick Start

Use this Skill to verify application lifecycle callbacks and scope isolation settings in Application.bx.

Frequently Asked Questions about boxlang-application-descriptor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure application lifecycle callbacks in BoxLang?▼

You can configure application lifecycle callbacks in BoxLang by defining start, end, session, and request handling events within the Application.bx file. This ensures correct startup and processing behavior across multi-application environments.

What is scope isolation and how does it work in BoxLang multi-application setups?▼

Scope isolation in BoxLang separates runtime environments by assigning distinct this.name values in Application.bx. This mechanism ensures isolated application, session, and request scopes for modular or multi-tenant architectures.

How do I debug application discovery and startup issues in BoxLang?▼

Debug application discovery and startup issues in BoxLang by verifying app discovery paths, checking session hooks, and validating async scheduler or watcher setup configurations within your Application.bx lifecycle settings.

Can I run multiple isolated applications within a single BoxLang runtime?▼

Yes, you can run multiple isolated applications within a single BoxLang runtime by setting distinct this.name properties in each Application.bx file, which configures isolated environments for multi-tenant or modular setups.

Why are my BoxLang session hooks not triggering during application startup?▼

Session hooks may not trigger during BoxLang application startup if app discovery fails or Application.bx lifecycle settings are misconfigured. Verify your application scope isolation settings and async watcher setup to resolve the issue.