feat(backend/blocks): add ConcatenateListsBlock

[mewaeltsegay]

feat(backend/blocks): add ConcatenateListsBlock

Description

This PR implements a new block ConcatenateListsBlock that concatenates multiple lists into a single list. This addresses the "good first issue" for implementing a list concatenation block in the platform/blocks area.

The block takes a list of lists as input and combines all elements in order into a single concatenated list. This is useful for workflows that need to merge data from multiple sources or combine results from different operations.

Changes 🏗️

• Added ConcatenateListsBlock class in autogpt_platform/backend/backend/blocks/data_manipulation.py

  • Input: lists: List[List[Any]] - accepts a list of lists to concatenate
  • Output: concatenated_list: List[Any] - returns a single concatenated list
  • Error output: error: str - provides clear error messages for invalid input types
  • Block ID: 3cf9298b-5817-4141-9d80-7c2cc5199c8e
  • Category: BlockCategory.BASIC (consistent with other list manipulation blocks)

• Added comprehensive test suite in autogpt_platform/backend/test/blocks/test_concatenate_lists.py

  • Tests using built-in test_input/test_output validation
  • Manual test cases covering edge cases (empty lists, single list, empty input)
  • Error handling tests for invalid input types
  • Category consistency verification
  • All tests passing

• Implementation details:

  • Uses extend() method for efficient list concatenation
  • Preserves element order from all input lists
  • Runtime type validation: Explicitly checks isinstance(lst, list) before calling extend() to prevent:
    • Strings being iterated character-by-character (e.g., extend("abc") → ['a', 'b', 'c'])
    • Non-iterable types causing TypeError (e.g., extend(1))
  • Clear error messages indicating which index has invalid input
  • Handles edge cases: empty lists, empty input, single list, None values
  • Follows existing block patterns and conventions

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • Run poetry run pytest test/blocks/test_concatenate_lists.py -v - all tests pass
  • Verified block can be imported and instantiated
  • Tested with built-in test cases (4 test scenarios)
  • Tested manual edge cases (empty lists, single list, empty input)
  • Tested error handling for invalid input types
  • Verified category is BASIC for consistency
  • Verified no linting errors
  • Confirmed block follows same patterns as other blocks in data_manipulation.py

Code Quality:

• Code follows existing patterns and conventions
• Type hints are properly used
• Documentation strings are clear and descriptive
• Runtime type validation implemented
• Error handling with clear error messages
• No linting errors
• Prisma client generated successfully

Testing

Test Results:

test/blocks/test_concatenate_lists.py::test_concatenate_lists_block_builtin_tests PASSED
test/blocks/test_concatenate_lists.py::test_concatenate_lists_manual PASSED

============================== 2 passed in 8.35s ==============================

Test Coverage:

• Basic concatenation: [[1, 2, 3], [4, 5, 6]] → [1, 2, 3, 4, 5, 6]
• Mixed types: [["a", "b"], ["c"], ["d", "e", "f"]] → ["a", "b", "c", "d", "e", "f"]
• Empty list handling: [[1, 2], []] → [1, 2]
• Empty input: [] → []
• Single list: [[1, 2, 3]] → [1, 2, 3]
• Error handling: Invalid input types (strings, non-lists) produce clear error messages
• Category verification: Confirmed BlockCategory.BASIC for consistency

Review Feedback Addressed

• Category Consistency: Changed from BlockCategory.DATA to BlockCategory.BASIC to match other list manipulation blocks (AddToListBlock, FindInListBlock, etc.)
• Type Robustness: Added explicit runtime validation with isinstance(lst, list) check before calling extend() to prevent:
  • Strings being iterated character-by-character
  • Non-iterable types causing TypeError
• Error Handling: Added error output field with clear, descriptive error messages indicating which index has invalid input
• Test Coverage: Added test case for error handling with invalid input types

Related Issues

• Addresses: "Implement block to concatenate lists" (good first issue, platform/blocks, hacktoberfest)

Notes

• This is a straightforward data manipulation block that doesn't require external dependencies
• The block will be automatically discovered by the block loading system
• No database or configuration changes required
• Compatible with existing workflow system
• All review feedback has been addressed and incorporated

---

Note

Adds a new list utility and updates docs.

• New block: ConcatenateListsBlock in backend/blocks/data_manipulation.py
  • Input lists: List[List[Any]]; outputs concatenated_list or error
  • Skips None entries; emits error for non-list items; preserves order
• Docs: Adds "Concatenate Lists" section to docs/integrations/basic.md and links it in docs/integrations/README.md
• Contributor guide: New docs/CLAUDE.md with manual doc section guidelines

^{Written by Cursor Bugbot for commit 4f56dd8. This will update automatically on new commits. Configure here.}

[coderabbitai]

Walkthrough

Adds a new ConcatenateListsBlock implementation (input validation, concatenation, test cases) and corresponding documentation updates including a new docs entry and duplicated manual block sections plus documentation guidelines in CLAUDE.md.

Changes

Cohort / File(s)	Summary
Backend — new block autogpt_platform/backend/backend/blocks/data_manipulation.py	Added ConcatenateListsBlock with Input (lists: List[List[Any]]) and Output (concatenated_list: List[Any], error: str), run validation/concatenation logic, and test inputs/outputs.
Docs — CLAUDE guidelines docs/CLAUDE.md	Added block documentation guidelines and structured manual block template sections (How It Works, Use Case, Style Guidelines) with examples.
Docs — README index docs/integrations/README.md	Inserted "Concatenate Lists" entry under Basic Operations pointing to the block documentation anchor.
Docs — Basic operations docs docs/integrations/basic.md	Added documentation for "Concatenate Lists" — note: the section appears duplicated (two identical manual block sections added).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hop through lists both wide and small,
I check each item, I hear the call.
None I skip, wrong types I flag,
Then stitch them true into one neat bag.
Joyful tails and a tidy hall! 🥕✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding a new ConcatenateListsBlock class to the backend blocks module.
Description check	✅ Passed	The PR description provides a comprehensive overview of changes, including block implementation details, test coverage, and addressed feedback, clearly relating to the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

This PR targets the master branch but does not come from dev or a hotfix/* branch.

Automatically setting the base branch to dev.

[CLAassistant]

All committers have signed the CLA.

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	5076be1
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/6933545c0349b40008c59047

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 4 🔵🔵🔵🔵⚪

🧪 PR contains tests

🔒 Security concerns Sensitive information handling: The new GoogleDriveFile includes a hidden _credentials_id propagated through block outputs and API; ensure this identifier is not exposed to unauthorized clients, is scoped per-user, and cannot be used to escalate access. Also review the new load-store-agents script for safe handling of test data and that no production credentials/emails are inadvertently created in non-test environments.

⚡ Recommended focus areas for review API Contract Change Replaced GoogleDrivePickerField with GoogleDriveFileField and introduced embedded auto_credentials; verify all existing blocks/frontends consuming the old picker format still function, and ensure backward compatibility or appropriate migrations for json_schema_extra keys and field shapes. *, title: str, description: str | None = None, credentials_kwarg: str = "credentials", credentials_scopes: list[str] | None = None, allowed_views: list[AttachmentView] | None = None, allowed_mime_types: list[str] | None = None, placeholder: str | None = None, **kwargs: Any, ) -> Any: """ Creates a Google Drive file input field with auto-generated credentials. This field type produces a single UI element that handles both: 1. Google OAuth authentication 2. File selection via Google Drive Picker The system automatically generates a credentials field, and the credentials are passed to the run() method using the specified kwarg name. Args: title: Field title shown in UI description: Field description/help text credentials_kwarg: Name of the kwarg that will receive GoogleCredentials in the run() method (default: "credentials") credentials_scopes: OAuth scopes required (default: drive.file) allowed_views: List of view types to show in picker (default: ["DOCS"]) allowed_mime_types: Filter by MIME types placeholder: Placeholder text for the button **kwargs: Additional SchemaField arguments Returns: Field definition that produces GoogleDriveFile Example: >>> class MyBlock(Block): ... class Input(BlockSchemaInput): ... spreadsheet: GoogleDriveFile = GoogleDriveFileField( ... title="Select Spreadsheet", ... credentials_kwarg="creds", ... allowed_views=["SPREADSHEETS"], ... ) ... ... async def run( ... self, input_data: Input, *, creds: GoogleCredentials, **kwargs ... ): ... # creds is automatically populated ... file = input_data.spreadsheet """ # Determine scopes - drive.file is sufficient for picker-selected files scopes = credentials_scopes or ["https://www.googleapis.com/auth/drive.file"] # Build picker configuration with auto_credentials embedded picker_config = { "multiselect": False, "allow_folder_selection": False, "allowed_views": list(allowed_views) if allowed_views else ["DOCS"], "scopes": scopes, # Auto-credentials config tells frontend to include _credentials_id in output "auto_credentials": { "provider": "google", "type": "oauth2", "scopes": scopes, "kwarg_name": credentials_kwarg, }, } if allowed_mime_types: picker_config["allowed_mime_types"] = list(allowed_mime_types) return SchemaField( default=None, title=title, description=description, placeholder=placeholder or "Select from Google Drive", # Use google-drive-picker format so frontend renders existing component format="google-drive-picker", advanced=False, json_schema_extra={ "google_drive_picker_config": picker_config, # Also keep auto_credentials at top level for backend detection "auto_credentials": { "provider": "google", "type": "oauth2", "scopes": scopes, "kwarg_name": credentials_kwarg, }, **kwargs, }, ) Credentials Handling New auto-credentials acquisition loop infers _credentials_id from input dicts; validate behavior when inputs are pydantic models vs dicts, and confirm locks are always released and no duplicate acquisitions occur when both explicit credentials and auto-credentials exist. field_name = info["field_name"] field_data = input_data.get(field_name) if field_data and isinstance(field_data, dict): # Check if _credentials_id key exists in the field data if "_credentials_id" in field_data: cred_id = field_data["_credentials_id"] if cred_id: # Credential ID provided - acquire credentials provider = info.get("config", {}).get( "provider", "external service" ) file_name = field_data.get("name", "selected file") try: credentials, lock = await creds_manager.acquire( user_id, cred_id ) creds_locks.append(lock) extra_exec_kwargs[kwarg_name] = credentials except ValueError: # Credential was deleted or doesn't exist raise ValueError( f"Authentication expired for '{file_name}' in field '{field_name}'. " f"The saved {provider.capitalize()} credentials no longer exist. " f"Please re-select the file to re-authenticate." ) # else: _credentials_id is explicitly None, skip credentials (for chained data) else: # _credentials_id key missing entirely - this is an error provider = info.get("config", {}).get("provider", "external service") file_name = field_data.get("name", "selected file") raise ValueError( f"Authentication missing for '{file_name}' in field '{field_name}'. " f"Please re-select the file to authenticate with {provider.capitalize()}." ) output_size = 0 Scope/Permissions GoogleSheetsCreateSpreadsheetBlock now uses Drive API with drive.file scope and builds both Drive and Sheets services; confirm scopes are sufficient for create + subsequent Sheets batchUpdate, and that preserving _credentials_id in outputs does not leak or mismatch credential references. class GoogleSheetsCreateSpreadsheetBlock(Block): class Input(BlockSchemaInput): # Explicit credentials since this block creates a file (no file picker) credentials: GoogleCredentialsInput = GoogleCredentialsField( ["https://www.googleapis.com/auth/drive.file"] ) title: str = SchemaField( description="The title of the new spreadsheet", ) sheet_names: list[str] = SchemaField( description="List of sheet names to create (optional, defaults to single 'Sheet1')", default=["Sheet1"], ) class Output(BlockSchemaOutput): result: dict = SchemaField( description="The result containing spreadsheet ID and URL", ) spreadsheet: GoogleDriveFile = SchemaField( description="The created spreadsheet as a GoogleDriveFile (for chaining to other blocks)", ) spreadsheet_id: str = SchemaField( description="The ID of the created spreadsheet", ) spreadsheet_url: str = SchemaField( description="The URL of the created spreadsheet", ) error: str = SchemaField( description="Error message if any", ) def __init__(self): super().__init__( id="c8d4c0d3-c76e-4c2a-8c66-4119817ea3d1", description="This block creates a new Google Sheets spreadsheet with specified sheets.", categories={BlockCategory.DATA}, input_schema=GoogleSheetsCreateSpreadsheetBlock.Input, output_schema=GoogleSheetsCreateSpreadsheetBlock.Output, disabled=GOOGLE_SHEETS_DISABLED, test_input={ "credentials": TEST_CREDENTIALS_INPUT, "title": "Test Spreadsheet", "sheet_names": ["Sheet1", "Data", "Summary"], }, test_credentials=TEST_CREDENTIALS, test_output=[ ( "spreadsheet", GoogleDriveFile( id="1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms", name="Test Spreadsheet", mimeType="application/vnd.google-apps.spreadsheet", url="https://docs.google.com/spreadsheets/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms/edit", iconUrl="https://www.gstatic.com/images/branding/product/1x/sheets_48dp.png", isFolder=False, _credentials_id=TEST_CREDENTIALS_INPUT[ "id" ], # Preserves credential ID for chaining ), ), ("spreadsheet_id", "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms"), ( "spreadsheet_url", "https://docs.google.com/spreadsheets/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms/edit", ), ("result", {"success": True}), ], test_mock={ "_create_spreadsheet": lambda *args, **kwargs: { "spreadsheetId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms", "spreadsheetUrl": "https://docs.google.com/spreadsheets/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms/edit", "title": "Test Spreadsheet", }, }, ) async def run( self, input_data: Input, *, credentials: GoogleCredentials, **kwargs ) -> BlockOutput: drive_service = _build_drive_service(credentials) sheets_service = _build_sheets_service(credentials) result = await asyncio.to_thread( self._create_spreadsheet, drive_service, sheets_service, input_data.title, input_data.sheet_names, ) if "error" in result: yield "error", result["error"] else: spreadsheet_id = result["spreadsheetId"] spreadsheet_url = result["spreadsheetUrl"] # Output the GoogleDriveFile for chaining (includes credentials_id) yield "spreadsheet", GoogleDriveFile( id=spreadsheet_id, name=result.get("title", input_data.title), mimeType="application/vnd.google-apps.spreadsheet", url=spreadsheet_url, iconUrl="https://www.gstatic.com/images/branding/product/1x/sheets_48dp.png", isFolder=False, _credentials_id=input_data.credentials.id, # Preserve credentials for chaining ) yield "spreadsheet_id", spreadsheet_id yield "spreadsheet_url", spreadsheet_url yield "result", {"success": True} def _create_spreadsheet( self, drive_service, sheets_service, title: str, sheet_names: list[str] ) -> dict: try: # Create blank spreadsheet using Drive API file_metadata = { "name": title, "mimeType": "application/vnd.google-apps.spreadsheet", } result = ( drive_service.files() .create(body=file_metadata, fields="id, webViewLink") .execute() ) spreadsheet_id = result["id"] spreadsheet_url = result.get( "webViewLink", f"https://docs.google.com/spreadsheets/d/{spreadsheet_id}/edit", ) # Rename first sheet if custom name provided (default is "Sheet1") if sheet_names and sheet_names[0] != "Sheet1": # Get first sheet ID and rename it meta = ( sheets_service.spreadsheets() .get(spreadsheetId=spreadsheet_id) .execute() ) first_sheet_id = meta["sheets"][0]["properties"]["sheetId"] sheets_service.spreadsheets().batchUpdate( spreadsheetId=spreadsheet_id, body={ "requests": [ { "updateSheetProperties": { "properties": { "sheetId": first_sheet_id, "title": sheet_names[0], }, "fields": "title", } } ] }, ).execute() # Add additional sheets if requested if len(sheet_names) > 1: requests = [ {"addSheet": {"properties": {"title": name}}} for name in sheet_names[1:] ] sheets_service.spreadsheets().batchUpdate( spreadsheetId=spreadsheet_id, body={"requests": requests} ).execute()

[deepsource-io]

Here's the code health analysis summary for commits 8be3c88..5076be1. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	5076be1
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/6933545c10c1c6000811d766

[majdyz]

@claude the test in the block should covers the testing need can we remove autogpt_platform/backend/test/blocks/test_concatenate_lists.py ?

[claude]

Claude encountered an error —— View job

Failed with exit code 128

---

I'll analyze this and get back to you.

[majdyz]

Thank you for your contribution!

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docs/integrations/basic.md`:
- Around line 637-671: Remove the duplicate "## Concatenate Lists" section so
only one canonical copy remains; locate both occurrences by the heading text "##
Concatenate Lists" and delete the redundant block (keeping the first or most
complete instance), ensuring you preserve the heading, the "What it is"/"How it
works"/"Inputs"/"Outputs"/"Possible use case" subsections and any manual markers
(<!-- MANUAL: ... -->) in the retained section so anchors and references remain
intact.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 25184fb and 4f56dd8.

📒 Files selected for processing (3)

• docs/CLAUDE.md
• docs/integrations/README.md
• docs/integrations/basic.md

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-11-25T08:48:33.246Z

Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Check for existing CLAUDE.md files that provide additional context. Follow established patterns and conventions already in the codebase. Maintain consistency with existing code style and architecture

Applied to files:

• docs/CLAUDE.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)

• GitHub Check: types
• GitHub Check: Seer Code Review
• GitHub Check: Cursor Bugbot
• GitHub Check: Analyze (python)
• GitHub Check: test (3.11)
• GitHub Check: test (3.12)
• GitHub Check: test (3.13)
• GitHub Check: Check PR Status

🔇 Additional comments (2)

docs/integrations/README.md (1)

34-34: LGTM!

The new table entry for "Concatenate Lists" is correctly formatted, properly ordered alphabetically, and follows the established pattern for block documentation entries.

docs/CLAUDE.md (1)

1-44: Remove or revise concerns about location and redundancy; clarify actual scope.

The file location and purpose are appropriate:

1. Location is consistent: This follows the established pattern of location-specific CLAUDE.md guidance (e.g., autogpt_platform/CLAUDE.md exists). A docs/-focused file is appropriate for documentation-specific guidance.

2. No redundancy detected: Existing files cover different scope:

   • autogpt_platform/CLAUDE.md - Platform development, architecture, testing
   • .github/copilot-instructions.md - General Copilot workflow for entire repo
   • docs/CLAUDE.md - Documentation standards for block documentation (no existing coverage)

3. Scope is appropriately focused: While specific to docs/integrations/ block documentation, the guidelines ("How It Works", "Use Case", "Style Guidelines") are general enough to apply to all blocks, not just Concatenate Lists.

4. Audience is implicit but clear: The filename convention CLAUDE.md establishes this is guidance for Claude/AI assistants, consistent with other guidance files in the repository. This aligns with learnings to maintain consistency with established patterns.

The file serves a legitimate purpose: standardizing how block documentation is formatted and explained across the integrations section.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}