Daily handoff for solo developers

Your chat assistant plans the day. Your coding agent starts already briefed.

For freelance and indie developers. Relaypad keeps one daily record of your plan, open questions, ruled-out approaches and calendar limits, so your terminal coding agent reads it before it starts and leaves a short end-of-session note your chat assistant uses tomorrow morning.

Plan today's work on the invoice export bug and save the brief for my coding agent →How it works

Start with the agent you already use.

RelaypadExample

> Plan today's work on the invoice export bug and save the brief for my coding agent

Today's brief: invoice export bug (illustrative example)

Goal: CSV export drops rows with accented client names
Deadline: Fix ready for client review by 17:00
Calendar limit: Client call 15:00 to 15:30
Focus time before the call: 09:30 to 12:00 and 12:30 to 15:00 = 5 hours
Ruled out: Switching the CSV library (tried yesterday, breaks date columns)
Open question: Does the client's import tool expect UTF-8 with BOM?
For the coding agent: Start with the encoding step in export_writer, add a test with the name Zoë

Illustrative example only. This brief is a draft and has not been saved. Say save to store it in your Fulcra account for your coding agent.

Starts with what you pasteA useful first answer before anything is connected.

Works with your agentBring the prompts to the assistant you already use.

You decide what is sharedNothing is saved or shared without your say.

How it works

Three steps, and you approve the result.

Lets a solo developer's coding agent and chat assistant pick up where the other left off, using one shared record of the day.

Plan the task with your chat assistant
In the morning, talk through the task as you normally would. Your assistant writes a short brief: the goal, the deadline, open questions, approaches you already ruled out, and the calendar limits for the day. You review it before anything is saved to your own Fulcra account.
Your coding agent reads the brief first
Before it touches code, your terminal coding agent reads the saved brief through the Fulcra CLI or MCP server. It knows the client call is at three and that the caching approach was dropped yesterday, so it does not spend an hour rediscovering that.
End the session with a handoff note
When you stop, the coding agent records a short note: what changed, what is stuck, and what it would try next. The next morning your chat assistant reads that note and suggests the first job of the day. You can edit or delete any note.

Try it now

Bring these to your agent.

Copy a prompt, add your details, and review what comes back.

Prompt 01

First pass from pasted notes

Here are my notes for today, pasted below: the task, the deadline, my meetings, and what I already tried. Turn them into a short brief for my coding agent with these headings: goal, deadline, calendar limits, ruled out, open questions, first step. Work out my focus hours before and after each meeting and show the sum. Do not save or send anything. Notes: [paste here]

Prompt 02

Optional: connect Relaypad handoffs to my Fulcra account

Read https://docs.fulcradynamics.com/agent-get-started.txt and explain in plain words what connecting to Fulcra would let you do for my daily handoff. Ask for my explicit permission before you connect, before you read any data such as my calendar events, before you save a brief or session note, and before you share anything. Only read the data I name. Do not read client folders, health data or personal notes unless I grant that.

Prompt 03

Draft an invitation to a collaborator I can review

Draft a short message I can review and send myself to a fellow developer who wants the same morning brief and end-of-session note setup. Include this starter prompt for their own agent: "Read https://docs.fulcradynamics.com/agent-get-started.txt, explain what Fulcra would do for my daily coding handoff, and ask my permission before connecting, reading, saving or sharing anything." Explain that their notes stay in their own account, and that if they later join a group I create, I as owner can read only the data types and time range they agree to, with no access for them to my data unless I share separately. Do not include any group link and do not send the message.

When you want continuity

Keep the part worth remembering.

Your first plan can start with details you provide. For next time, the connected prompt helps your agent keep the context you choose in your own Fulcra account.

Before sharing, review the exact information and who can read it. Other people make their own choices. A shared plan becomes an agreement when the people involved confirm it.

Questions

Before you start.

How does my coding agent read what my chat assistant planned?

Both agents connect to your own Fulcra account, through the Fulcra CLI or the Fulcra MCP server. The chat assistant saves the brief as a record or file, and the coding agent reads it before starting. You approve the connection and each save.

Will it read my calendar or my other files?

Only what you grant. With permission, an agent can read Apple calendar events through Fulcra to find your meetings. It does not write to your calendar. Client folders, health data and personal notes stay unread unless you choose to allow them.

Can a client or teammate see my handoff notes?

Not unless you share them. Fulcra lets you share selected data, and groups let an owner read the data types and time range each member agrees to. Members share read-only with the owner, not with each other, and can leave any time.