Skip to content

fix: return the terminal after init and clarify me output - #4

Merged
alibek-seksenali merged 1 commit into
mainfrom
fix/init-exit-and-me-output
Sep 14, 2026
Merged

alibek-seksenali merged 1 commit into
mainfrom
fix/init-exit-and-me-output

Conversation

@alibek-seksenali

Copy link
Copy Markdown
Contributor

Summary

  • 1msg init now restores the TTY and process.exits, so an error or a successful verify no longer leaves the shell hanging (1MSG-166 review).
  • 1msg me prints a labeled WhatsApp Business profile; empty/{error} bodies are explained instead of a raw blob.
  • Non-interactive init --base-url/--instance-id is read from Commander globals. Bump to 0.1.4.

Test plan

  • npx jest (103 passing)
  • After merge: GitHub release v0.1.4 and npm publish @1msg/cli@0.1.4 (via 1msg-api Publish @1msg/cli, dry_run=false)
  • npx -y @1msg/cli@0.1.4 init returns the console; npx -y @1msg/cli@0.1.4 me is labeled kv

Made with Cursor

Init left stdin/raw-mode open so the process never exited; me dumped a raw GET /me body. Exit after every command, print a labeled profile, and read init --base-url/--instance-id from globals. Bump to 0.1.4.

Co-authored-by: Cursor <cursoragent@cursor.com>
@alibek-seksenali
alibek-seksenali merged commit e5c0a85 into main Sep 14, 2026
1 check passed
@alibek-seksenali
alibek-seksenali deleted the fix/init-exit-and-me-output branch September 14, 2026 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant