Daily workflow

You use Recallium by talking to your coding agent in plain language. These five workflows cover most daily use.

​

Start a session with context

At the beginning of a session, ask:

Load Recallium for this project. Summarize the recent work, active effort, open follow-ups, and rules I should know.

Your agent should orient itself before it edits the repository. If you are returning to a specific effort, name it:

Resume the checkout reliability workstream and tell me the next useful step.

​

Save a decision or implementation

When a meaningful unit of work lands, describe what future sessions need to know:

Remember this JWT implementation. Access tokens expire after 15 minutes, refresh tokens rotate, and we use HTTP-only cookies. Include the security trade-off and the files we changed.

For a decision, include the rejected alternatives:

Save why we chose Postgres over DynamoDB for the ledger. Include the consistency requirement and the scaling trade-off.

The agent chooses the appropriate record shape and connects it to the current project and effort.

​

Recall a past decision

Ask the question you want the earlier work to answer:

What did we decide about the database for user preferences, and why?

Why does refresh-token rotation work this way?

Your agent should search the stored project history, open the strongest matches, and answer from their reasoning.

​

Check context before editing

Before changing established code, ask about the file:

I am about to edit src/auth/jwt.ts. What decisions, fixes, and warnings should I know first?

This can surface security constraints, earlier incidents, and behavior that is easy to miss by reading the current implementation alone.

​

Search the full body of work

Use a broad request when you need the history of a feature rather than one decision:

Show me what we have done on authentication. Group the implementations, decisions, bug fixes, and remaining follow-ups.

Add a project or directory when the scope is ambiguous.

​

Resume after a break

When you return later, ask:

Where did we leave off?

A useful recap includes what changed, what was verified, what remains open, and the next concrete action.

​

End a session cleanly

Before stopping unfinished work, ask:

Save a continuation point for the next session. Include what is complete, what remains, and the next action.

If a decision or root cause landed during the session, save that durable context separately rather than burying it inside the continuation note.