Offer external-source backfill (langfuse/helicone/otlp) at onboard
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- cli, observability
Research direction
Start by reading the tj onboard flow and the existing ingest_langfuse, ingest_helicone, and ingest_otlp adapters to understand how onboarding can invoke them. Check how the CLI handles interactive versus non-interactive input. Done means external backfill is offered explicitly, can be declined, is skipped without waiting on stdin, and stores no credential beyond the one-shot backfill.
Written by the indexing model from the issue text.
Description
Context
On-disk backfill sources (claude-code, codex) auto-backfill by default on tj onboard — no opt-out, last 30 days. Good.
The external-source adapters (langfuse, helicone, otlp) are manual-only via tj backfill <source> because they need an API key or a dump file that the onboard flow doesn't collect. So they can never be silently defaulted the way the on-disk sources are — a new user who has history in one of those tools won't get it backfilled unless they know to run the CLI command themselves.
Ask (product decision, not a bug)
Add an optional interactive prompt in tj onboard that offers to pull history from an external source: "Do you also send traces to Langfuse / Helicone, or export OTLP? Paste an API key or a dump file path to backfill it." Skippable, never silent, no credential stored beyond the one-shot backfill.
Constraints
- Never default silently — always an explicit prompt the user can decline.
- Non-interactive onboard must skip it (no hang waiting on stdin).
- Reuse the existing
ingest_langfuse/ingest_helicone/ingest_otlpadapters — this is onboard wiring only, no adapter changes.
Deferred design question flagged during the backfill audit — filing so it's not lost.
- Dominant language
- Python
- Stars
- 122
- Forks
- 35
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Metabuilder-Labs/tokenjam
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#786 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Metabuilder-Labs/tokenjam#759 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Metabuilder-Labs/tokenjam#728 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#591 ·
Maintainers usually reply within 1 day
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Metabuilder-Labs/tokenjam#559 ·
Maintainers usually reply within 1 day
All issues in Metabuilder-Labs/tokenjam
Similar issues
-
Use mhctools predictor_required=False for saved-result rescoringPossibly taken @iskandr claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#4051 · 1 comment ·
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
awslabs/visual-asset-management-system#514 ·
Maintainers usually reply within 1 day
-
backend bug spec:REQ-053
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nolte/kamerplanter#2547 ·
Maintainers usually reply within 1 day