3 months ago
- The agent is a guest in the app, editing the same document as the user—one document, two hands.
- Coding agents succeed because they have a workspace, tools, and a feedback loop; non-coding apps need a similar harness around the user's document.
- Don't put the chat in front of the app; the agent should be beside the user, not between them and the application.
- Keep the work in the document, not in the conversation. Chat is just one input surface over the document.
- Use deterministic code for precise operations; the model only translates fuzzy intent into operations and arguments.
- State is synced across surfaces; the agent is another client, not the owner of the document.
- Serverless infrastructure (Workers, Durable Objects) makes it affordable to give every user an agent harness.