{
  "edition": {
    "edition": "2026-09-06-draft-01",
    "language": "en",
    "publicationState": "published",
    "sourceRevision": "a7e788eb4b151fd92c1f58153e015773e3a829af",
    "projectCount": 67,
    "documentCount": 94,
    "skillCount": 10,
    "archivePath": "library.zip",
    "archiveBytes": 181812,
    "releasedAt": "2026-09-08T05:03:11.129+00:00"
  },
  "access": {
    "released": true,
    "rehearsal": false
  },
  "project": "connected-systems/engineer-in-your-pocket.md",
  "markdown": "https://legion.tw/api/projects/packet.md/connected-systems/engineer-in-your-pocket.md?edition=2026-09-06-draft-01",
  "documents": [
    {
      "path": "connected-systems/README.md",
      "text": "# Connected systems\n\n[All project types](../README.md) · [Shared launch](../shared/launch.md)\n\nExtend useful applications into a connected workflow, preserving their records and letting each device serve its actual role.\n\n## Projects to build\n\n- [From a site visit to a finished report](site-visit-to-report.md)\n- [Your engineer at home, available from your pocket](engineer-in-your-pocket.md)\n- [A research system that keeps up with your thinking](connected-research.md)\n- [A game night across different screens](multi-screen-game-night.md)\n- [Capture outside and process on the computer](capture-to-processing.md)\n- [A shared lending service with private working tools](lending-service.md)\n\nThese are instructions for projects you can build with your coding agent.\n"
    },
    {
      "path": "connected-systems/engineer-in-your-pocket.md",
      "text": "# Your engineer at home, available from your pocket\n\nExtend the [remote-agent phone app](../native-phone/coding-agent-in-your-pocket.md) and [agent-readable notes](../native-phone/agent-readable-notes.md) 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](../shared/launch.md).\n\nStart 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.\n\n## Turn an idea into a working conversation\n\nLet 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.\n\nKeep 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.\n\nUse 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.\n\n## Let work continue when the phone is put away\n\nThe 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.\n\nMake 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.\n\nFor 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.\n\n## Bring the result back to the person\n\nNotify 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.\n\nProvide 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.\n\nAssociate 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.\n\n## Make the private system understandable\n\nUse 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.\n\nComplete 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.\n\nTeach 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.\n"
    },
    {
      "path": "native-phone/coding-agent-in-your-pocket.md",
      "text": "# Talk to your coding agent from your phone\n\nBuild a native phone app through which the person can continue working with you on their computer while they are away. Build it extremely well, with a dependable conversation and useful control over real work happening in their projects.\n\nRead this brief and follow the [shared launch](../shared/launch.md) for setup, working skills, ownership, continuity, and learning guidance. Discover the build and installation route for their actual phone and carry it through to an installed application.\n\n## The experience\n\nThe person has a computer where their coding agent can work on applications. From their phone, they choose a project, open or start a conversation, and ask for something. The agent can inspect the project and carry out the work using its normal capabilities. They can read its response, discuss a decision, answer a question, and interrupt the work when their direction changes.\n\nImagine they notice an awkward screen in an app while out. They ask the agent to improve it, explain what bothered them, and then put the phone away. The computer continues working. When they return, they can see what happened and continue the same conversation.\n\nConnect the phone app to the coding-agent environment the person already uses, with its existing account and model access. Carry the conversations, working context, and actions between the phone and that environment. The person should recognize the project and agent they work with at their desk.\n\nRemote work should use the same project instructions, installed skills, and working knowledge. Use the installed agent's supported integration capabilities so the phone participates in real agent sessions and can accurately show what happened.\n\n## Stay oriented while away\n\nMake it clear which project and conversation are open. Keep messages readable on the phone, with useful progress and results easy to follow. The person needs to understand whether the agent is working, waiting for an answer, finished, or currently unreachable.\n\nGive their own actions equally clear outcomes: they can see whether a message has reached the computer and whether an interruption took effect. A lost phone connection and stopped agent work are different events; the experience should make that distinction understandable.\n\nThe conversation survives switching applications, locking the phone, and reconnecting later. When the person returns, show the current conversation and the work completed during their absence. Keep the underlying project and its work available from the computer as well.\n\n## Connect their own devices\n\nUse a private connection suited to the person's devices. Tailscale is a natural fit for reaching their computer while away. Establish the connection as part of making the application useful, with access belonging to the person and the devices they choose.\n\nExplain what needs to stay running on the computer for the agent to be available. Help the person understand any account, model-usage, or service costs involved in their chosen setup. Select the installation and connection approach from their actual environment; own those engineering decisions.\n\n## Build a foundation they can keep using\n\nThe complete experience here is remote conversation, real project work, direction, interruption, and returning to what happened. Give those capabilities sustained attention through focused steps, then put them together in an installed app the person can use from their phone.\n\nExercise the remote working experience, including leaving and returning to a conversation. Help the person try a useful change to one of their projects and understand where the result lives. Keep the interface centered on the work they are directing.\n\nInclude a connection from outside the computer's local network in that experience. Help the person understand the roles of their devices: the phone carries their conversation and control, while the computer runs the agent and does the project work. They should know how to restore the connection and continue when a device has been unavailable.\n\nLater, they may want voice conversations, photographs, completion notifications, previews, or a convenient way to install something the agent built. Notes captured during the day can become material for a conversation. Choose a foundation that allows those additions while preserving the conversations and projects they already rely on.\n"
    },
    {
      "path": "native-phone/agent-readable-notes.md",
      "text": "# Send your notes into your agent's workspace\n\nBuild a native Android notes application that synchronizes with the person's computer and saves ordinary, readable files where their coding agent works. Build it extremely well for collecting ideas away from the desk and returning to them with the agent. Follow the [shared launch](../shared/launch.md).\n\nStart with the person's existing projects and notes. Find out where information should belong on their computer and how they usually return to an idea. Preserve the useful organization they already have.\n\n## Capture while away\n\nLet the person type, dictate, or attach a photograph to a note. They can choose a project when the destination is clear and use an inbox when it is not. Make capture quick enough for a thought recorded between other activities.\n\nKeep the note, its date, attachments, and useful context together. Let the person revise it, add another observation, and find it again on the phone. Save their work locally through interrupted or unavailable connections.\n\nIf they already have the [voice-capture app](voice-capture.md), extend its collection into this experience. Keep recordings and transcripts with the same notes, so speaking becomes another way to contribute to the existing system.\n\n## Put the notes where the agent can read them\n\nSynchronize notes into the person's chosen workspace as Markdown and ordinary attachment files. Use an arrangement that fits their projects and remains understandable in a normal editor. Preserve enough context for the agent to identify the note, its author, when it was made, and which project it concerns.\n\nUse the existing coding agent's normal access to that workspace. Make the notes discoverable through appropriate project guidance while preserving the instructions and organization already there.\n\nThe person should be able to say, “Read the notes I made today. Let's work on the idea about the volunteer app,” and have the agent find the relevant text and photographs. Make that a real working experience delivered by this project.\n\n## Keep notes and requests distinct\n\nPreserve the person's observations, quoted reference material, and explicit requests in their appropriate roles. A saved idea is available for discussion. Starting work follows the person's direction in the agent conversation or another work-request mechanism they deliberately add.\n\nKeep the person's original note distinguishable from any later agent explanation or proposed plan. Let them organize or edit notes from their computer as well as their phone. Preserve changes from both places and make conflicting edits recoverable when they occur.\n\n## Make the connection dependable\n\nSet up a private connection between the person's phone and computer. Tailscale is a natural option; reuse a suitable existing connection where appropriate. Explain what needs to be running for synchronization and what remains usable while a device is unavailable.\n\nShow whether a note is saved on the phone, waiting to synchronize, or available on the computer. Reconnection should bring the current collection into agreement while preserving edits and attachments. Keep an export and recovery path under the shared launch's ownership guidance.\n\n## Use a note to begin real work\n\nHandle the Android build, installation, and connection setup. Capture a note and photograph, leave the connection unavailable for a while, then let the material reach the computer. Open the resulting files and ask the existing agent to discuss them. Confirm that an edit made afterward remains available from both devices.\n\nExplain how an agent's working context can include information gathered outside its chat window. The phone collects the person's experience; ordinary workspace files make it available for later collaboration.\n\nA later extension can let the person explicitly mark a note as work for the agent to pick up while they remain away. The [remote-agent chat app](coding-agent-in-your-pocket.md) can also let them start that conversation immediately. Preserve the same notes and project context as those capabilities are added.\n"
    }
  ]
}