Skip to content

demo: Example app with calendar assistant using tool calling#211

Merged
pweglik merged 62 commits intov0.4.0-rc1from
@pw/llm-tool-calling-flashy-demo
Apr 28, 2025
Merged

demo: Example app with calendar assistant using tool calling#211
pweglik merged 62 commits intov0.4.0-rc1from
@pw/llm-tool-calling-flashy-demo

Conversation

@pweglik
Copy link
Copy Markdown
Contributor

@pweglik pweglik commented Apr 24, 2025

Description

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update (improves or adds clarity to existing documentation)

Tested on

  • iOS
  • Android

Checklist

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation accordingly
  • My changes generate no new warnings

Additional notes

pweglik and others added 30 commits April 23, 2025 12:36
Remove Llama Export, refactor docs

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [x] Documentation update (improves or adds clarity to existing
documentation)

- [x] I have performed a self-review of my code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have updated the documentation accordingly
- [x] My changes generate no new warnings

---------

Co-authored-by: Jakub Chmura <92989966+chmjkb@users.noreply.github.com>
@pweglik
Copy link
Copy Markdown
Contributor Author

pweglik commented Apr 25, 2025

I think we should add some response message if tool was called, e.g "Tool execution finished successfully" or smth like this as for now the message generated by llm just disappears and it's a bit confusing form me

We have param for it called: displayToolCalls. I rhink I will set it to true. Normally showing tool call is undesired but in demo app it is confusing, you're right. i set it to true, when calling useLLMfromChatScreen`

Also maybe some predefined prompt for user would be great as I barely know what should I tell the model.

Great recommendation, I'll add something

…ved console logs. Added text about what model can do.
@pweglik pweglik force-pushed the @pw/llm-tool-calling-flashy-demo branch from da0ecc2 to f4506f3 Compare April 28, 2025 07:53
@pweglik
Copy link
Copy Markdown
Contributor Author

pweglik commented Apr 28, 2025

Added text and removed unnecessary code.

Screenshot 2025-04-28 at 09 52 10

Base automatically changed from @pw/support-tokenizer-config to v0.4.0-rc1 April 28, 2025 14:24
pweglik and others added 8 commits April 28, 2025 16:28
## Description

Small docs fixes and adding section about tool calling to `useLLM.md`

## Solves
#212
## Description

Changed the name and some small bugfixes on the side

### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update (improves or adds clarity to existing
documentation)

### Tested on

- [x] iOS
- [x] Android


### Related issues

#205 

### Checklist

- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [ ] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->
## Description

Add method for deleting the message and all following messages. I've
also modified the example so it showcases the feature:





### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update (improves or adds clarity to existing
documentation)

### Tested on

- [x] iOS
- [ ] Android

### Testing instructions

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

[<!-- Add screenshots here, if applicable
-->](https://github.com/user-attachments/assets/bf13746d-9628-4512-a27a-cd9532e01f44)

### Related issues

#206 

### Checklist

- [x] I have performed a self-review of my code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have updated the documentation accordingly
- [x] My changes generate no new warnings
## Description

This PR deletes the use of macro which aborted the ET runtime when the
length of the prompt exceeds the kMaxContextLen. Instead of aborting an
error is returned to the end user and ET_LOG is made as well. Fixes #201

### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update (improves or adds clarity to existing
documentation)

### Tested on

- [ ] iOS
- [ ] Android

### Testing instructions

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

<!-- Add screenshots here, if applicable -->

### Related issues

<!-- Link related issues here using #issue-number -->

### Checklist

- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [ ] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->

---------

Co-authored-by: Norbert Klockiewicz <Nklockiewicz12@gmail.com>
## Description

This PR adds constants for other LLMs like hammer.

### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update (improves or adds clarity to existing
documentation)

### Tested on

- [x] iOS
- [x] Android

### Testing instructions

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

<!-- Add screenshots here, if applicable -->

### Related issues

<!-- Link related issues here using #issue-number -->

### Checklist

- [x] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [ ] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->
## Description

There was a problem with llms exported with bfloat16 on android
resulting in error during forward pass. This PR contains new runtime
with a fix to this problem

### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update (improves or adds clarity to existing
documentation)

### Tested on

- [ ] iOS
- [x] Android

### Testing instructions

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

<!-- Add screenshots here, if applicable -->

### Related issues

<!-- Link related issues here using #issue-number -->

### Checklist

- [x] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [ ] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->
@pweglik pweglik merged commit e7d9563 into v0.4.0-rc1 Apr 28, 2025
2 checks passed
@pweglik pweglik deleted the @pw/llm-tool-calling-flashy-demo branch April 28, 2025 15:39
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.

4 participants