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

Teams page: offer both "New team" and "+ New team in <team>" when a team is selected

Open Beginner friendly
  • Is something wrong?
#1,510 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Start in internal/tui3/teamspagedraw.go by reading teamsRailNew and teamsRailNewWords, then trace teamsActNewTeam in internal/tui3/teamsacts.go. Wire the selected-team row to nil id for a top-level team while retaining the t.ID nested option. Done means both rows appear in the narrow rail and nesting-limit dim/hint behavior remains unchanged.

Written by the indexing model from the issue text.

Description

area:chat feature

Today the teams rail shows only + New team in <name> when a team is selected — the top-level + New team is only visible with no team selected. A selected team should offer both options: top-level + New team and nested + New team in <current team>.

Details
  • internal/tui3/teamspagedraw.go: teamsRailNew / teamsRailNewWords currently draw only the nested variant when a team is selected; add the top-level option alongside it.
  • internal/tui3/teamsacts.go: teamsActNewTeam with no id already creates a top-level team — wire the new row to it (nil id vs t.ID).
  • Maintain the narrow-rail two-row presentation and nesting-limit dim/hint behavior for the nested option.

Drafted with CodeAF · reviewed and owned by the author

Dominant language
Go
Stars
115
Forks
14
Avg merge
9h 35m
Merged PRs (30d)
752

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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 Agent-Field/CodeAF

All issues in Agent-Field/CodeAF

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.