Add aevatar app experience and Telegram user bridge integration#28
Merged
Add aevatar app experience and Telegram user bridge integration#28
Conversation
- Added multiple workflows for OpenClaw integration, including setup, readiness checks, and screenshot tasks, enhancing the capabilities of the workflow system. - Introduced a unified CLI tool for configuration, improving user experience and accessibility. - Updated documentation to reflect new workflows and CLI commands, ensuring clarity for users. - Enhanced the web application to support new workflows and provide better interaction with OpenClaw features. These changes aim to streamline the integration of OpenClaw into the Aevatar ecosystem, improving usability and functionality.
- Updated the `openclaw_call` functionality to restrict execution to the OpenClaw CLI only, with support for custom installation paths via the `AEVATAR_OPENCLAW_CLI_PATH` environment variable. - Improved documentation across multiple files to clarify the usage of `openclaw_call`, including safety constraints for the OpenClaw bridge and the requirement for explicit authentication tokens. - Refactored the OpenClaw module to validate CLI executable identity, ensuring that only valid OpenClaw binaries are executed. - Enhanced integration tests to cover new error handling scenarios and validate the behavior of the OpenClaw module under various conditions. These changes aim to strengthen the OpenClaw integration within the Aevatar ecosystem, improving security and usability for developers.
- Revised the `openclaw_call` documentation across multiple files to specify that the custom installation path set via `AEVATAR_OPENCLAW_CLI_PATH` must point to an executable named `openclaw`. - Enhanced clarity in the README files to ensure users understand the constraints and requirements for using the OpenClaw CLI effectively. These changes aim to improve user understanding and ensure correct usage of the OpenClaw integration within the Aevatar ecosystem.
- Removed multiple OpenClaw workflows (57-68) from the project to streamline the workflow system and focus on essential functionalities. - Updated the `AGENTS.md` file to include a new CLI playground asset drift guard for verifying static resource consistency. - Revised the `README.md` to reflect the removal of outdated workflows and clarify the current capabilities of the OpenClaw integration. - Enhanced the web application to improve user interaction with the remaining workflows and ensure clarity in available features. These changes aim to simplify the OpenClaw integration within the Aevatar ecosystem, improving usability and maintainability.
- Introduced multiple new workflow examples demonstrating various primitives such as `assign`, `cache`, `conditional`, and `llm_call`. - Updated existing demo workflows to improve clarity and functionality, including renaming demo identifiers for consistency. - Added ergonomic aliases for `cli_call`, `foreach_llm`, and `map_reduce_llm` to streamline usage. - Enhanced documentation in `README.md` to reflect changes in demo execution commands and workflow descriptions. These updates aim to enrich the Aevatar demo experience, showcasing the capabilities of the workflow system more effectively.
loning
reviewed
Mar 6, 2026
Contributor
There was a problem hiding this comment.
不要写在workflow里面,把独立的GAgent都放到独立项目里面, 作为能力提供
- Introduced the `TelegramUserBridgeGAgent` for delegating tasks to external agents in Telegram groups, allowing Aevatar to handle complex operations through group interactions. - Updated workflow YAML examples to reflect the new delegation pattern, including improved handling of responses and timeouts. - Enhanced documentation for the Telegram bridge integration, detailing prompt composition and key points for effective usage. - Added a GitHub Actions workflow for publishing the Aevatar CLI, streamlining the release process. These changes aim to improve the Aevatar workflow capabilities and provide clearer guidance for users integrating with Telegram.
eanzhao
added a commit
that referenced
this pull request
May 8, 2026
- #13 (major, arch): /api/oauth/aevatar-client/rebuild now dispatches ProvisionAevatarOAuthClientCommand via IActorDispatchPort.DispatchAsync, matching /unbind. The inline actor.HandleEventAsync was a known CLAUDE.md "投递语义必须 runtime-neutral" violation; aligning the two endpoints removes the inconsistency that any future inbox middleware would silently bypass on rebuild. - #24 (minor, design): callback endpoint accepts ?format=json on the URL to opt back into the {status:"bound", already_bound, display_name} envelope that programmatic CLI/SDK consumers used pre-HTML-render. Default stays HTML for browser callbacks. - #26 (minor, arch): /rebuild now sits behind a RebuildAuthEndpointFilter that enforces the admin-token check before model binding and per-request DI activation kick in. The filter + the inline check in the handler are redundant by design (defense in depth) — the filter rejects unauth posts before deserialization runs, and the handler still validates so hand-rolled tests/integration scenarios cannot bypass. - #28 (minor, design): document the readmodel-deletion contract in the ExternalIdentityBindingProjector header — empty BindingId deletes the document instead of upserting an inactive record; downstream audit consumers must read the committed-event log directly. - #1 + #2 (blocker, arch): no change needed. Earlier commits in this PR already moved /model self-heal to IActorDispatchPort.DispatchAsync and removed the EnsureProjectionForActorAsync call from the slash-command request path. Verified by reading the current handler. - #25 (minor, test): documented in the rebuild handler comment — concurrent /rebuild calls would race on the same actor, but this is operator-grade break-glass and de-duping concurrent rebuilds is out of scope. Build clean (Identity), 34 OAuth-path tests pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
aevatarCLI command groups with richer subcommands aroundconfig,chat, and especiallyapp.aevatar appruntime improvements (health probing, restart flow, API base resolution, embedded/proxy mode handling, and improved playground experience).telegram_user) and bridge agents (TelegramBridgeGAgent/TelegramUserBridgeGAgent) to support Telegram group request/reply workflows.telegram_openclaw_bridge_chat) and related connector deployment guidance.Why
aevatar app) and a better built-in playground.Main Changes
aevatar appwith--port,--no-browser,--api-base, andaevatar app restart.chatandapp./api/bridge/callback-tokenand/api/bridge/callbacks.BridgeGAgent) and bridge options wiring.telegram_userconnector and builder in bootstrap connector registration.agent_typeworkflow parameters.Notes