Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(core): publish agent details on connect #591

Merged
merged 6 commits into from
Dec 17, 2024
Merged

Conversation

jrriehl
Copy link
Contributor

@jrriehl jrriehl commented Dec 16, 2024

Proposed Changes

Optionally publish agent details (name, readme, avatar url) after connecting with the local inspector.

Types of changes

What type of change does this pull request make (put an x in the boxes that apply)?

  • Bug fix (non-breaking change that fixes an issue).
  • New feature added (non-breaking change that adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to stop working as expected).
  • Documentation update.
  • Something else (e.g., tests, scripts, example, deployment, infrastructure).

Checklist

Put an x in the boxes that apply:

  • I have read the CONTRIBUTING guide
  • Checks and tests pass locally

If applicable

  • I have added tests that prove my fix is effective or that my feature works
  • I have added/updated the documentation (executed the script in python/scripts/generate_api_docs.py)

Dacksus
Dacksus previously approved these changes Dec 16, 2024
Copy link
Contributor

@Dacksus Dacksus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

python/src/uagents/mailbox.py Show resolved Hide resolved
@jrriehl jrriehl merged commit e4d37c2 into main Dec 17, 2024
9 checks passed
@jrriehl jrriehl deleted the feat/update-agent-details branch December 17, 2024 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants