Jev directory
CommunityJev Agents & MCP
TIA — Triage Issue Agent
GitHub issue triage agent built with Eve and Jev. It takes one typed decision per issue through a pipeline of classify, validate, duplicate and apply steps, with dry-run defaults, a label allow-list, and raw Jev answers stored for threshold tuning.
- Stars
- 8
- Reading time
- 2 min
- Published by
- Community
- Added
- Oct 2026
Highlights
- GitHub issue triage agent built with Eve and Jev, taking one typed decision per issue.
- Pipeline steps include classify, validate, duplicate, and apply, with dry-run defaults.
- Never closes, transfers, or converts an issue, and never removes a label a human applied.
- Runs as the hey-tia[bot] GitHub App through Vercel Connect; config lives in .github/tia.yml.
- Raw Jev answers are stored next to every action for threshold tuning.
Questions about this entry
Short answers drawn from the linked project or page.
Follow SETUP.md to deploy it. TIA runs as the hey-tia[bot] GitHub App through Vercel Connect. Local development uses pnpm dev, and production deployment uses pnpm run deploy.
Each repository owns its config in .github/tia.yml, and only maintainers is required. A repository without a valid file is ignored. Other keys include decisions, thresholds, sweep, discord, reproduction, source, and triageMaintainerIssues.
Text written by GitHub users never reaches the model's prompt. An @-mention is reduced by Jev to "triage request or not". The model sees only tia's own tools, and eve's built-ins are off.
apply_triage is the only tool that writes to an issue. It enforces dry-run, one comment of 80 words per run, a label allow-list, and keeps human-applied labels. TIA never closes, transfers, or converts an issue.
Runs that need an approval happen in a Discord channel with Approve and Cancel buttons. Without that channel, those runs are forced to dry-run.
Irreversible actions are handed to maintainers with an @-mention. A repository without a valid .github/tia.yml is ignored, and without a Discord approval channel runs are forced to dry-run.
pnpm dev runs the local agent with the eve terminal UI; pnpm eval runs evals; pnpm typecheck and pnpm build validate; pnpm validate-config checks a tia.yml; pnpm propose-setup previews the setup PR; pnpm backfill dry-runs a backlog.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: Agent Handoff Gate: agents verify what they hand off
X: Jev as an LLM guardrail inside Agentgateway
X: Vercel's fx safety reviewer, measured at 18× faster
Reddit: Early experiments wiring Jev into Pi as a safety layer and model router.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.