Skip to content
This repository was archived by the owner on Aug 13, 2026. It is now read-only.

feat: add TaskMarket discovery tools - #6723

Open
alexluisillo91-creator wants to merge 1 commit into
FlowiseAI:mainfrom
alexluisillo91-creator:codex/taskmarket-tools
Open

feat: add TaskMarket discovery tools#6723
alexluisillo91-creator wants to merge 1 commit into
FlowiseAI:mainfrom
alexluisillo91-creator:codex/taskmarket-tools

Conversation

@alexluisillo91-creator

Copy link
Copy Markdown

Summary

  • add a native TaskMarket tool node with browse, get, and track operations
  • use only TaskMarket's public read-only API; no wallet, credentials, submissions, payments, or mutations
  • validate task IDs and bound pagination, timeouts, filters, and response size
  • mark remote task descriptions and submissions as untrusted data
  • include a Flowise icon and focused unit coverage

Testing

  • pnpm --filter flowise-components build (TypeScript + gulp)
  • jest nodes/tools/TaskMarket/TaskMarket.test.ts --runInBand — 8 tests passed
  • focused ESLint — passed with zero warnings
  • Prettier check — passed
  • live smoke test against the public TaskMarket list, task detail, tag filter, and submissions endpoints

Safety

The node exposes discovery only. It cannot access a wallet, create or submit tasks, transfer funds, or call arbitrary hosts.

This implementation was AI-assisted and then reviewed, built, linted, formatted, and tested locally.

dblagbro added a commit to dblagbro/flow-wiser that referenced this pull request Aug 12, 2026
…ill merging (#18)

The 2026-08-05 snapshot was taken because "upstream repository moves to public
archive on 2026-08-10, which locks issues and pull requests". That did not
happen. Verified 2026-08-12: archived=false, disabled=false, comments still
working, and three pull requests merged on 2026-08-07 -- after the documented
2026-07-29 code freeze and after the snapshot was taken.

Upstream is frozen, not closed. Contributions can still be commented on and, on
this evidence, still merged.

This contradicts docs/PROJECT-LOG.md, docs/product.md and docs/STATUS.md, which
all assert the archive happened. It also makes a public comment on upstream
FlowiseAI#6706 wrong. Both are flagged in DELTA-2026-08-12.md rather than corrected here,
because the licensing narrative is REVIEW REQUIRED and belongs to a human.

Synced:
  * 3 new PRs captured as git am-able patches -- FlowiseAI#6714, FlowiseAI#6723, FlowiseAI#6725
  * 3 upstream-MERGED fixes this fork does not have, captured to
    merged-after-snapshot/ -- FlowiseAI#6680, FlowiseAI#6708, FlowiseAI#6709, all maintainer-authored
  * prs/index.json refreshed 347 -> 346, issues 698 -> 701
  * both indexes normalised to a single JSON array; the originals were 11
    concatenated per-page arrays that parse only with jq -s. Data was complete
    in both, only the shape changed.

Licence check applied to all six new patches: no diff hunks against
packages/server/src/enterprise/ or IdentityManager.ts. All clean, no stripping
required, and no hunk content was read to determine it -- decisions made on the
diff --git path headers alone, per docs/CLEANROOM-PROTOCOL.md.

DELTA-2026-08-12.md also records where Flow-Wiser has already solved a still-open
upstream PR, with the fork's fix being the more complete one in every confirmed
case: FlowiseAI#6670 and FlowiseAI#6642 (the unpinned Docker version -- this fork's founding
defect, still open upstream from two independent reporters), FlowiseAI#6706
(connect-sqlite3), and FlowiseAI#4805 (Node 22, open since 2025-07-06 for the change
ADR-0004 completed this week across ten locations rather than three).

Contributing any of it back is an outward action and is left for authorization.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

1 participant