Your engineer at home, available from your pocket

Extend the remote-agent phone app and agent-readable notes into a complete way to direct work and use its results while away from the computer. Build it extremely well. The person should be able to capture an idea, discuss it, let their agent build, and try what it made from their phone. Follow the shared launch.

Start with their actual agent installation, account, projects, and connected applications. Preserve existing conversations and working records. Complete any missing foundation needed for this experience, with the computer continuing to own the project work.

Turn an idea into a working conversation

Let the person bring a note, photograph, or recording into the relevant project conversation. Retain the original material and make clear what has reached the computer. The agent should receive enough context to understand why the person captured it.

Keep collecting an idea and commissioning work distinct. Give the person an easy way to say what they want done, discuss the direction, and begin when the intent is settled. A note can remain a thought for later.

Use the existing agent's project guidance, skills, and normal capabilities. Let it ask a meaningful question when needed, make ordinary engineering decisions itself, and report changes in the same conversation. Support voice input if useful for the person's situation, with a clear chance to correct an important misunderstanding.

Let work continue when the phone is put away

The computer should keep doing authorized work after the phone locks or loses connection. Show the actual state when the person returns: still working, waiting for their answer, finished, interrupted, or currently unreachable.

Make direction and interruption effective from the phone. A message awaiting delivery and a message the agent has received should be distinguishable. Keep completed work and the conversation available after reconnecting.

For work spanning several sessions, use a real supported continuation mechanism and the shared launch's autonomy-loop guidance. Give the person a useful way to inspect the current responsibility, change it, or stop it.

Bring the result back to the person

Notify them when there is something worth returning to: a completed result, a consequential question, or a problem requiring their attention. Opening the notification should return to the relevant project and work.

Provide the result in a form the phone can use. A document can open directly. A web application can offer a reachable preview. For an application built for their phone, provide its installable artifact and a convenient route through the device's normal installation process. Explain any platform-specific setup as part of delivering that capability.

Associate each result with the work and version that produced it. Let the person inspect it, try it, describe an improvement, and continue the same job. Preserve the version they already rely on when a new candidate is still being prepared.

Make the private system understandable

Use Tailscale for the person's chosen devices, or retain a suitable existing private connection. Explain which machine runs the agent, where project files live, and what needs to remain available for remote work and previews. Establish the connection and normal startup or recovery controls as part of the build.

Complete a useful project change from outside the computer's local network. Start with a captured idea, leave the phone, return through a notification, inspect the delivered result, and ask for a refinement. Use the shared launch's ownership guidance for source, conversations, and built artifacts.

Teach the person that their location need not determine where the work happens. They can make decisions from the phone while their existing engineer and computer do the building.