Skip to content

feat: Add invoice scanning agent implementation#240

Open
dsowinski2 wants to merge 4 commits into
mainfrom
feat/ent-170-add-an-invoice-scanning-agent
Open

feat: Add invoice scanning agent implementation#240
dsowinski2 wants to merge 4 commits into
mainfrom
feat/ent-170-add-an-invoice-scanning-agent

Conversation

@dsowinski2
Copy link
Copy Markdown
Contributor

@dsowinski2 dsowinski2 commented Dec 2, 2025

This PR adds separate plugin with example implementation of "invoice scanning" agent (React and tool calling). It has access to file upload tools and extracts data from invoices in shape of provided json.

Docs use cased to be added.

@dsowinski2 dsowinski2 self-assigned this Dec 2, 2025
Base automatically changed from feat/add-tool-calling-agent-package to main December 8, 2025 13:45
@dsowinski2 dsowinski2 marked this pull request as draft January 29, 2026 11:48
@dsowinski2 dsowinski2 force-pushed the feat/ent-170-add-an-invoice-scanning-agent branch 3 times, most recently from 8546920 to b710977 Compare January 30, 2026 07:25
@dsowinski2 dsowinski2 marked this pull request as ready for review February 3, 2026 08:26
@dsowinski2 dsowinski2 requested a review from mateus-po February 10, 2026 07:00
@dsowinski2 dsowinski2 force-pushed the feat/ent-170-add-an-invoice-scanning-agent branch from b710977 to f3a33cc Compare February 11, 2026 11:52
Copy link
Copy Markdown
Contributor

@mateus-po mateus-po left a comment

Choose a reason for hiding this comment

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

Only comment from me is pertinent to extracting docs updates to separate PR, otherwise looks good:>

Comment thread docs/app/agents/page.tsx
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Similarly as with the competitors research PR, I think that docs updates should be on separate PR.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Why do you think this should be a separate PR?
We got a new feature and its docs i believe it would be better to keep them as a one whole commit, but please let me know

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