Browse Xevol
Your agents should know where you are.
Coordinates gives AI agents a safe view of your real-world context: current city, timezone, travel state, itinerary, and residency signals. You choose the precision, retention, and access.
Agents are blind to real life.
They can read your files, search the web, write code, and manage calendars. But they usually do not know whether it is morning for you, whether you are traveling, or whether the location they have is five minutes old or five days old.
Coordinates fixes that layer: current place, timezone, freshness, precision, and permission.
Capture real-world context
Coordinates keeps a private record of current place, travel movement, itinerary, and residency-relevant history.
Choose what leaves the device
Share timezone, country, city, or exact coordinates depending on the use case. Most agents do not need your raw trail.
Preview the agent view
See the context an agent can read before it uses it: precision, freshness, and history access.
Use it from xevol-cli
Agents, scripts, and cron jobs read approved context through xevol-cli instead of a bespoke location protocol.
Agents get the approved view.
Coordinates does not hand agents your location database. It returns the context they are allowed to use.
{
"city": "Beijing",
"country": "China",
"timezone": "Asia/Shanghai",
"precision": "city",
"recorded_at": "2026-05-06T03:12:00Z",
"staleness_minutes": 18,
"exact_coordinates": "hidden"
}Useful agents need boundaries.
Most agents do not need exact coordinates. They need the right level of context: timezone for scheduling, city for local recommendations, country for travel rules, and fresh/stale metadata before acting.
Latest known place
Give agents current city, country, timezone, and freshness without exposing your full history.
Precision controls
Use timezone, country, city, or exact coordinates depending on the task. Exact location should be the exception.
Freshness metadata
Agents can tell the difference between a location from ten minutes ago and one from yesterday before they act.
Travel and residency signals
Country day counts, timelines, and audit-friendly history turn movement into context you can review.
CLI-native access
Agents and scripts read approved context through xevol-cli, the same interface humans can inspect.
Local-first capture
Coordinates records on-device first and syncs only under the rules you choose.
FAQ
Give agents enough context to help.
Start with private location capture. Then decide what agents, scripts, and xevol-cli can see.