Agents
Your agent, identity and connected context
Use the real owner agent with supported history and tools while preserving control of disclosure and actions.
Open the existing agent
Bankeiz opens the existing owner agent inside the account’s Messages experience. It reasons from supported conversation history, configured memories and selected records. A public conversation with BJ’s Twin uses the native conversation and configured contact/calendar tools. These are real hosted subject/context paths; a landing-page prompt is only an initial context for a conversation, not the agent’s entire brain.
- Open the agent conversation
Use the existing Messages/agent entry under the intended identity.
- Explain the outcome
Supply the task naturally and include relevant context you intend to disclose.
- Choose supporting records
Where offered, select the actual records to attach rather than assuming the entire private archive is shared.
- Review a proposed action
Use the supported tool and approval flow for its actual consequence.
Continuity has a source
Conversation, configured memory, selected context and carried agent history have their actual source and permission scopes. The owner request path includes explicit request/expiry bindings and matches the intended account/username. It retains ambiguous requests for explicit recovery rather than automatically resending. An agent can speak from its admitted context without acquiring authority to invent missing ownership or financial evidence.
What an answer can establish
| Result | Scope |
|---|---|
| Generated answer | An interpretation grounded in supplied/admitted context. |
| Suggested action handoff | A proposal, not an admitted financial operation. |
| Configured contact/calendar tool result | The actual tool’s supported operation and recorded result. |
| Payment, sale or backing | The exact financial source, permission and execution contract remain required. |
Give useful context privately
Use the minimum relevant source for the task. Current owner-context selection is bounded; it is not an automatic complete private archive upload. Do not paste signing keys, recovery phrases, Vault bearer originals or checkout secrets into a conversation. Camera/microphone permissions remain separate device choices. Messaging consent explicitly does not authorize payments or automatic replies.
Extend deliberately
Compatible developer tools can compose distinct agent identities, owner bindings and carried histories. Hosted computation, storage and tool access retain the limits of the selected service and grant. The selected host’s entitlement, grant and actual tool capability still apply. Build continuity from admitted enclosing proof objects and native subject operations rather than a copied JSON memory file.
Implementation sources
Inspect the exact path.
Source links retain revision 6c5d582. Read the documented operation and assessment scope alongside its code.