run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-07-19 16:43:32 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

[PR #785] [MERGED] Improve Agent Data interface, and add file related fields to extracted data for file tracking #862

New Issue
Closed
opened 2026-02-16 00:19:20 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 00:19:20 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_cloud_services/pull/785
Author: @adrianlyjak
Created: 7/8/2025
Status: ✅ Merged
Merged: 7/9/2025
Merged by: @adrianlyjak

Base: main ← Head: adrian/agent-file-fields

📝 Commits (1)

  • 5c4c525 Add file related fields for file tracking. Simplify API

📊 Changes

7 files changed (+96 additions, -54 deletions)

View changed files

📝 llama_cloud_services/beta/agent_data/__init__.py (+2 -0)
📝 llama_cloud_services/beta/agent_data/client.py (+39 -28)
📝 llama_cloud_services/beta/agent_data/schema.py (+44 -15)
📝 llama_parse/pyproject.toml (+1 -1)
📝 pyproject.toml (+1 -1)
📝 tests/beta/agent_data/test_agent_data_client.py (+8 -8)
📝 tests/beta/agent_data/test_agent_data_schema.py (+1 -1)

📄 Description

  • rename, the _agent_data repetition was kind of too much, Replaced with _item
  • Rename some parameters for consistency
  • Allow creating an agent client without providing the lower level llama_cloud.client, default auth from env vars
  • Fix incorrect FilterOperation typing. Just expects a dict
  • Use the conventional "pending_review" instead of "in_review"

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/llama_cloud_services/pull/785 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 7/8/2025 **Status:** ✅ Merged **Merged:** 7/9/2025 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `adrian/agent-file-fields` --- ### 📝 Commits (1) - [`5c4c525`](https://github.com/run-llama/llama_cloud_services/commit/5c4c5252ecb4f827a1e14ed7e8790a1ccca87ed7) Add file related fields for file tracking. Simplify API ### 📊 Changes **7 files changed** (+96 additions, -54 deletions) <details> <summary>View changed files</summary> 📝 `llama_cloud_services/beta/agent_data/__init__.py` (+2 -0) 📝 `llama_cloud_services/beta/agent_data/client.py` (+39 -28) 📝 `llama_cloud_services/beta/agent_data/schema.py` (+44 -15) 📝 `llama_parse/pyproject.toml` (+1 -1) 📝 `pyproject.toml` (+1 -1) 📝 `tests/beta/agent_data/test_agent_data_client.py` (+8 -8) 📝 `tests/beta/agent_data/test_agent_data_schema.py` (+1 -1) </details> ### 📄 Description - rename, the `_agent_data` repetition was kind of too much, Replaced with `_item` - Rename some parameters for consistency - Allow creating an agent client without providing the lower level `llama_cloud.client`, default auth from env vars - Fix incorrect `FilterOperation` typing. Just expects a dict - Use the conventional "pending_review" instead of "in_review" --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 00:19:20 -05:00
yindo closed this issue 2026-02-16 00:19:20 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#862
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?