Fix prompt for env on devmode, remove old server flag now that it comes from API

[jhaynie]

Summary by CodeRabbit

• Refactor
  • Simplified command-line interface by removing the "server" and "force" flags.
  • Streamlined connection logic by eliminating server address fallback and related options.
• Documentation
  • Updated Discord community invite links across the CLI, TUI, README, and error system.
• User Interaction
  • Improved prompt clarity by separating informational messages from interactive questions.

[coderabbitai]

Walkthrough

The changes remove the "server" and "force" command-line flags and all related logic from the development command and server connection handling. This includes deleting flag definitions, environment file processing, and server address customization logic, as well as removing associated fields and logic from the server implementation. Additionally, multiple Discord community invite links were updated across documentation, CLI descriptions, TUI help, and error system constants. The user prompt in environment handling was adjusted to separate informational messages from interactive questions, and the dependency github.com/agentuity/go-common was updated.

Changes

Files / Areas	Change Summary
cmd/dev.go	Removed "server" and "force" flag definitions and all related logic, including environment file processing.
internal/dev/server.go	Removed serverAddr from Server and ServerArgs structs; deleted all logic referencing these fields.
README.md, cmd/root.go, internal/dev/tui.go, internal/errsystem/console.go	Updated Discord invite link from https://discord.gg/vtn3hgUfuc to https://discord.gg/agentuity.
internal/envutil/envutil.go	Modified prompt in HandleMissingProjectEnvs to print title separately before asking the question.
go.mod	Updated dependency github.com/agentuity/go-common from version v1.0.60 to v1.0.64.

Possibly related PRs

• [AGENT-209] Refactor adding env vars from file #324: Introduced the "force" flag and refactored environment file processing, directly related to the removal of the "force" flag and environment processing logic in this PR.

Poem

A hop and a skip, two flags are gone,
No more "server" to dwell upon.
"Force" is retired, the code is clean,
Simpler paths, no in-between.
The bunny cheers with floppy ears—
Streamlined code brings joyful years! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2f95288 and b291e73.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (7)

• README.md (1 hunks)
• cmd/dev.go (1 hunks)
• cmd/root.go (1 hunks)
• go.mod (1 hunks)
• internal/dev/tui.go (1 hunks)
• internal/envutil/envutil.go (1 hunks)
• internal/errsystem/console.go (1 hunks)

✅ Files skipped from review due to trivial changes (5)

• internal/dev/tui.go
• internal/errsystem/console.go
• README.md
• go.mod
• cmd/root.go

🚧 Files skipped from review as they are similar to previous changes (1)

• cmd/dev.go

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Test CLI Upgrade Path (windows-latest)

🔇 Additional comments (1)

internal/envutil/envutil.go (1)

179-180: Improved prompt clarity by separating information from the question.

This change enhances the user experience by first displaying the informational message about missing environment variables, then presenting the action question separately. This separation makes the UI more intuitive and easier to follow.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.