From e80d89a31c5e4935d2a09ded1dac3b35ecddc6b6 Mon Sep 17 00:00:00 2001 From: Alex Date: Thu, 2 Apr 2026 14:03:50 -0700 Subject: [PATCH] docs: translate file upload sections to pt-BR, ko, ar Co-Authored-By: Claude Opus 4.5 --- docs/ar/concepts/files.mdx | 4 ++-- docs/ar/concepts/flows.mdx | 36 +++++++++++++++++------------------ docs/ko/concepts/files.mdx | 4 ++-- docs/ko/concepts/flows.mdx | 36 +++++++++++++++++------------------ docs/pt-BR/concepts/files.mdx | 4 ++-- docs/pt-BR/concepts/flows.mdx | 36 +++++++++++++++++------------------ 6 files changed, 60 insertions(+), 60 deletions(-) diff --git a/docs/ar/concepts/files.mdx b/docs/ar/concepts/files.mdx index cc04a6cee..80c2e27da 100644 --- a/docs/ar/concepts/files.mdx +++ b/docs/ar/concepts/files.mdx @@ -134,8 +134,8 @@ result = flow.kickoff( ) ``` - -When deployed on CrewAI Platform, `ImageFile`, `PDFFile`, and other file-typed fields in your flow state automatically get a file upload UI. Users can drag and drop files directly in the Platform interface. Files are stored securely and passed to agents using provider-specific optimizations (inline base64, file upload APIs, or URL references depending on the provider). For API usage examples, see [File Inputs in Flows](/concepts/flows#file-inputs). + +عند النشر على منصة CrewAI، تحصل الحقول من نوع الملف مثل `ImageFile` و `PDFFile` وغيرها في حالة التدفق تلقائيًا على واجهة رفع ملفات. يمكن للمستخدمين سحب وإفلات الملفات مباشرة في واجهة المنصة. يتم تخزين الملفات بشكل آمن وتمريرها إلى الوكلاء باستخدام تحسينات خاصة بالمزود (base64 مضمّن، أو واجهات برمجة لرفع الملفات، أو مراجع URL حسب المزود). للاطلاع على أمثلة استخدام API، راجع [مدخلات الملفات في التدفقات](/ar/concepts/flows#مدخلات-الملفات). ### مع الوكلاء المستقلين diff --git a/docs/ar/concepts/flows.mdx b/docs/ar/concepts/flows.mdx index e3754aba7..5f81292c0 100644 --- a/docs/ar/concepts/flows.mdx +++ b/docs/ar/concepts/flows.mdx @@ -341,9 +341,9 @@ flow.kickoff() من خلال توفير خيارات إدارة الحالة غير المهيكلة والمهيكلة، تمكّن تدفقات CrewAI المطورين من بناء سير عمل ذكاء اصطناعي مرن ومتين في آن واحد، ملبيةً مجموعة واسعة من متطلبات التطبيقات. -### File Inputs +### مدخلات الملفات -When using structured state, you can include file-typed fields using classes from `crewai-files`. This enables file uploads as part of your flow's input: +عند استخدام الحالة المهيكلة، يمكنك تضمين حقول من نوع الملف باستخدام فئات من `crewai-files`. هذا يتيح رفع الملفات كجزء من مدخلات التدفق الخاص بك: ```python from crewai.flow.flow import Flow, start @@ -363,21 +363,21 @@ class OnboardingFlow(Flow[OnboardingState]): return self.state.document ``` -When deployed on **CrewAI Platform**, file-typed fields automatically render as file upload dropzones in the UI. Users can drag and drop files, which are then passed to your flow. +عند النشر على **منصة CrewAI**، تُعرض الحقول من نوع الملف تلقائيًا كمناطق سحب وإفلات لرفع الملفات في واجهة المستخدم. يمكن للمستخدمين سحب وإفلات الملفات، والتي تُمرر بعد ذلك إلى التدفق الخاص بك. -**Kicking off with files via API:** +**بدء التشغيل مع الملفات عبر API:** -The `/kickoff` endpoint auto-detects the request format: -- **JSON body** → normal kickoff -- **multipart/form-data** → file upload + kickoff +تكتشف نقطة النهاية `/kickoff` تنسيق الطلب تلقائيًا: +- **جسم JSON** ← بدء تشغيل عادي +- **multipart/form-data** ← رفع ملف + بدء تشغيل -API users can also pass URL strings directly to file-typed fields—Pydantic coerces them automatically. +يمكن لمستخدمي API أيضًا تمرير سلاسل URL مباشرة إلى الحقول من نوع الملف — يقوم Pydantic بتحويلها تلقائيًا. -### API Usage +### استخدام API -#### Option 1: Multipart kickoff (recommended) +#### الخيار 1: بدء تشغيل multipart (موصى به) -Send files directly with the kickoff request: +أرسل الملفات مباشرة مع طلب بدء التشغيل: ```bash # With files (multipart) — same endpoint @@ -387,9 +387,9 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -F 'cover_image=@/path/to/photo.jpg' ``` -Files are automatically stored and converted to `FileInput` objects. The agent receives the file with provider-specific optimization (inline base64, file upload API, or URL reference depending on the LLM provider). +يتم تخزين الملفات تلقائيًا وتحويلها إلى كائنات `FileInput`. يتلقى الوكيل الملف مع تحسين خاص بالمزود (base64 مضمّن، أو API لرفع الملفات، أو مرجع URL حسب مزود LLM). -#### Option 2: JSON kickoff (no files) +#### الخيار 2: بدء تشغيل JSON (بدون ملفات) ```bash # Without files (JSON) — same endpoint @@ -399,9 +399,9 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -d '{"inputs": {"company_name": "Einstein"}}' ``` -#### Option 3: Separate upload + kickoff +#### الخيار 3: رفع منفصل + بدء تشغيل -This is an alternative to multipart upload when you need to upload files separately from the kickoff request. Upload files first, then reference them by URL: +هذا بديل لرفع multipart عندما تحتاج إلى رفع الملفات بشكل منفصل عن طلب بدء التشغيل. ارفع الملفات أولاً، ثم أشِر إليها بواسطة URL: ```bash # Step 1: Upload @@ -418,11 +418,11 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -d '{"inputs": {"company_name": "Einstein"}, "input_files": {"cover_image": "https://..."}}' ``` -See the Platform API documentation for full `/files` endpoint details. +راجع وثائق Platform API للحصول على تفاصيل كاملة حول نقطة النهاية `/files`. -#### On CrewAI Platform +#### على منصة CrewAI -When using the Platform UI, file-typed fields automatically render as drag-and-drop upload zones. No API calls needed—just drop the file and click Run. +عند استخدام واجهة المنصة، تُعرض الحقول من نوع الملف تلقائيًا كمناطق سحب وإفلات للرفع. لا حاجة لاستدعاءات API — فقط أفلِت الملف وانقر على تشغيل. ## استمرارية التدفق diff --git a/docs/ko/concepts/files.mdx b/docs/ko/concepts/files.mdx index 4f589dfec..dc298ef4c 100644 --- a/docs/ko/concepts/files.mdx +++ b/docs/ko/concepts/files.mdx @@ -134,8 +134,8 @@ result = flow.kickoff( ) ``` - -When deployed on CrewAI Platform, `ImageFile`, `PDFFile`, and other file-typed fields in your flow state automatically get a file upload UI. Users can drag and drop files directly in the Platform interface. Files are stored securely and passed to agents using provider-specific optimizations (inline base64, file upload APIs, or URL references depending on the provider). For API usage examples, see [File Inputs in Flows](/concepts/flows#file-inputs). + +CrewAI 플랫폼에 배포하면 flow 상태의 `ImageFile`, `PDFFile` 및 기타 파일 타입 필드가 자동으로 파일 업로드 UI를 갖게 됩니다. 사용자는 플랫폼 인터페이스에서 직접 파일을 드래그 앤 드롭할 수 있습니다. 파일은 안전하게 저장되고 프로바이더별 최적화(인라인 base64, 파일 업로드 API 또는 프로바이더에 따른 URL 참조)를 사용하여 에이전트에 전달됩니다. API 사용 예제는 [Flows의 파일 입력](/ko/concepts/flows#파일-입력)을 참조하세요. ### 단독 에이전트와 함께 diff --git a/docs/ko/concepts/flows.mdx b/docs/ko/concepts/flows.mdx index 2dcfebbec..10d23415c 100644 --- a/docs/ko/concepts/flows.mdx +++ b/docs/ko/concepts/flows.mdx @@ -334,9 +334,9 @@ flow.kickoff() CrewAI Flows는 비구조적 및 구조적 상태 관리 옵션을 모두 제공함으로써, 개발자들이 다양한 애플리케이션 요구 사항에 맞춰 유연하면서도 견고한 AI 워크플로를 구축할 수 있도록 지원합니다. -### File Inputs +### 파일 입력 -When using structured state, you can include file-typed fields using classes from `crewai-files`. This enables file uploads as part of your flow's input: +구조화된 상태를 사용할 때, `crewai-files`의 클래스를 사용하여 파일 타입 필드를 포함할 수 있습니다. 이를 통해 flow의 입력으로 파일 업로드가 가능합니다: ```python from crewai.flow.flow import Flow, start @@ -356,21 +356,21 @@ class OnboardingFlow(Flow[OnboardingState]): return self.state.document ``` -When deployed on **CrewAI Platform**, file-typed fields automatically render as file upload dropzones in the UI. Users can drag and drop files, which are then passed to your flow. +**CrewAI 플랫폼**에 배포하면 파일 타입 필드가 UI에서 자동으로 파일 업로드 드롭존으로 렌더링됩니다. 사용자는 파일을 드래그 앤 드롭할 수 있으며, 해당 파일은 flow로 전달됩니다. -**Kicking off with files via API:** +**API를 통한 파일 포함 시작:** -The `/kickoff` endpoint auto-detects the request format: -- **JSON body** → normal kickoff -- **multipart/form-data** → file upload + kickoff +`/kickoff` 엔드포인트는 요청 형식을 자동으로 감지합니다: +- **JSON body** → 일반 kickoff +- **multipart/form-data** → 파일 업로드 + kickoff -API users can also pass URL strings directly to file-typed fields—Pydantic coerces them automatically. +API 사용자는 파일 타입 필드에 URL 문자열을 직접 전달할 수도 있습니다 — Pydantic이 자동으로 변환합니다. -### API Usage +### API 사용법 -#### Option 1: Multipart kickoff (recommended) +#### 옵션 1: Multipart kickoff (권장) -Send files directly with the kickoff request: +kickoff 요청과 함께 파일을 직접 전송합니다: ```bash # With files (multipart) — same endpoint @@ -380,9 +380,9 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -F 'cover_image=@/path/to/photo.jpg' ``` -Files are automatically stored and converted to `FileInput` objects. The agent receives the file with provider-specific optimization (inline base64, file upload API, or URL reference depending on the LLM provider). +파일은 자동으로 저장되고 `FileInput` 객체로 변환됩니다. 에이전트는 프로바이더별 최적화(LLM 프로바이더에 따라 인라인 base64, 파일 업로드 API 또는 URL 참조)와 함께 파일을 수신합니다. -#### Option 2: JSON kickoff (no files) +#### 옵션 2: JSON kickoff (파일 없음) ```bash # Without files (JSON) — same endpoint @@ -392,9 +392,9 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -d '{"inputs": {"company_name": "Einstein"}}' ``` -#### Option 3: Separate upload + kickoff +#### 옵션 3: 분리된 업로드 + kickoff -This is an alternative to multipart upload when you need to upload files separately from the kickoff request. Upload files first, then reference them by URL: +kickoff 요청과 별도로 파일을 업로드해야 할 때 multipart 업로드의 대안입니다. 먼저 파일을 업로드한 다음 URL로 참조합니다: ```bash # Step 1: Upload @@ -411,11 +411,11 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -d '{"inputs": {"company_name": "Einstein"}, "input_files": {"cover_image": "https://..."}}' ``` -See the Platform API documentation for full `/files` endpoint details. +`/files` 엔드포인트에 대한 자세한 내용은 플랫폼 API 문서를 참조하세요. -#### On CrewAI Platform +#### CrewAI 플랫폼에서 -When using the Platform UI, file-typed fields automatically render as drag-and-drop upload zones. No API calls needed—just drop the file and click Run. +플랫폼 UI를 사용할 때 파일 타입 필드는 자동으로 드래그 앤 드롭 업로드 영역으로 렌더링됩니다. API 호출이 필요 없습니다 — 파일을 드롭하고 실행을 클릭하면 됩니다. ## 플로우 지속성 diff --git a/docs/pt-BR/concepts/files.mdx b/docs/pt-BR/concepts/files.mdx index ea7a9fae5..91b5faba0 100644 --- a/docs/pt-BR/concepts/files.mdx +++ b/docs/pt-BR/concepts/files.mdx @@ -134,8 +134,8 @@ result = flow.kickoff( ) ``` - -When deployed on CrewAI Platform, `ImageFile`, `PDFFile`, and other file-typed fields in your flow state automatically get a file upload UI. Users can drag and drop files directly in the Platform interface. Files are stored securely and passed to agents using provider-specific optimizations (inline base64, file upload APIs, or URL references depending on the provider). For API usage examples, see [File Inputs in Flows](/concepts/flows#file-inputs). + +Quando implantado na Plataforma CrewAI, campos tipados como arquivo como `ImageFile`, `PDFFile` e outros no estado do seu flow recebem automaticamente uma interface de upload de arquivos. Os usuários podem arrastar e soltar arquivos diretamente na interface da Plataforma. Os arquivos são armazenados de forma segura e passados para os agentes usando otimizações específicas do provedor (base64 inline, APIs de upload de arquivo ou referências por URL dependendo do provedor). Para exemplos de uso da API, consulte [Entradas de Arquivos em Flows](/pt-BR/concepts/flows#entradas-de-arquivos). ### Com Agentes Standalone diff --git a/docs/pt-BR/concepts/flows.mdx b/docs/pt-BR/concepts/flows.mdx index da6b73bca..f338eb837 100644 --- a/docs/pt-BR/concepts/flows.mdx +++ b/docs/pt-BR/concepts/flows.mdx @@ -173,9 +173,9 @@ Cada estado nos flows do CrewAI recebe automaticamente um identificador único ( Ao oferecer as duas opções de gerenciamento de estado, o CrewAI Flows permite que desenvolvedores criem fluxos de IA que sejam ao mesmo tempo flexíveis e robustos, atendendo a uma ampla variedade de requisitos de aplicação. -### File Inputs +### Entradas de Arquivos -When using structured state, you can include file-typed fields using classes from `crewai-files`. This enables file uploads as part of your flow's input: +Ao usar estado estruturado, você pode incluir campos tipados como arquivo usando classes do `crewai-files`. Isso habilita uploads de arquivos como parte da entrada do seu flow: ```python from crewai.flow.flow import Flow, start @@ -195,21 +195,21 @@ class OnboardingFlow(Flow[OnboardingState]): return self.state.document ``` -When deployed on **CrewAI Platform**, file-typed fields automatically render as file upload dropzones in the UI. Users can drag and drop files, which are then passed to your flow. +Quando implantado na **Plataforma CrewAI**, campos tipados como arquivo são renderizados automaticamente como zonas de upload de arquivos na interface. Os usuários podem arrastar e soltar arquivos, que são então passados para o seu flow. -**Kicking off with files via API:** +**Iniciando com arquivos via API:** -The `/kickoff` endpoint auto-detects the request format: -- **JSON body** → normal kickoff -- **multipart/form-data** → file upload + kickoff +O endpoint `/kickoff` detecta automaticamente o formato da requisição: +- **Corpo JSON** → kickoff normal +- **multipart/form-data** → upload de arquivo + kickoff -API users can also pass URL strings directly to file-typed fields—Pydantic coerces them automatically. +Usuários da API também podem passar strings de URL diretamente para campos tipados como arquivo — o Pydantic as converte automaticamente. -### API Usage +### Uso da API -#### Option 1: Multipart kickoff (recommended) +#### Opção 1: Kickoff multipart (recomendado) -Send files directly with the kickoff request: +Envie arquivos diretamente com a requisição de kickoff: ```bash # With files (multipart) — same endpoint @@ -219,9 +219,9 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -F 'cover_image=@/path/to/photo.jpg' ``` -Files are automatically stored and converted to `FileInput` objects. The agent receives the file with provider-specific optimization (inline base64, file upload API, or URL reference depending on the LLM provider). +Os arquivos são armazenados automaticamente e convertidos em objetos `FileInput`. O agente recebe o arquivo com otimização específica do provedor (base64 inline, API de upload de arquivo ou referência por URL dependendo do provedor LLM). -#### Option 2: JSON kickoff (no files) +#### Opção 2: Kickoff JSON (sem arquivos) ```bash # Without files (JSON) — same endpoint @@ -231,9 +231,9 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -d '{"inputs": {"company_name": "Einstein"}}' ``` -#### Option 3: Separate upload + kickoff +#### Opção 3: Upload separado + kickoff -This is an alternative to multipart upload when you need to upload files separately from the kickoff request. Upload files first, then reference them by URL: +Esta é uma alternativa ao upload multipart quando você precisa fazer upload dos arquivos separadamente da requisição de kickoff. Faça o upload dos arquivos primeiro e depois referencie-os por URL: ```bash # Step 1: Upload @@ -250,11 +250,11 @@ curl -X POST https://your-deployment.crewai.com/kickoff \ -d '{"inputs": {"company_name": "Einstein"}, "input_files": {"cover_image": "https://..."}}' ``` -See the Platform API documentation for full `/files` endpoint details. +Consulte a documentação da API da Plataforma para detalhes completos do endpoint `/files`. -#### On CrewAI Platform +#### Na Plataforma CrewAI -When using the Platform UI, file-typed fields automatically render as drag-and-drop upload zones. No API calls needed—just drop the file and click Run. +Ao usar a interface da Plataforma, campos tipados como arquivo são renderizados automaticamente como zonas de arrastar e soltar para upload. Nenhuma chamada de API é necessária — basta soltar o arquivo e clicar em Executar. ## Persistência de Flow