flock-core 0.4.0b44__tar.gz → 0.4.0b46__tar.gz

flock_core-0.4.0b46/.github/ISSUE_TEMPLATE/vulnerability_report.md

@@ -0,0 +1,85 @@
+---
+name: Vulnerability Report
+about: Report a security vulnerability in the project
+title: "[Vulnerability] <Brief Summary of the Vulnerability>"
+labels: vulnerability, security 
+assignees: ''
+---
+
+<!--
+Note: Please search to see if an issue already exists for the vulnerability you encountered.
+-->
+
+
+# Vulnerability Details
+
+**Title:**
+<!-- A brief title summarizing the vulnerability (e.g. "SQL Injection in Agent Tool xyz") -->
+
+**Description:**
+<!--
+A detailed description of the vulnerability.
+Explain what the vulnerability is, what components
+of the framework it affects, and any specific configurations
+or conditions that may lead to exploitation.
+-->
+
+**Impact:**
+<!--
+Explain the potential impact of the vulnerability on the framework and users, including
+what information could be exposed, altered, or destroyed.
+
+
+Include any possible scenarios in which the vulnerability could be exploited.
+-->
+
+## Steps to Reproduce
+
+<!--
+
+Please provide a clear and concise list of steps to reproduce the vulnerability:
+
+-->
+
+## Evidence:
+
+<!--
+
+If possible, please provide any screenshots, logs, or console outputs that
+demonstrate the vulnerability.
+
+This helps to convey the issue effectively.
+-->
+
+## Environment
+
+<!--
+
+Please provide details about the environment in which you discovered the vulnerability:
+
+- **Operating System:** (e.g., Windows 10, Ubuntu 20.04)
+- **Browser:** (e.g., Chrome 92, Firefox 89)
+- **Application Version:** (e.g., 1.2.3)
+- **Library Versions:** (list any libraries or dependencies relevant to the vulnerability)
+
+-->
+
+## Suggested Mitigation
+
+<!--
+
+If you have thoughts on how to fix or mitigate the vulnerabilit, please provide them below.
+This could include code changes, configurations, or references to best practices.
+
+-->
+
+## Additional Context
+
+<!--
+Provide any additional context or information that you believe is necessary for understanding 
+the vulnerability or its implications.
+-->
+---
+
+**Thank you for reporting!**
+We appreciate your efforts in helping us keep this project secure

flock_core-0.4.0b46/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+info@whiteduck.de.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

flock_core-0.4.0b46/CONTRIBUTING.md

@@ -0,0 +1,151 @@
+<!-- TOC --><a name="contributing-to-flock"></a>
+# Contributing to Flock
+
+First off, thanks for taking the time to contribute!
+Flock is still in early development but we value outside input. ❤️
+
+We follow the [Contributor Covenant](https://www.contributor-covenant.org/) code of conduct.
+
+## Table of Contents:
+<!-- TOC start -->
+
+- [Contributing to Flock](#contributing-to-flock)
+   * [🗒️ Getting Started:](#-getting-started)
+   * [❗ Reporting Issues:](#-reporting-issues)
+   * [🚋 Pull Requests: ](#-pull-requests)
+   * [💻 Coding Standards: ](#-coding-standards)
+      + [General Standards:](#general-standards)
+      + [A few best practices for writing good code:](#a-few-best-practices-for-writing-good-code)
+         - [Embrace Declarative Programming Principles:](#embrace-declarative-programming-principles)
+         - [Consistent Code Formatting:](#consistent-code-formatting)
+         - [Meaningful Naming Conventions:](#meaningful-naming-conventions)
+         - [Modular and Composable Code:](#modular-and-composable-code)
+   * [📖 Documentation Guidelines: ](#-documentation-guidelines)
+      + [A few best practices for writing good documentation:](#a-few-best-practices-for-writing-good-documentation)
+   * [🔭 Testing and Reliability:](#-testing-and-reliability)
+   * [Release Process:](#release-process)
+
+<!-- TOC end -->
+
+<!-- TOC --><a name="-getting-started"></a>
+## 🗒️ Getting Started:
+1. Fork the repo & create your feature branch (`git checkout -b feat/my-awesome-thing`).
+2. Install dev dependencies: `uv pip install -r requirements.txt && uv pip install -r requirements-dev.txt.`
+3. Run tests: `pytest -q` (they should pass before and after your change).
+4. Make changes – keep them atomic and well-documented.
+5. Lint & type-check: `ruff .` and `mypy src/.`
+6. Commit following Conventional Commits (`feat:`, `fix:`, `docs:` etc.).
+7. Open a PR against main. Include a description, screenshots, and linked issues.
+
+
+<!-- TOC --><a name="-reporting-issues"></a>
+## ❗ Reporting Issues:
+- Before submitting a new issue, pleas check [existing issues](https://github.com/whiteducksoftware/flock/issues) if it has already been reported.
+- To submit a new issue, please use the provided **Issue Templates** and provide a clear and descriptive title along with a detailed description of the problem or feature request, including steps to reproduce if it's a bug.
+
+<!-- TOC --><a name="-pull-requests"></a>
+## 🚋 Pull Requests: 
+- Ensure your code is well-tested and adheres to the [Coding Standards](#code-standards) outlined below.
+- Write clear commit messages that explain the changes made.
+- Clearly outline and communicate breaking API-changes.
+- Before submitting a pull request, make sure your branch is up to date with the base branch (`main`) of the [main repository](https://github.com/whiteducksoftware/flock).
+- Open a pull request with a summary of your changes and any relevant issue numbers.
+
+<!-- TOC --><a name="-coding-standards"></a>
+## 💻 Coding Standards: 
+- Flock follows a **declarative** approach and design philosophy. Make sure that your code follows this principle.
+- Follow the coding conventions used within the existing codebase.
+- Keep code modular and readable. Prefer clarity over brevity.
+- Include comments where necessary and explain complex logic.
+
+<!-- TOC --><a name="general-standards"></a>
+### General Standards:
+- Python `3.10.+`. Use type hints everywhere.
+- Follow [`ruff`](https://docs.astral.sh/ruff/) default rules + [`black`](https://black.readthedocs.io/en/stable/index.html) formatting.
+- Keep imports sorted (`ruff format`)
+- Write **async-friendly** code. (non-blocking I/O)
+
+<!-- TOC --><a name="a-few-best-practices-for-writing-good-code"></a>
+### A few best practices for writing good code:
+
+<!-- TOC --><a name="embrace-declarative-programming-principles"></a>
+#### Embrace Declarative Programming Principles:
+- **Favor Declarative Styles**:
+   - Exposed API-Code should express the desired results rather than detailing the control flow of the program.
+   - Use declarative constructs to define behavior instead of imperative constructs where applicable.
+   - Aim for expressiveness and clarity in stating "what" should happen rather than "how" it should happen.
+- **Use High-Level Abstractions**:
+   - Leverage Flock's existing abstractions to minimize boilerplate code and simplify the implementation.
+   - This makes the code easier to read and understand.
+<!-- TOC --><a name="consistent-code-formatting"></a>
+#### Consistent Code Formatting:
+- **Adhere to Existing Code Style**: Consistency in formatting enhances readability and helps developers navigate the codebase.
+<!-- TOC --><a name="meaningful-naming-conventions"></a>
+#### Meaningful Naming Conventions:
+- **Use Descriptive Names**:
+  - Choose variable, function, and class names that clearly describe their purpose.
+  - Be consistent. Stick to the naming conventions in Flock's existing code-base.
+<!-- TOC --><a name="modular-and-composable-code"></a>
+#### Modular and Composable Code:
+- **Write Modular Code**: Break down complex logic into smaller, reusable components.
+- **Avoid Side Effects**: Aim to minimize side effects where possible.
+
+
+<!-- TOC --><a name="-documentation-guidelines"></a>
+## 📖 Documentation Guidelines: 
+- Documentation lives under [`docs/`](https://github.com/whiteducksoftware/flock/tree/master/docs), and is built with [MkDocs Material](https://github.com/squidfunk/mkdocs-material).
+- Good documentation is crucial for the usability of Flock. When adding or updating code, please also update the relevant documentation.
+- Use clear, concise language and include examples where applicable. (On that note: If you want to, you may also provide an example for the [example showcase](https://github.com/whiteducksoftware/flock-showcase)
+- Maintain consistency in formatting and style throughout the documentation.
+- Use American English
+- Keep sentences short; favour lists & tables.
+- Add code blocks with triple-backticks and language.
+
+<!-- TOC --><a name="a-few-best-practices-for-writing-good-documentation"></a>
+### A few best practices for writing good documentation:
+1. Document the **Why**, not just the how:
+    - Documentation should explain the rational behind your decisions, rather than just describing the "how".
+    - This helps other developers understand the context and reasoning for the implementation, making the code more maintainable and modifyiable.
+2. Keep it Up to Date:
+   - Your documentation should evolve alongside the code. If you change the behavior of an existing component of Flock, please also take care to make sure the documentation reflects this fact.
+3. Write for the Reader:
+   - Consider the audience for your documentation.
+   - It should be accessible and understandable for developers who are not intimately familiar with the code.
+4. Document Intent and Design:
+   - Refering to Point 1, Document your decisions of **why** you chose to implement a new component or code change the way you did, if it is not immediately obvious.
+5. Code as Documentation:
+   - Well-written code can serve as it's own documentation.
+   - Code should be clear, expressive and self-explanatory where possible.
+   - Using meaningful names for variables, functions, and classes can reduce the need for excessive comments.
+6. Provide Examples:
+   - Examples can help other developers understand your changes and are therefore encouraged.
+7. Use Comments Wisely:
+   - Aviod redundant comments that merely restate what the code does, which can clutter the codebase and detract from its readability.
+8. Be Pragmatic:
+   - There is no need for you to excessively comment every line of code you provide.
+   - Add documentation where necessary and focus on keeping documentation on a high level.
+
+<!-- TOC --><a name="-testing-and-reliability"></a>
+## 🔭 Testing and Reliability:
+Flock aims to provide a easy and reliable way to implement agentic applications. Therefore, well tested code is crucial.
+
+- Test your changes thoroughly! Ensure that existing tests pass and add **new tests** for any new functionality.
+- Follow Flock's testing conventions and use the provided testing framework.
+- Run the tests before submitting your pull request to confirm that nothing is broken.
+- Test can be run locally with `pytest -q`
+- Place new tests in `tests/` mirroring the package path.
+- Use [`pytest`](https://docs.pytest.org/en/stable/) fixtures instead of duplicating setup code.
+- For Temporal code, rely on the *Temporal Test Server* fixture.
+
+
+<!-- TOC --><a name="release-process"></a>
+## Release Process:
+1. Maintainer bumps versiion in `pyproject.toml` following **SemVer**.
+2. Changelog entry added in `docs/about/changelog.md`.
+3. `uv pip install -e .[all] && pytest`
+4. `git tag v.X.Y.Z && git push --tags`
+5. GitHub Action publishes to PyPI.
+
+Thank you for contributing to Flock, the declarative Agent-Framework. 🦆💓
+
+

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: flock-core
-Version: 0.4.0b44
+Version: 0.4.0b46
 Summary: Declarative LLM Orchestration at Scale
 Author-email: Andre Ratzenberger <andre.ratzenberger@whiteduck.de>
 License-File: LICENSE

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/docs/about/contributing.md

@@ -21,7 +21,14 @@ First off, thanks for taking the time to contribute!  Flock is still early but w
 
 ---
 
-## 2. Docs Contributions
+
+## 2. Reporting Issues:
+* Before submitting a new issue, pleas check [existing issues](https://github.com/whiteducksoftware/flock/issues) if it has already been reported.
+* To submit a new issue, please use the provided **Issue Templates** and provide a clear and descriptive title along with a detailed description of the problem or feature request, including steps to reproduce if it's a bug.
+
+---
+
+## 3. Docs Contributions
 
 Docs live under `docs/` and are built with **MkDocs Material**.
 
@@ -32,10 +39,13 @@ mkdocs serve  # live-reload at http://localhost:8000
 * Use American English.
 * Keep sentences short; favour lists & tables.
 * Add code blocks with triple-backticks and language.
+* Good documentation is crucial for the usability of Flock. When adding or updating code, please also update the relevant documentation.
+* Use clear, concise language and include examples where applicable. (On that note: If you want to, you may also provide an example for the [example showcase](https://github.com/whiteducksoftware/flock-showcase)
+* Maintain consistency in formatting and style throughout the documentation.
 
 ---
 
-## 3. Coding Standards
+## 4. Coding Standards
 
 * Python `3.10+`.  Use type hints everywhere.
 * Follow `ruff` default rules + `black` formatting.
@@ -44,15 +54,27 @@ mkdocs serve  # live-reload at http://localhost:8000
 
 ---
 
-## 4. Tests
+## 5. Tests
 
 * Place new tests in `tests/` mirroring the package path.
 * Use `pytest` fixtures instead of duplicating setup code.
 * For Temporal code, rely on the *Temporal Test Server* fixture.
+* Test your changes thoroughly! Ensure that existing tests pass and add **new tests** for any new functionality.
+* Follow Flock's testing conventions and use the provided testing framework.
+* Run the tests before submitting your pull request to confirm that nothing is broken.
+
+---
 
+## 6. Pull Requests: 
+- Ensure your code is well-tested and adheres to the Coding-Standards.
+- Write clear commit messages that explain the changes made.
+- Clearly outline and communicate breaking API-changes.
+- Before submitting a pull request, make sure your branch is up to date with the base branch (`main`) of the [main repository](https://github.com/whiteducksoftware/flock).
+- Open a pull request with a summary of your changes and any relevant issue numbers.
+  
 ---
 
-## 5. Release Process
+## 7. Release Process
 
 1. Maintainer bumps version in `pyproject.toml` following *SemVer*.
 2. Changelog entry added in `docs/about/changelog.md`.
@@ -60,6 +82,10 @@ mkdocs serve  # live-reload at http://localhost:8000
 4. `git tag vX.Y.Z && git push --tags`.
 5. GitHub Action publishes to PyPI.
 
----
+--- 
+
+
+
+
 
 Happy hacking! 🐦

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "flock-core"
-version = "0.4.0b-44"
+version = "0.4.0b-46"
 description = "Declarative LLM Orchestration at Scale"
 readme = "README.md"
 authors = [

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/src/flock/cli/manage_agents.py

@@ -5,6 +5,7 @@ including listing, adding, editing, and removing agents.
 """
 
 import questionary
+from rich.box import Box
 from rich.console import Console
 from rich.panel import Panel
 from rich.table import Table
@@ -104,9 +105,11 @@ def _list_agents(flock: Flock):
         model = agent.model or flock.model or "Default"
 
         # Format description (truncate if too long)
-        description = str(agent.description)
-        if len(description) > 30:
+        description = agent.resolved_description
+        if description and len(description) > 30:
             description = description[:27] + "..."
+        elif not description:
+            description = "N/A"
 
         # Format input/output (truncate if too long)
         input_str = str(agent.input)
@@ -156,13 +159,13 @@ def _view_agent_details(agent: FlockAgent):
     )
 
     # Create a panel for each section
-    basic_info = Table(show_header=False, box=None)
+    basic_info = Table(show_header=False, box=Box.ROUNDED, padding=(0, 2))
     basic_info.add_column("Property", style="cyan")
     basic_info.add_column("Value", style="green")
 
     basic_info.add_row("Name", agent.name)
     basic_info.add_row("Model", str(agent.model or "Default"))
-    basic_info.add_row("Description", str(agent.description))
+    basic_info.add_row("Description", agent.resolved_description if agent.resolved_description else "N/A")
     basic_info.add_row("Input", str(agent.input))
     basic_info.add_row("Output", str(agent.output))
     basic_info.add_row("Write to File", str(agent.write_to_file))
@@ -329,6 +332,18 @@ def _edit_agent(flock: Flock):
 
     agent = flock._agents[agent_name]
 
+    if not agent:
+        console.print(f"[bold red]Agent '{agent_name}' not found.[/]")
+        return
+
+    console.print(f"\n[bold underline]Details for Agent: {agent.name}[/]")
+    basic_info = Table(show_header=False, box=Box.ROUNDED, padding=(0, 2))
+    basic_info.add_row("Name", agent.name)
+    description = agent.resolved_description
+    basic_info.add_row("Description", description if description else "N/A")
+    basic_info.add_row("Model", agent.model or "Flock Default")
+    basic_info.add_row("Input Signature", str(agent.input))
+
     # Choose edit method
     edit_choice = questionary.select(
         "How would you like to edit this agent?",

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/src/flock/core/api/endpoints.py

@@ -246,7 +246,7 @@ def create_api_router() -> APIRouter:
         """List all available agents in the currently loaded Flock."""
         logger.debug("API request: list agents")
         agents_list = [
-            {"name": agent.name, "description": agent.description or agent.name}
+            {"name": agent.name, "description": agent.resolved_description or agent.name}
             for agent in flock_instance.agents.values()
         ]
         return {"agents": agents_list}

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/src/flock/core/flock_agent.py

@@ -195,6 +195,37 @@ class FlockAgent(BaseModel, Serializable, DSPyIntegrationMixin, ABC):
         """Get a list of currently enabled modules attached to this agent."""
         return [m for m in self.modules.values() if m.config.enabled]
 
+    @property
+    def resolved_description(self) -> str | None:
+        """Returns the resolved agent description.
+        If the description is a callable, it attempts to call it.
+        Returns None if the description is None or a callable that fails.
+        """
+        if callable(self.description):
+            try:
+                # Attempt to call without context first.
+                # If callables consistently need context, this might need adjustment
+                # or the template-facing property might need to be simpler,
+                # relying on prior resolution via resolve_callables.
+                return self.description()
+            except TypeError:
+                # Log a warning that context might be needed?
+                # For now, treat as unresolvable in this simple property.
+                logger.warning(
+                    f"Callable description for agent '{self.name}' could not be resolved "
+                    f"without context via the simple 'resolved_description' property. "
+                    f"Consider calling 'agent.resolve_callables(context)' beforehand if context is required."
+                )
+                return None # Or a placeholder like "[Callable Description]"
+            except Exception as e:
+                logger.error(
+                    f"Error resolving callable description for agent '{self.name}': {e}"
+                )
+                return None
+        elif isinstance(self.description, str):
+            return self.description
+        return None
+
     # --- Lifecycle Hooks (Keep as they were) ---
     async def initialize(self, inputs: dict[str, Any]) -> None:
         """Initialize agent and run module initializers."""

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/src/flock/webapp/static/css/chat.css

@@ -29,7 +29,7 @@ body.chat-page {
     padding: 1rem 1.5rem; 
     display: flex;
     flex-direction: column;
-    min-height: 60vh;
+    min-height: 0;
     gap: 1rem;
     background-color: rgba(0, 0, 0, 0.05);
     background-image: 
@@ -118,7 +118,7 @@ body.chat-page {
     box-shadow: 0 0 0 2px rgba(var(--pico-primary-rgb, 0, 123, 255), 0.25);
 }
 
-#chat-form button { 
+#chat-container form button[type="submit"] { 
     flex: 0 0 auto; 
     min-width: auto;
     width: 150px; /* Wider send button */
@@ -132,7 +132,7 @@ body.chat-page {
     height: 3rem;
 }
 
-#chat-form button:hover {
+#chat-container form button[type="submit"]:hover {
     background: var(--pico-primary-hover, var(--pico-primary));
     transform: translateY(-2px);
     box-shadow: 0 4px 8px rgba(0, 0, 0, 0.1);
@@ -185,11 +185,11 @@ body.chat-page {
    ------------------------------------------------------------------------- */
 body:not(.chat-page) #chat-container,
 body:not(.chat-page) .chat-container {
-    height: auto;
-    min-height: 60vh;
-    /* share same centering rules */
+    height: 100%;
+    min-height: 100%;
+    /* allow full width inside the main content area */
     width: 100%;
-    max-width: 80%;
+    max-width: 100%;
     margin: 0 auto;
 }
 
@@ -225,3 +225,18 @@ body:not(.chat-page) .chat-settings-form .grid button:first-child {
     flex: 0 0 auto;
     width: auto;
 }
+
+/* -------------------------------------------------------------------------
+   Container flex area to ensure chat-log grows/shrinks as needed
+   ------------------------------------------------------------------------- */
+#chat-content-area {
+    display: flex;
+    flex-direction: column;
+    flex: 1 1 auto;
+    overflow: hidden;
+}
+
+/* Prevent double scrollbars when chat is embedded */
+main.main-content:has(#chat-container) {
+    overflow: hidden;
+}

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/src/flock/webapp/templates/base.html

@@ -32,7 +32,7 @@
 
 <body>
     <header class="top-header">
-        <span><strong>🐧 Flock UI 🐤</strong></span>
+        <span><strong>🐧 Flock Playground 🐤</strong></span>
         <span id="header-flock-status-container" hx-get="/ui/htmx/header-flock-status?ui_mode={{ ui_mode }}"
             hx-trigger="load, flockLoaded from:body, flockCleared from:body" hx-swap="innerHTML">
             <small>Loading status...</small> {# Placeholder while loading #}

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/src/flock/webapp/templates/chat.html

@@ -33,7 +33,13 @@
                 <p><em>Loading chat…</em></p>
             </div>
             
-            <form id="chat-form" hx-post="/chat/send" hx-target="#chat-log" hx-swap="innerHTML" hx-on::after-request="this.reset()">
+            <form id="chat-form-standalone"
+                  hx-post="/chat/send"
+                  hx-target="#chat-log"
+                  hx-swap="innerHTML"
+                  hx-disabled-elt="input[name='message'], button[type='submit']"
+                  hx-on::before-request="htmx.find('#chat-form-standalone button[type=\'submit\']').textContent = 'Sending...'"
+                  hx-on::after-request="htmx.find('#chat-form-standalone button[type=\'submit\']').textContent = 'Send'; this.reset();">
                 <input type="text" name="message" placeholder="Type a message…" required autofocus>
                 <button type="submit">Send</button>
             </form>

{flock_core-0.4.0b44 → flock_core-0.4.0b46}/src/flock/webapp/templates/partials/_agent_detail_form.html

@@ -23,12 +23,13 @@
           hx-indicator="#agent-detail-loading-indicator">
 
         <fieldset>
-            <label for="agent_name_field">Name *</label>
-            <input type="text" id="agent_name_field" name="agent_name" value="{{ agent.name if agent and not form_errors else (form_data.agent_name if form_data else '') }}" required placeholder="my_processing_agent">
+            <legend>Core Agent Configuration</legend>
+            <label for="agent_name_field">Agent Name *</label>
+            <input type="text" id="agent_name_field" name="agent_name" value="{{ agent.name if agent and not form_errors else (form_data.agent_name if form_data else '') }}" required placeholder="Unique name for the agent">
             {% if form_errors and form_errors.agent_name %}<small class="field-error">{{ form_errors.agent_name }}</small>{% endif %}
 
             <label for="agent_description_field">Description</label>
-            <textarea id="agent_description_field" name="agent_description" placeholder="Briefly describe what this agent does.">{{ agent.description if agent and not form_errors else (form_data.agent_description if form_data else '') }}</textarea>
+            <textarea id="agent_description_field" name="agent_description" placeholder="Briefly describe what this agent does.">{{ agent.resolved_description if agent and not form_errors else (form_data.agent_description if form_data else '') }}</textarea>
 
             <label for="agent_model_field">Model Override (Optional)</label>
             <input type="text" id="agent_model_field" name="agent_model" value="{{ agent.model if agent and agent.model and not form_errors else (form_data.agent_model if form_data else '') }}" placeholder="e.g., openai/gpt-3.5-turbo (uses Flock default if blank)">