fern-api
Recap information about errors/failures at the bottom
Which Fern component?
Fern CLI
How important is this?
P3 - Low (Nice to have)
What's the feature?
The Fern CLI produces a lot of output. Sometimes, a failure occurs and I don't even notice anything went wrong because the error was logged 120 lines ago and my terminal has moved on. It would save me time and frustration if I could rely on all errors or failures being written at the bottom and not have to scroll to see what the issue was.
In the particular case that is prompting me to write about this, the error I'm seeing is
ERROR 2025-10-27T18:02:12.379Z [unioned]: Download ../tts Skipping parsing document tts-asyncapi.json
in this case, the fern check process isn't even exiting non-zero, it's just happily skipping over the schema it should be validating, so that's a bigger usability problem, but I know in other cases where the fern CLI does end up failing I typically have to scroll up many many lines in order to find the information I need to help debug.
This wouldn't just help me also. I've been using Claude code as an assistant to help me with some fern things, and when it comes to commands with long output, the strategy it uses is often to tail the last 20 lines or so because it knows it doesn't want to clobber its context. Putting all error output at the bottom (ideally with a stack trace as per #10105) is pretty standard behavior for CLI tools, and the deficiency I think is a real barrier for successfully adopting the fern CLI in ai-driven workflows.
Any alternatives?
No response
Are you interested in contributing this feature?
No
Hi! @twitchard i have implemented the fix for the CLI error visibility issue errors now get collected and displayed at the bottom of the output with proper exit codes, so no more hunting through pages of logs. let me know
