CLInkedin is a desktop app for managing contacts, optimized for use via a Command Line Interface (CLI) while still having the benefits of a Graphical User Interface (GUI). If you can type fast, CLInkedin can get your contact management tasks done faster than traditional GUI apps.
Ensure you have Java 17 or above installed in your Computer.
Mac users: Ensure you have the precise JDK version prescribed here.
Download the latest .jar file from here.
Copy the file to the folder you want to use as the home folder for your CLInkedin.
Open a command terminal, cd into the folder you put the jar file in, and use the java -jar clinkedin.jar command to run the application.
A GUI similar to the below should appear in a few seconds. Note how the app contains some sample data.

Type the command in the command box and press Enter to execute it. e.g. typing help and pressing Enter will open the help window.
Some example commands you can try:
list : Lists all contacts.
add n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01 : Adds a contact named John Doe to CLInkedin.
delete 3 : Deletes the 3rd contact shown in the current list.
clear : Deletes all contacts.
exit : Exits the app.
Refer to the Features below for details of each command.
Notes about the command format:
Words in UPPER_CASE are the parameters to be supplied by the user.
e.g. in add n/NAME, NAME is a parameter which can be used as add n/John Doe.
Items in square brackets are optional.
e.g n/NAME [t/TAG] can be used as n/John Doe t/friend or as n/John Doe.
Items with … after them can be used multiple times including zero times.
e.g. [t/TAG]… can be used as (i.e. 0 times), t/friend, t/friend t/family etc.
Parameters can be in any order.
e.g. if the command specifies n/NAME p/PHONE_NUMBER, p/PHONE_NUMBER n/NAME is also acceptable.
Extraneous parameters for commands that do not take in parameters (such as help, list, exit, sortcom and clear) will be ignored.
e.g. if the command specifies help 123, it will be interpreted as help.
If you are using a PDF version of this document, be careful when copying and pasting commands that span multiple lines as space characters surrounding line-breaks may be omitted when copied over to the application.
helpShows a message explaining how to access the help page.
Format: help
addAdds a contact to CLInkedin.
Format: add n/NAME p/PHONE_NUMBER e/EMAIL a/ADDRESS [c/COMPANY] [l/LINK] [r/REMARK] [t/TAG]…
Input constraints:
') and hyphens (-). , & -/ or @/Tip: A contact can have any number of tags (including 0)
Examples:
add n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01add n/Betsy Crowe t/friend e/betsycrowe@example.com a/Pasir Ris Drive c/Google r/Follow up next week p/1234567 t/teacherlistShows a list of all contacts in CLInkedin.
Format: list
editEdits an existing contact in CLInkedin.
Format: edit INDEX [n/NAME] [p/PHONE] [e/EMAIL] [a/ADDRESS] [c/COMPANY] [l/LINK] [r/REMARK] [t/TAG]…
Each field must still follow its respective input constraints (refers to input constraints in Add command section above for details).
INDEX. The index refers to the index number shown in the displayed contact list. The index must be a positive integer 1, 2, 3, …t/ without specifying any tags after it.c/ or r/ without specifying any value.Examples:
edit 1 p/91234567 e/johndoe@example.com:Edits the phone number and email address of the 1st contact to be 91234567 and johndoe@example.com respectively.edit 2 n/Betsy Crower t/ Edits the name of the 2nd contact to be Betsy Crower and clears all existing tags.edit 3 c/ r/ Clears both the company and remark fields of the 3rd contact.findFinds contacts whose names contain any of the given keywords.
Format: find KEYWORD [;MORE_KEYWORDS]
hans will match HansHans Bo will not match Bo HansHan will match Hans.contains() search).
e.g. Hans Bo will return Hans Bobber, but not Hans LimExamples:
find John returns john and John Doefind alex david returns Alex David onlyfind alex; yu returns Alex Yeoh and Bernice YufindcomFinds all contacts whose company name matches any of the given keywords.
Format:
findcom KEYWORD [; KEYWORD]…
google, Google, GOOGLE are treated the same.;.Examples:
findcom Google
Returns all contacts whose company contains “Google”.
findcom Google; Amazon
Returns all contacts whose company contains either “Google” or “Amazon”.
findcom fintech; bank
Returns all contacts whose company contains either “fintech” or “bank”.
sortcomSorts the currently displayed contact list alphabetically by company name.
Format:
sortcom
apple, Apple, APPLE are treated the same.findcom or tag show).Examples:
sortcom
Sorts all currently displayed contacts by company name in alphabetical order.
findcom Google sortcom
First filters contacts by company “Google”, then sorts the filtered results alphabetically.
deleteDeletes the specified contact from CLInkedin.
Format: delete INDEX
INDEX.deleted command.Examples:
list followed by delete 2 deletes the 2nd contact in CLInkedin.find Betsy followed by delete 1 deletes the 1st contact in the results of the find command.deletedShows a list of recently deleted contacts.
Format: deleted
Examples:
deletedrestoreRestores a contact from the deleted list.
Format: restore INDEX
INDEX from the deleted contacts list.deleted list.Examples:
deleted followed by restore 1tag createCreates a new tag with an optional color.
Format: tag create TAG_NAME [COLOR]
TAG_NAME.friend and Friend are treated as different tags).COLOR is not provided, a default color will be assigned.Tip: Valid color formats include case-insensitive plain names, or hexadecimal values.
Examples: orange, #ff6688
Examples:
tag create friendtag create colleague bluetag create vip #ff6688tag assign, tag unassignAssign/remove a tag to/from 1 or multiple contacts at once.
Format: tag assign INDEX[,INDEX]... TAG_NAME, tag unassign INDEX[,INDEX]... TAG_NAME
TAG_NAME tag to/from multiple contacts.Examples:
tag assign 1 friendtag assign 1,4,6 friendtag unassign 1 friendtag unassign 1,4,6 friendtag deleteDeletes a tag and removes it from all contacts.
Format: tag delete TAG_NAME
TAG_NAME.Examples:
tag delete friendtag listShows a list of all tags in CLInkedin.
Format: tag list
tag renameRenames an existing tag and updates all respective contacts with it.
Format: tag rename OLD_TAG_NAME NEW_TAG_NAME
OLD_TAG_NAME to the NEW_TAG_NAME.OLD_TAG_NAME does not exist, an error message will be shown.Examples:
tag rename friends closefriendstag rename colleagues coworkerstag colorAdds a color to a tag.
Format: tag color TAG_NAME COLOR
TAG_NAME.Examples:
tag color friends bluetag color coworker #343434tag showShow contacts that have a specific tag.
Format: tag show TAG_NAME
TAG_NAME.Examples:
tag show friendstag show coworkersclearClears all entries from CLInkedin.
Format: clear
exitExits the program.
Format: exit
CLInkedin data are saved in the hard disk automatically after any command that changes the data. There is no need to save manually.
CLInkedin data are saved automatically as a JSON file [JAR file location]/data/addressbook.json. Advanced users are welcome to update data directly by editing that data file.
Caution:
If your changes to the data file makes its format invalid, CLInkedin will discard all data and start with an empty data file at the next run. Hence, it is recommended to take a backup of the file before editing it.
Furthermore, certain edits can cause CLInkedin to behave in unexpected ways (e.g., if a value entered is outside the acceptable range). Therefore, edit the data file only if you are confident that you can update it correctly.
Q: How do I transfer my data to another Computer?
A: Install the app in the other computer and overwrite the empty data file it creates with the file that contains the data of your previous CLInkedin home folder.
Q: Why does sortcom not sort all contacts after using tag show?
A: sortcom sorts only the currently displayed contact list. After tag show, the list is filtered, so only that subset is sorted. Use list first to sort all contacts.
preferences.json file created by the application before running the application again.help command (or use the Help menu, or the keyboard shortcut F1) again, the original Help Window will remain minimized, and no new Help Window will appear. The remedy is to manually restore the minimized Help Window.| Action | Format, Examples |
|---|---|
| Add | add n/NAME p/PHONE_NUMBER e/EMAIL a/ADDRESS [c/COMPANY] [l/LINK] [r/REMARK] [t/TAG]… e.g., add n/James Ho p/22224444 e/jamesho@example.com a/123 Clementi Rd t/friend t/colleague |
| Clear | clear |
| Delete | delete INDEXe.g., delete 3 |
| Edit | edit INDEX [n/NAME] [p/PHONE_NUMBER] [e/EMAIL] [a/ADDRESS] [c/COMPANY] [l/LINK] [r/REMARK] [t/TAG]…e.g., edit 2 n/James Lee e/jameslee@example.com |
| Find | find KEYWORD [MORE_KEYWORDS]e.g., find James Jake |
| Find Company | findcom COMPANY [; MORE_COMPANY]e.g., find Google; Amazon |
| Sort Company | sortcom |
| List | list |
| Deleted | deleted |
| Restore | restore INDEXe.g., restore 1 |
| Delete Tag | tag delete TAG_NAMEe.g., tag delete friend |
| Tag Create | tag create TAG_NAME [COLOR]e.g., tag create friend blue |
| Tag Assign | tag assign INDEX[,INDEX]... TAG_NAMEe.g., tag assign 1,4,6 friend |
| Tag Unassign | tag unassign INDEX[,INDEX]... TAG_NAMEe.g., tag unassign 1,4,6 friend |
| Tag List | tag list |
| Tag Rename | tag rename OLD_TAG_NAME NEW_TAG_NAMEe.g., tag rename friends closefriends |
| Tag Color | tag color TAG_NAME COLORe.g., tag color friends red |
| Tag Delete | tag delete TAG_NAMEe.g., tag delete friend |
| Help | help |
| Prefix | Field | Description | Example |
|---|---|---|---|
n/ | Name | Contact’s full name | n/John Doe |
p/ | Phone | Phone number | p/98765432 |
e/ | Email address | e/john@example.com | |
a/ | Address | Address or context | a/NUS Computing |
c/ (optional) | Company | Company name | c/Google |
l/ (optional) | Link | URL (e.g., LinkedIn) | l/https://linkedin.com/in/john |
r/ (optional) | Remark | Additional notes | r/Met at career fair |
t/ (optional) | Tag | Tag(s) for categorisation | t/friend |
Prefix usage constraints:
Prefixes must be used without spaces between the prefix and /.
Valid:
c/Google r/Met at event
Invalid:
c / Google
r / Met at event
If a prefix is written incorrectly (e.g., with spaces), it may be interpreted as part of another field and lead to unexpected errors.
Fields marked as (optional) (c/, l/, r/, t/) can be omitted when adding or editing a contact.
Each field must still follow its respective input constraints (refers to input constraints in Add command section above for details).
Tip: Each prefix applies only to the value immediately following it. Ensure correct formatting to avoid parsing errors.