Nimbus is a personal task management chatbot that helps you keep track of your todos, deadlines, and events via a simple command-line interface.
Nimbus.jar from the releases page.cd into the folder, and run:
java -jar Nimbus.jar
Notes about the command format:
- Words in
UPPER_CASEare parameters to be supplied by you.- Parameters must be provided in the order shown.
- Extraneous parameters for commands that do not take in parameters (e.g.
list,bye) will result in an error.
todoAdds a todo task (a task with no date attached).
Format: todo DESCRIPTION
Example:
todo read book
Expected output:
Got it. I've added this task:
[T][ ] read book
Now you have 1 tasks in the list.
deadlineAdds a task with a due date.
Format: deadline DESCRIPTION /by DATE
DATE can be in ISO-8601 format (e.g. 2025-12-31) for formatted display, or free-form text (e.g. Sunday).Example:
deadline return book /by 2025-06-15
Expected output:
Got it. I've added this task:
[D][ ] return book (by: Jun 15 2025)
Now you have 2 tasks in the list.
eventAdds a task with a start and end date/time.
Format: event DESCRIPTION /from START /to END
START and END can be in ISO-8601 format or free-form text.Example:
event project meeting /from 2025-08-06 /to 2025-08-07
Expected output:
Got it. I've added this task:
[E][ ] project meeting (from: Aug 6 2025 to: Aug 7 2025)
Now you have 3 tasks in the list.
listDisplays all tasks in your task list.
Format: list
Example output:
Here are the tasks in your list:
1.[T][ ] read book
2.[D][ ] return book (by: Jun 15 2025)
3.[E][ ] project meeting (from: Aug 6 2025 to: Aug 7 2025)
markMarks the specified task as done.
Format: mark INDEX
INDEX is the task number shown in the list output.Example:
mark 1
Expected output:
Nice! I've marked this task as done:
[T][X] read book
unmarkMarks the specified task as not done.
Format: unmark INDEX
Example:
unmark 1
Expected output:
OK, I've marked this task as not done yet:
[T][ ] read book
deleteRemoves the specified task from the list.
Format: delete INDEX
Example:
delete 3
Expected output:
Noted. I've removed this task:
[E][ ] project meeting (from: Aug 6 2025 to: Aug 7 2025)
Now you have 2 tasks in the list.
findFinds all tasks whose descriptions contain the given keyword.
Format: find KEYWORD
Example:
find book
Expected output:
Here are the matching tasks in your list:
1.[T][ ] read book
2.[D][ ] return book (by: Jun 15 2025)
byeExits the application.
Format: bye
Task data is saved automatically to ./data/nimbus.txt after every command that modifies the task list. There is no need to save manually.
Task data is saved as a text file at ./data/nimbus.txt. Advanced users are welcome to update data directly by editing that file.
⚠️ Caution: If your changes to the data file are not in the correct format, Nimbus may not be able to load the file and will start with an empty task list.
Q: How do I transfer my data to another computer?
A: Copy the data/nimbus.txt file from your current Nimbus home folder to the same location on the other computer.
Q: Can I use dates in formats other than ISO-8601?
A: Yes. If a date string is not in yyyy-MM-dd format, Nimbus stores and displays it as-is (e.g. Sunday, next week).
| Action | Format |
|---|---|
| Todo | todo DESCRIPTION |
| Deadline | deadline DESCRIPTION /by DATE |
| Event | event DESCRIPTION /from START /to END |
| List | list |
| Mark | mark INDEX |
| Unmark | unmark INDEX |
| Delete | delete INDEX |
| Find | find KEYWORD |
| Exit | bye |