Global alias

Open
#3,745 1 comment 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
shell
Domain
cli, networking

Research direction

The issue names no files, tests, or entry points. Start by locating Warp's existing alias handling and SSH connection behavior, then clarify how aliases should be configured, expanded locally, and applied to remote shells. Done should include a defined configuration format and documented behavior for local and SSH commands.

Written by the indexing model from the issue text.

Description

enhancement triaged
Discord username (optional)

clansty

Describe the solution you'd like?
In a special file I can set some alias and environments, these alias will apply anywhere, with any ssh connection. 

eg. ip=ip --color=auto

These alias may not expose to remote shell and expend when executing, or run as a script upon connecting to a ssh remote
Is your feature request related to a problem? Please describe.

No response

Additional context

No response

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

Ignore

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

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 warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.