AutoGPT

mirror of https://github.com/Significant-Gravitas/AutoGPT.git synced 2026-04-08 03:00:28 -04:00

Author	SHA1	Message	Date
Zamil Majdy	c3698ae887	Merge branch 'dev' of github.com:Significant-Gravitas/AutoGPT into fix/dry-run-simulation-streaming	2026-04-01 06:15:12 +02:00
Zamil Majdy	f821bb2bfa	Merge branch 'dev' of github.com:Significant-Gravitas/AutoGPT into fix/dry-run-simulation-streaming # Conflicts: # autogpt_platform/backend/backend/copilot/tools/helpers.py # autogpt_platform/backend/backend/copilot/tools/test_dry_run.py	2026-03-31 19:09:13 +02:00
Zamil Majdy	2d5f8544ea	Merge branch 'dev' of github.com:Significant-Gravitas/AutoGPT into fix/dry-run-simulation-streaming	2026-03-31 15:17:25 +02:00
Zamil Majdy	6d4f8a4be5	fix(frontend): use regenerated Orval types for UserRateLimitResponse Now that the OpenAPI spec includes user_email and email param, the generated types are correct. Remove manual type assertions and the intersection type on RateLimitDisplay Props.	2026-03-29 09:50:37 +02:00
Zamil Majdy	c6d037f2c2	merge: resolve conflict with dev in useRateLimitManager.ts Keep type assertions for email param and user_email response field since the generated Orval types haven't been regenerated yet to include these backend fields.	2026-03-29 09:43:07 +02:00
Zamil Majdy	419c3b3141	fix(frontend): clear stale execution results before dry-run/no-input runs Port the clearAllNodeExecutionResults call from #12575 so the UI shows fresh output instead of stale results from prior executions. Also fix pre-existing TS errors in admin rate-limit components.	2026-03-29 08:13:23 +02:00
Zamil Majdy	7cd6733ad5	fix(frontend): close first-click simulate race condition with WS subscription Port the fix from #12575: after the WebSocket subscription confirms, invalidate the execution details query so any events published before the subscription was established are refetched. This prevents the first Simulate click from appearing to do nothing.	2026-03-29 08:05:02 +02:00
Zamil Majdy	4468f96279	fix(copilot): resolve host-scoped credentials for authenticated web requests (#12579 ) ## Summary - Fixed `_resolve_discriminated_credentials()` in `helpers.py` to handle URL/host-based credential discrimination (used by `SendAuthenticatedWebRequestBlock`) - Previously, only provider-based discrimination (with `discriminator_mapping`) was handled; URL-based discrimination (with `discriminator` set but no `discriminator_mapping`) was silently skipped - This caused host-scoped credentials to either match the wrong host or fail to match at all when the CoPilot called `run_block` for authenticated HTTP requests - Added 14 targeted tests covering discriminator resolution, host matching, credential resolution integration, and RunBlockTool end-to-end flows ## Root Cause `_resolve_discriminated_credentials()` checked `if field_info.discriminator and field_info.discriminator_mapping:` which excluded host-scoped credentials where `discriminator="url"` but `discriminator_mapping=None`. The URL from `input_data` was never added to `discriminator_values`, so `_credential_is_for_host()` received empty `discriminator_values` and returned `True` for any host-scoped credential regardless of URL match. ## Fix When `discriminator` is set without `discriminator_mapping`, the URL value from `input_data` is now copied into `discriminator_values` on a shallow copy of the field info (to avoid mutating the cached schema). This enables `_credential_is_for_host()` to properly match the credential's host against the target URL. ## Test plan - [x] `TestResolveDiscriminatedCredentials` - 4 tests verifying URL discriminator populates values, handles missing URL, doesn't mutate original, preserves provider/type - [x] `TestFindMatchingHostScopedCredential` - 5 tests verifying correct/wrong host matching, wildcard hosts, multiple credential selection - [x] `TestResolveBlockCredentials` - 3 integration tests verifying full credential resolution with matching/wrong/missing hosts - [x] `TestRunBlockToolAuthenticatedHttp` - 2 end-to-end tests verifying SetupRequirementsResponse when creds missing and BlockDetailsResponse when creds matched - [x] All 28 existing + new tests pass - [x] Ruff lint, isort, Black formatting, pyright typecheck all pass --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-29 08:05:02 +02:00
Zamil Majdy	1a5b2ead70	fix(blocks): raise AIConditionBlock errors instead of swallowing them (#12593 ) ## Why Sentry alert [AUTOGPT-SERVER-8C8](https://significant-gravitas.sentry.io/issues/7367978095/) — `AIConditionBlock` failing in prod with: ``` Invalid 'max_output_tokens': integer below minimum value. Expected a value >= 16, but got 10 instead. ``` Two problems: 1. `max_tokens=10` is below OpenAI's new minimum of 16 2. The `except Exception` handler was calling `logger.error()` which triggered Sentry for what are known block errors, AND silently defaulting to `result=False` — making the block appear to succeed with an incorrect answer ## What - Bump `max_tokens` from 10 to 16 (fixes the root cause) - Remove the `try/except` entirely — the executor already handles exceptions correctly (`ValueError` = known/no Sentry, everything else = unknown/Sentry). The old handler was just swallowing errors and producing wrong results. ## Test plan - [x] Existing `AIConditionBlock` tests pass (block only expects "true"/"false", 16 tokens is plenty) - [x] No more silent `result=False` on errors - [x] No more spurious Sentry alerts from `logger.error()` Fixes AUTOGPT-SERVER-8C8 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-29 08:05:02 +02:00
Nicholas Tindle	e74fa882d8	dx(skills): add /open-pr and /setup-repo skills (#12591 ) ### Why / What / How Why: Agents working in worktrees lack guidance on two of the most common workflows: properly opening PRs (using the repo template, validating test coverage, triggering the review bot) and bootstrapping the repo from scratch with a worktree-based layout. Without these skills, agents either skip steps (no test plan, wrong template) or require manual hand-holding for setup. What: Adds two new Claude Code skills under `.claude/skills/`: - `/open-pr` — A structured PR creation workflow that enforces the canonical `.github/PULL_REQUEST_TEMPLATE.md`, validates test coverage for existing and new behaviors, supports a configurable base branch, and integrates the `/review` bot workflow for agents without local testing capability. Cross-references `/pr-test`, `/pr-review`, and `/pr-address` for the full PR lifecycle. - `/setup-repo` — An interactive repo bootstrapping skill that creates a worktree-based layout (main + reviews + N numbered work branches). Handles .env file provisioning with graceful fallbacks (.env.default, .env.example), copies branchlet config, installs dependencies, and is fully idempotent (safe to re-run). How: Markdown-based SKILL.md files following the existing skill conventions. Both skills use proper bash patterns (seq-based loops instead of brace expansion with variables, existence checks before branch/worktree creation, error reporting on install failures). `/open-pr` delegates to AskUserQuestion-style prompts for base branch selection. `/setup-repo` uses AskUserQuestion for interactive branch count and base branch selection. ### Changes 🏗️ - Added `.claude/skills/open-pr/SKILL.md` — PR creation workflow with: - Pre-flight checks (committed, pushed, formatted) - Test coverage validation (existing behavior not broken, new behavior covered) - Canonical PR template enforcement (read and fill verbatim, no pre-checked boxes) - Configurable base branch (defaults to dev) - Review bot workflow (`/review` comment + 30min wait) for agents without local testing - Related skills table linking `/pr-test`, `/pr-review`, `/pr-address` - Added `.claude/skills/setup-repo/SKILL.md` — Repo bootstrap workflow with: - Interactive setup (branch count: 4/8/16/custom, base branch selection) - Idempotent branch creation (skips existing branches with info message) - Idempotent worktree creation (skips existing directories) - .env provisioning with fallback chain (.env → .env.default → .env.example → warning) - Branchlet config propagation - Dependency installation with success/failure reporting per worktree ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Verified SKILL.md frontmatter follows existing skill conventions - [x] Verified trigger conditions match expected user intents - [x] Verified cross-references to existing skills are accurate - [x] Verified PR template section matches `.github/PULL_REQUEST_TEMPLATE.md` - [x] Verified bash snippets use correct patterns (seq, show-ref, quoted vars) - [x] Pre-commit hooks pass on all commits - [x] Addressed all CodeRabbit, Sentry, and Cursor review comments 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Low Risk > Low risk documentation-only change: adds new markdown skills without modifying runtime code. Main risk is workflow guidance drift (e.g., `.env`/worktree steps) if it diverges from actual repo conventions. > > Overview > Adds two new Claude Code skills under `.claude/skills/` to standardize common developer workflows. > > `/open-pr` documents a PR creation flow that enforces using `.github/PULL_REQUEST_TEMPLATE.md` verbatim, calls out required test coverage, and describes how to trigger/poll the `/review` bot when local testing isn’t available. > > `/setup-repo` documents an idempotent, interactive bootstrap for a multi-worktree layout (creates `reviews` and `branch1..N`, provisions `.env` files with `.env.default`/`.env.example` fallbacks, copies `.branchlet.json`, and installs dependencies), complementing the existing `/worktree` skill. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit `80dbeb1596`. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>	2026-03-29 08:05:02 +02:00
Zamil Majdy	153673ce8e	fix(backend): preserve thinking blocks during transcript compaction (#12574 ) ## Why AutoPilot users hit `invalid_request_error` ("thinking or redacted_thinking blocks in the latest assistant message cannot be modified") when sessions get long enough to trigger transcript compaction. The Anthropic API requires thinking blocks in the last assistant message to be byte-for-byte identical to the original response — our compaction was flattening them to plain text, destroying the cryptographic signatures. Reported in Discord `#breakage` by John Ababseh with session `31d3f08a-cb94-45eb-9fce-56b3f0287ef4`. ## What - `compact_transcript` now splits the transcript into a compressible prefix and a preserved tail (last assistant entry + trailing entries). Only the prefix is compressed; the tail is re-appended verbatim, preserving thinking blocks exactly. - `_flatten_assistant_content` now silently drops `thinking` and `redacted_thinking` blocks instead of creating `[__thinking__]` placeholders — they carry no useful context for compression summaries. - `response_adapter` explicitly handles `ThinkingBlock` (skip gracefully instead of silently falling through the isinstance chain). - `_format_sdk_content_blocks` now passes through raw dict blocks (e.g. `redacted_thinking` that the SDK may not have a typed class for) verbatim to the transcript. ## How The key insight is the Anthropic API's asymmetric constraint: - Last assistant message: thinking/redacted_thinking blocks must be preserved byte-for-byte - Older assistant messages: thinking blocks can be removed entirely `compact_transcript` uses `_find_last_assistant_entry()` to split the JSONL into two parts: 1. Prefix (everything before the last assistant): flattened and compressed normally 2. Tail (last assistant + any trailing user message): preserved verbatim and re-chained via `_rechain_tail()` to maintain the `parentUuid` chain This ensures the API always sees the original thinking blocks in the last assistant message while still achieving meaningful compression on older turns. ## Test plan - [x] 25 new tests across `thinking_blocks_test.py` (TDD: written before implementation) - [x] `_find_last_assistant_entry` splits correctly at last assistant, handles edges (no assistant, index 0, trailing user) - [x] `_rechain_tail` patches parentUuid chain, handles empty tail - [x] `_flatten_assistant_content` strips thinking/redacted_thinking blocks, handles mixed content - [x] `compact_transcript` preserves last assistant's thinking blocks - [x] `compact_transcript` strips thinking from older assistant messages - [x] Edge cases: trailing user message, single assistant, no thinking blocks - [x] `response_adapter` handles ThinkingBlock without crash - [x] `_format_sdk_content_blocks` preserves thinking block format and raw dict blocks - [x] All existing copilot SDK tests pass - [x] Pre-commit hooks (lint, format, typecheck) all pass	2026-03-29 08:05:02 +02:00
Zamil Majdy	6de1585d8b	fix(platform): fix prod Sentry errors and reduce on-call alert noise (#12565 ) ## Why Multiple Sentry issues paging on-call in prod: 1. AUTOGPT-SERVER-8BP: `ConversionError: Failed to convert anthropic/claude-sonnet-4-6 to <enum 'LlmModel'>` — the copilot passes OpenRouter-style provider-prefixed model names (`anthropic/claude-sonnet-4-6`) to blocks, but the `LlmModel` enum only recognizes the bare model ID (`claude-sonnet-4-6`). 2. BUILDER-7GF: `Error invoking postEvent: Method not found` — Sentry SDK internal error on Chrome Mobile Android, not a platform bug. 3. XMLParserBlock: `BlockUnknownError raised by XMLParserBlock with message: Error in input xml syntax` — user sent bad XML but the block raised `SyntaxError`, which gets wrapped as `BlockUnknownError` (unexpected) instead of `BlockExecutionError` (expected). 4. AUTOGPT-SERVER-8BS: `Virus scanning failed for Screenshot 2026-03-26 091900.png: range() arg 3 must not be zero` — empty (0-byte) file upload causes `range(0, 0, 0)` in the virus scanner chunking loop, and the failure is logged at `error` level which pages on-call. 5. AUTOGPT-SERVER-8BT: `ValueError: <Token var=<ContextVar name='current_context'>> was created in a different Context` — OpenTelemetry `context.detach()` fails when the SDK streaming async generator is garbage-collected in a different context than where it was created (client disconnect mid-stream). 6. AUTOGPT-SERVER-8BW: `RuntimeError: Attempted to exit cancel scope in a different task than it was entered in` — anyio's `TaskGroup.__aexit__` detects cancel scope entered in one task but exited in another when `GeneratorExit` interrupts the SDK cleanup during client disconnect. 7. Workspace UniqueViolationError: `UniqueViolationError: Unique constraint failed on (workspaceId, path)` — race condition during concurrent file uploads handled by `WorkspaceManager._persist_db_record` retry logic, but Sentry still captures the exception at the raise site. 8. Library UniqueViolationError: `UniqueViolationError` on `LibraryAgent (userId, agentGraphId, agentGraphVersion)` — race conditions in `add_graph_to_library` and `create_library_agent` caused crashes or silent data loss. 9. Graph version collision: `UniqueViolationError` on `AgentGraph (id, version)` — copilot re-saving an agent at an existing version collides with the primary key. ## What ### Backend: `LlmModel._missing_()` for provider-prefixed model names - Adds `_missing_` classmethod to `LlmModel` enum that strips the provider prefix (e.g., `anthropic/`) when direct lookup fails - Self-contained in the enum — no changes to the generic type conversion system ### Frontend: Filter Sentry SDK noise - Adds `postEvent: Method not found` to `ignoreErrors` — a known Sentry SDK issue on certain mobile browsers ### Backend: XMLParserBlock — raise ValueError instead of SyntaxError - Changed `_validate_tokens()` to raise `ValueError` instead of `SyntaxError` - Changed the `except SyntaxError` handler in `run()` to re-raise as `ValueError` - This ensures `Block.execute()` wraps XML parsing failures as `BlockExecutionError` (expected/user-caused) instead of `BlockUnknownError` (unexpected/alerts Sentry) ### Backend: Virus scanner — handle empty files + reduce alert noise - Added early return for empty (0-byte) files in `scan_file()` to avoid `range() arg 3 must not be zero` when `chunk_size` is 0 - Added `max(1, len(content))` guard on `chunk_size` as defense-in-depth - Downgraded `scan_content_safe` failure log from `error` to `warning` so single-file scan failures don't page on-call via Sentry ### Backend: Suppress SDK client cleanup errors on SSE disconnect - Replaced `async with ClaudeSDKClient` in `_run_stream_attempt` with manual `__aenter__`/`__aexit__` wrapped in new `_safe_close_sdk_client()` helper - `_safe_close_sdk_client()` catches `ValueError` (OTEL context token mismatch) and `RuntimeError` (anyio cancel scope in wrong task) during `__aexit__` and logs at `debug` level — these are expected when SSE client disconnects mid-stream - Added `_is_sdk_disconnect_error()` helper for defense-in-depth at the outer `except BaseException` handler in `stream_chat_completion_sdk` - Both Sentry errors (8BT and 8BW) are now suppressed without affecting normal cleanup flow ### Backend: Filter workspace UniqueViolationError from Sentry alerts - Added `before_send` filter in `_before_send()` to drop `UniqueViolationError` events where the message contains `workspaceId` and `path` - The error is already handled by `WorkspaceManager._persist_db_record` retry logic — it must propagate for the retry logic to work, so the fix is at the Sentry filter level rather than catching/suppressing at source ### Backend: Library agent race condition fixes - `add_graph_to_library`: Replaced check-then-create pattern with create-then-catch-`UniqueViolationError`-then-update. On collision, updates the existing row (restoring soft-deleted/archived agents) instead of crashing. - `create_library_agent`: Replaced `create` with `upsert` on the `(userId, agentGraphId, agentGraphVersion)` composite unique constraint, so concurrent adds restore soft-deleted entries instead of throwing. ### Backend: Graph version auto-increment on collision - `__create_graph` now checks if the `(id, version)` already exists before `create_many`, and auto-increments the version to `max_existing + 1` to avoid `UniqueViolationError` when the copilot re-saves an agent. ### Backend: Workspace `get_or_create_workspace` upsert - Changed from find-then-create to `upsert` to atomically handle concurrent workspace creation. ## Test plan - [x] `LlmModel("anthropic/claude-sonnet-4-6")` resolves correctly - [x] `LlmModel("claude-sonnet-4-6")` still works (no regression) - [x] `LlmModel("invalid/nonexistent-model")` still raises `ValueError` - [x] XMLParserBlock: unclosed tags, extra closing tags, empty XML all raise `ValueError` - [x] XMLParserBlock: `SyntaxError` from gravitasml library is caught and re-raised as `ValueError` - [x] Virus scanner: empty file (0 bytes) returns clean without hitting ClamAV - [x] Virus scanner: single-byte file scans normally (regression test) - [x] Virus scanner: `scan_content_safe` logs at WARNING not ERROR on failure - [x] SDK disconnect: `_is_sdk_disconnect_error` correctly identifies cancel scope and context var errors - [x] SDK disconnect: `_is_sdk_disconnect_error` rejects unrelated errors - [x] SDK disconnect: `_safe_close_sdk_client` suppresses ValueError, RuntimeError, and unexpected exceptions - [x] SDK disconnect: `_safe_close_sdk_client` calls `__aexit__` on clean exit - [x] Library: `add_graph_to_library` creates new agent on first call - [x] Library: `add_graph_to_library` updates existing on UniqueViolationError - [x] Library: `create_library_agent` uses upsert to handle concurrent adds - [x] All existing workspace overwrite tests still pass - [x] All tests passing (existing + 4 XML syntax + 3 virus scanner + 10 SDK disconnect + library tests)	2026-03-29 08:05:02 +02:00
Zamil Majdy	f42b04f374	feat(platform): add shared admin user search + rate-limit modal on spending page (#12577 ) ## Why Admin rate-limit management required manually entering user UUIDs. The spending page already had user search but it wasn't reusable. ## What - Extract `AdminUserSearch` as shared component from spending page search - Add rate-limit modal (usage bars + reset) to spending page user rows - Add email/name/UUID search to standalone rate-limits page - Backend: add email query parameter to rate-limit endpoint ## How - `AdminUserSearch` in `admin/components/` — reused by both spending and rate-limits - `RateLimitModal` opens from spending page "Rate Limits" button - Backend `_resolve_user_id()` accepts email or user_id - Smart routing: exact email → direct lookup, UUID → direct, partial → fuzzy search ### Follow-up - `AdminUserSearch` is a plain text input with no typeahead/fuzzy suggestions — consider adding autocomplete dropdown with debounced search ### Checklist 📋 - [x] Shared search component extracted and reused - [x] Tests pass - [x] Type-checked	2026-03-29 08:05:02 +02:00
Zamil Majdy	f93556ac69	fix(frontend): clear node statuses before dry-run simulation in builder The builder's simulate button runs executeGraph with dry_run=true but did not call cleanNodesStatuses() beforehand. Without clearing previous node statuses, the polling-based status updates from the new execution were not visually reflected — stale state from a prior run prevented new RUNNING/COMPLETED badges from appearing. The normal run path (via RunInputDialog) already calls cleanNodesStatuses() at line 157 of useRunInputDialog.ts. This fix aligns the dry-run path with the same behavior. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-28 07:41:54 +00:00
Zamil Majdy	8cc2349717	fix(copilot): fix return type annotation, add strip() comment, clean up test yield style	2026-03-27 11:03:07 +07:00
Zamil Majdy	35dbae4469	test(copilot): add regression test for prompt error pin exclusion Verify that build_simulation_prompt excludes "error" from the "MUST include" output pin list, preventing contradiction with the "OMIT error unless simulating a logical error" instruction.	2026-03-27 10:41:07 +07:00
Zamil Majdy	49a3f0f492	fix(copilot): resolve prompt contradiction, clean up leftover variable, clarify guard comment - Exclude "error" from the "MUST include" output pin list in the simulator prompt to avoid contradicting the "OMIT error unless simulating a logical error" instruction - Inline displayOutputs back into .map() since filtering was moved to simulator - Add clarifying comment about block_id dependency in isRunBlockErrorOutput fallback guard	2026-03-27 10:37:19 +07:00
Zamil Majdy	b7aa293a86	fix(platform): drop empty error pins at simulator source instead of patching downstream The simulator was yielding empty "error" pins (error="") for every block with an error output, then helpers.py and the frontend had to filter them out. This moves the fix to the source: the simulator now omits empty/blank error pins entirely, so no downstream patching is needed. - simulator.py: skip yielding error pins with empty/blank string values - helpers.py: remove the clean_outputs filtering (no longer needed) - helpers.tsx: remove isEmptyErrorPin helper and dry-run-specific filtering - BlockOutputCard.tsx: remove dry-run-specific empty error pin filter - tests updated to reflect new behavior	2026-03-27 10:11:24 +07:00
Zamil Majdy	91037e96ea	chore: re-trigger CI checks	2026-03-27 00:39:56 +07:00
Zamil Majdy	6adb436be7	Merge branch 'dev' of github.com:Significant-Gravitas/AutoGPT into fix/dry-run-simulation-streaming	2026-03-26 23:38:53 +07:00
Zamil Majdy	284af1f4fd	fix(frontend): scope getAccordionMeta empty error pin filter to dry-run only Aligns getAccordionMeta with BlockOutputCard: only filter out empty error pins for dry-run outputs. For real executions, empty error pins are meaningful signals and should be counted in accordion metadata.	2026-03-26 20:48:50 +07:00
Zamil Majdy	67db950b8a	fix(copilot): move relative import after @/ imports in BlockOutputCard	2026-03-26 20:39:04 +07:00
Zamil Majdy	3bf6ad2d16	fix(copilot): address PR review - scope filter to dry-run, extract helper - Scope empty-error pin filter to dry-run only in BlockOutputCard (real executions keep empty error as meaningful "no error" signal) - Extract shared isEmptyErrorPin() helper in helpers.tsx for DRY - Add vacuous truth guard (and v) to backend filter for clarity	2026-03-26 20:36:14 +07:00
Zamil Majdy	c562cbd121	fix(copilot): fix dry-run simulation showing INCOMPLETE/error status The dry-run block simulation was showing misleading "INCOMPLETE" status and "error" output even on successful simulations. Root causes: 1. The simulator always includes an empty "error" pin (set to "") for blocks that define one. This caused the frontend to render a misleading "error" output section and the LLM to misinterpret the result as a failure, reporting "INCOMPLETE" to the user. 2. The frontend's isRunBlockErrorOutput() check was too broad — using `"error" in output` which could match non-error responses. 3. The parseOutput() fallback for untyped payloads could incorrectly classify a BlockOutputResponse as an ErrorResponse. Fixes: - Backend: Strip empty "error" pins from dry-run outputs and add explicit "Status: COMPLETED" to the response message - Frontend: Tighten isRunBlockErrorOutput() to only match actual error responses (type=error), not block outputs with error in outputs dict - Frontend: Fix parseOutput() to exclude BlockOutputResponse from error fallback matching - Frontend: Filter empty error pins from BlockOutputCard display and output key counting in accordion metadata	2026-03-26 20:32:13 +07:00

Compare commits

24 Commits

feat/keep- ... fix/dry-ru

Diff Content Not Available

Compare commits

24 Commits feat/keep- ... fix/dry-ru

Diff Content Not Available

24 Commits

feat/keep- ... fix/dry-ru