Skip to content
Film and focused work

AI coding agent tasks and handovers: save ideas and continue in a fresh session

Save ideas, bugs and technical debt as tasks in Giljo HQ. Use agent handovers to summarize long AI coding sessions and continue without another Markdown file.

An AI coding session can produce more than the feature you asked for. You spot an improvement. The agent finds a bug or technical debt. After hours of work, the conversation is long enough that you want to start a fresh session without explaining everything again.

Tasks and handovers in Giljo HQ help with both situations. Tasks keep work you may want to return to. Handovers summarize the work already done so another session can continue. The accompanying animated film introduces these two uses.

Use tasks to save ideas without interrupting your coding agent

Suppose your agent is adding trail search to a hiking app, and you think of a better way to organize saved routes. You don't need to choose between starting that feature now and hoping you remember it later. Ask the agent to add the idea to the task list, then continue with search.

The same applies to bugs, small to-dos and technical debt. A useful task says what needs attention and includes enough background to understand it later. It doesn't need a full project plan.

Agents can also create tasks themselves when they find work to defer. For example, an agent might finish a fix and record a separate cleanup it noticed along the way. You can review those tasks later or ask an agent to help decide which ones are worth doing next.

Saving a task does not authorize the agent to start it. And if a problem prevents the current feature from working, the agent should explain that rather than quietly postponing it.

Use a handover when an AI coding session gets too long

After a long session, the agent may have investigated several approaches, changed files, run tests and made decisions with you. Starting a new chat can mean losing that background. Asking for a summary in another Markdown file also leaves you with another document to manage.

In Giljo HQ, ask the agent to create a session handover using the task tool. It saves a handover record that the next connected session can retrieve, without requiring a separate Markdown file.

The tool's handover requirements guide the agent to record the state of the work, including what the next session must verify, what is waiting for your decision and what the outgoing agent could not confirm. That gives the next agent more useful instructions than a general recap of the conversation.

You can then start a fresh session and point it to the handover. The new agent should read it and check the current files and results before continuing. The handover preserves context; it does not start the next agent or replace those checks.

A task is work to consider. A handover is context to continue.

Use a task when you want to say, "Keep this for later." Use a handover when you want to say, "Here is where we stopped, and what you need to know to continue."

Both keep useful information out of a single chat history. You decide which saved tasks become work, while the handover helps your next coding session pick up an existing piece of work.