What it does
5 features
Town · Personal agent
Product and access
Town: separate product profile from the personal-agent research.
Core features
5 features from provider sources · checked on 16 October 2026. Availability and limits are listed below.
Usable AI models
Fixed choice across providers
Town picks the model per task itself: Anthropic is the primary provider, with OpenAI and Gemini for selected features. The pages checked describe neither a model choice nor your own keys.
Model families named
- Anthropic (Claude)
- OpenAI (GPT)
- Google (Gemini)
- Model choice
- The product chooses
- Your own API key
- Not stated
- Router or custom endpoint
- Not stated
- Local models
- Not stated
The rating covers the generally available main access. Documented · Sources accessed on
Town: AI Model Providers · Town: Subprocessors · Town: Product · Town: Updates
Does it fit my task?
2 practical tasks · 3 requirements and limits
A good fit if …
- you want an assistant with its own email address for email, calendar and Drive
- you want to start routines by schedule, email, calendar event, Slack mention or webhook
- you want to set roles in a team and decide per integration who may use it
Less suitable if …
- you want to pay with a non-US card, as some such cards fail at checkout
- you need team routines with approval before every action; they always run automatically
Editorial assessment based on provider documentation. Not a product test.
Practical tasks
Editorial examples based on documented features. No product tests performed.
Editorial starter task
- Your input
- Draft a reply to a scheduling email with two calendar options.
- Possible result
- A reviewable draft with open questions and the inputs used.
- What to check
- Compare the result with the inputs; approve external actions only after personal review.
Example: Coordinate appointments
- Your input
- A bounded task for “Coordinate appointments” with approved sample data.
- Possible result
- Handle calendar tasks and scheduling.
- What to check
- Compare the result with the inputs; approve external actions only after personal review.
Draft a reply to a scheduling email with two calendar options.
Your possible prompt
Organize these shared documents by topic. Create an overview with deadlines and next steps. Prepare draft replies for my approval.
Adjust the task, data and permissions.
Requirements and limits
Can I use it?
Availability still unclear
Europe & regional availability
Original sources reviewed; specific country availability remains unresolved.
Reviewed scope: Product access, channels and regional evidence
Reviewed on:
Availability still unclear
Europe: specific availability unconfirmed
According to the page, paid billing is not yet available everywhere, and some cards issued outside the US can fail at checkout. If the bank requires extra verification, Town cannot currently walk you through that step. The page gives no country list for Europe.
Region, reason and source
Region covered: Germany, EU/EEA, United Kingdom and Switzerland
Documented reason: The reviewed sources identify no regulatory reason for a regional restriction.
Accounts & permissions
Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.
Configuration covered: A person's Town assistant, individual or within a team workspace
Sources reviewed:
Show all 3 points
Documented
Account used
When you sign up, you name your assistant and get a dedicated email address at town.com. It uses connected accounts such as Google or Outlook through your connection; OAuth tokens are stored securely and refreshed automatically. Installable routines run with the identity of the respective member, background routines as the team.
Evidence · Evidence · EvidenceDocumented
Admin approval
The roles are Owner, Admin and Member. By default admins and owners control who creates installable routines and skills and who invites members. For each integration you can choose who may use it: all members, specific members or team routines only. The reviewed pages do not mention admin rules for approving individual actions.
Evidence · EvidenceDocumented
Data access & team sharing
The assistant only reaches accounts you have connected; routines can be limited to the triggering account, all connected accounts or selected accounts. Team integrations are shared: every member with access can reach whatever the connection can reach in that tool.
Evidence · Evidence
Memory and conversation continuity
4 of 6 criteria documented
Global and routine-specific memories with profile view and chat controls.
Personal Townie across web, Mac, Slack and email
Sources accessed:
Documentation by criterion
StoragePartly documented
Storage and scope
Town keeps role, people and preference information in a readable profile view. Backend and file format are not named.
SelectionDocumented
Selection and timing
Style and key facts are mostly learned automatically; explicit instructions are classified as global or routine-specific memories.
Edit & deleteDocumented
Inspect, edit and delete
Settings → Profile shows memories and allows deletion; review questions and forgetting requests also work through chat.
Access boundariesDocumented
Agent and channel boundaries
The same personal memory follows web, Mac, Slack and email. Global entries apply everywhere; routine entries apply to the relevant routine.
RetrievalDocumented
Retrieval
Each routine run automatically receives global and matching routine-specific memories. The Townie makes the selection.
New conversationsPartly documented
Session reset and compaction
Memory survives routine runs and channel changes. Technical context compaction and a separate session reset are not explained.
Cost and effort
Prices as of 16 October 2026
Prices and included usage
Pricing checked
Complete public pricing unconfirmed in the reviewed sources.
- Pricing reflects reviewed sources; confirm unlisted amounts and access with the provider.
Setup
Create an account and connect required work services.
Operation & oversight
Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.
Deployment covered: Hosted service with routines, triggers and team workspace
Sources reviewed:
Editorial assessment
Triggers, approval modes and the action log are well documented, whereas state, failure reporting and recovery are not. For teams this means setting roles and integration access deliberately.
Show all 6 points
Open in reviewed sources
Files and working state
The reviewed pages do not describe how sandbox state or files are stored between runs.
EvidenceDocumented with conditions
Sign-ins
According to the documentation, OAuth tokens are stored securely and refreshed automatically. What happens on expiry is not stated. You can disconnect accounts at any time in your account settings.
EvidenceDocumented
Human intervention
Per thread you choose Auto, Balanced or Strict, and per tool Ask each time or Always allow. Routines run in Auto or Human in the Loop mode, where actions other people would see wait for your approval; team routines always run in Auto.
EvidenceDocumented with conditions
Detecting errors
Every action is logged with its time, reasoning, trigger and result; the result is recorded as success or failure. The security page does not describe automatic reporting of failed runs.
EvidenceOpen in reviewed sources
Resuming after failures
Recovery after failures is not described. For approvals, the session stays paused until you answer in the chat; Dismiss only clears the notification and neither approves nor rejects.
Evidence
Evidence and open questions
2 sources · 2 open points
Open points
The reviewed sources contain no reliable information on these points. A gap says nothing about the product.
Europe: Availability still unclear
Requirements and limits: not yet confirmed
Sources and evidence
Provider sources reviewed; the following examples are editorial suggestions, not hands-on tests.
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
Provider
Provider of Town; identity and features documented through linked sources.
- Operator
- Town
- Organization
- Provider
- Website
- www.town.com
Changes to this profile 1
Added Town with provider sources, access status and boundaries.
These notes describe editorial changes. Source and pricing review dates appear in their respective sections.