> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/borrow/reminders.md).

# Your deadline

Walking away by neglect is the product's biggest risk. gage sends no reminders; your calendar can hold the date, and the deadline is yours to keep.

Weekly expiries are easy to forget, and gage sends no reminders: no Telegram message, no email and no web push. Put the date in your own calendar.

## Add a loan to your calendar

On **Portfolio**, each loan you borrow has **Add to calendar** on the **Agenda**. It takes no signature and no transaction.

* **Google Calendar** and **Outlook** open a prefilled event for that loan in a new tab. The event stays as you saved it.
* **Apple Calendar** subscribes to your wallet's feed: every loan you borrow, kept up to date, and a loan that closes drops out. The **Calendar** row at the foot of the **Loans** tab offers the same feed.

The link you pick gives that calendar the loan's end, its amounts and its page, and a feed gives it your public wallet address.

## What a calendar cannot do

A calendar depends on your device and your calendar app, and a feed on how often that app refreshes it and on gage's site being up. The clock on your position page is the only one that counts: check it yourself, and repay early rather than at the deadline.

{% hint style="danger" %}
If you miss the deadline, the lenders keep your collateral. On the current engine, repayment closes the second the term ends.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gage.cash/borrow/reminders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
