DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to shorten long command logs and passing test output for the model with DSH Jev Plugin

Removes clearly unneeded progress lines and repeated notices from command output while keeping failures and summaries.

Who it is forA developer whose DSH agent runs long builds or test suites and fills its context with routine output.

The problemLong command output, mostly passing tests and repeated progress notices, uses up context that the agent needs for the actual failure.

The outcomeClearly unneeded log lines are removed after a command returns, failures and summaries stay, and an original-output recovery reference remains.

What you need first

  • A supported DeepSeek Harness release: 0.1.7-rc.1, 0.1.7-rc.2, 0.2.0-rc.1, 0.2.0-rc.2, 0.2.1-alpha.2 or 0.2.1-alpha.3
  • A saved Jev or Luna Decisions connection, with OpenRouter or OpenAI for Luna, and its request address and credential reference
  • The plugin package file added to a DSH profile through the Web UI install steps in the README

Steps

  1. Follow the Install through the Web UI section to add the plugin to a jev profile, then run dsh --profile jev.
  2. Open Jev, then Settings and features, and select the judgment connection.
  3. Enable Long-log admission and Test-log admission.
  4. Run a build or test command that produces long output and check that failures, summaries and named or slow tests are still visible.

Prompt for your agent

Using the repo luobosibing2/dsh-jev-plugin, enable Long-log admission and Test-log admission in a DSH profile named jev, then run <target test command>. Report which passing details were removed and confirm the failures and summary remain. Verify that the original-output recovery reference is present.

Caveat. Judgments about which log lines are unneeded are model decisions and are not guaranteed to match what a developer would keep.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page