Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature]: Discuss fork contributions, including an animated welcome crab

Closed
  • Is something wrong?
#475 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@ayush5harma is already working on this.

Since Oct 14, 2026.

Assessment

This issue has not been assessed yet.

Description

area: tui type: feature

Problem Statement

I maintain a fork with some additional UI and workflow features and would like to contribute selected parts upstream. This is a request to agree the next scope, not a proposal to merge the fork wholesale or open parallel PRs.

The existing discussions already cover /agents (#439), output presentation (#461), launch configuration (#462), hook/startup visibility (#463), /reload (#464), and /export (#465). Those threads should remain the place for their individual design decisions. The agreed /agents work stays separate.

Proposed Solution

One additional candidate is the animated welcome mascot from fork PR #30. It animates the existing ASCII crab:

  • While connecting, four poses change the eyes and legs every 180 ms.
  • After the first successful connection, a 1.2-second wave/blink sequence returns to the original resting pose.
  • Animation is limited to the visible welcome screen. Reduced-motion preferences, narrow terminals, and later connections keep it still.
  • Redraws stop when the animation is no longer visible or has finished.

Implementation reference: welcome renderer and timing, event-loop redraw handling. The fork includes pinned-clock animation tests; any upstream port would need fresh verification against upstream, including reduced motion, narrow layouts, connection transitions, and the final resting frame.

I understand #440 / #441 rejected replacing the crab with Claude Code's mascot because of the branding concern. This candidate keeps the existing crab artwork; it does not reuse the rejected Anthropic mascot glyphs.

Would you consider this animation as a later, separate contribution? Of the existing fork-related proposals above, which would you prefer next after /agents? I will wait for explicit agreement on one scope before preparing another upstream PR.

Alternatives Considered

Keep the welcome crab static and leave the animation fork-only. Contribute only the features already being discussed in their existing issues. Either is fine; this issue is to establish your preference before additional upstream work.

Checklist

  • I have searched existing issues and discussions to ensure this is not a duplicate. The related closed mascot proposal is acknowledged above; this proposal concerns animation of the existing crab and contribution scope.
Dominant language
Rust
Stars
261
Forks
57
Avg merge
9h 37m
Merged PRs (30d)
62

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from srothgan/claude-code-rust

All issues in srothgan/claude-code-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.