01 / AI · Analysis
Pickle halts KakaoTalk integration after one day
Choosing tasks to delegate to AI also means checking what the connected service permits.

AI assistant Pickle halted its integration with KakaoTalk, a Korean messaging service, after one day, according to the report. The halt affected a service connection used by an assistant acting on users' behalf.
The report also examined checks before entrusting an account to AI. Its distinction matters for users choosing what to delegate: an assistant's ability to perform a task and a connected service's permission are separate considerations.
The same report stated that United Airlines, a US airline, banned bookings by AI agents. The integration halt and the booking ban bring service access into the discussion, but they concern different restrictions.
Permission to connect and act
According to the report, Pickle's case involved an integration stopping, while United's involved a ban on AI agent bookings. One concerned a service connection; the other concerned permission to perform a particular task. The distinction matters when assessing what each case means for delegation.
The report addressed conditions users should examine before handing an account to AI. Read through that lens, the relevant checks cover both the task an assistant can perform and the task the connected service allows. A working connection alone does not establish permission.
Korean platforms' own agent strategies
The report also described agent strategies at Naver and Kakao, Korean internet platform companies. These provide Korean context for distinguishing an outside assistant's connection to a service from delegation features offered by the platform itself.
Taken together, the cases discussed in the report make access permission a consideration alongside an assistant's capabilities. For users deciding what to delegate, checking the connected service's permitted scope belongs alongside choosing the task, before entrusting an account to AI.