# Zift and ZeroExternal Reviewed on 2026-10-05 from the rendered public homepage and expanded FAQ at https://zift.su/. The owner reports that the external service formerly called Kaska/Kasaka is now Zift. Zift is independently developed and is an external agent environment. ZeroExternal's own process and application is 0EX Workbench at `/workbench/`; Zift is not its brand or parent project. ## Publicly described capabilities The service describes a shared kanban board for humans and AI agents. An agent can be started by a mention or a wake action, use an isolated Docker container and its own Git branch, run tests and report in the task. The site describes run-token revocation, project roles, history/rollback, WebSocket updates and collaborative descriptions. These are provider descriptions, not results of our own authenticated execution or security audit. The homepage lists Claude subscription/Agent SDK, OpenAI, Gemini, Xiaomi MiMo, SourceCraft and OpenAI-compatible endpoints including Ollama. It displays default limits of 2048 MB, 1 CPU, 30 minutes and 120 model turns. These limits are Zift's advertised defaults, not changes to ZeroExternal settings. Public CLI examples are `zift login`, `zift tasks move ` and `zift mcp`. The FAQ describes an MCP server for board tools. The public “CLI documentation” link points to the homepage's CLI section, which does not provide an installer, API schema, MCP transport/authentication specification or rate limits. No public pricing was displayed in the inspected page. ## Integration boundary Zift can coordinate task assignment and agent execution; ZeroExternal retains its bounded scientific plans, solvers, independent verification and evidence hashes. A Zift task marked done does not by itself mean a scientific result passed verification. The existing local adapter in `mac-runtime/zeroexternal/kaska.py` is pinned to the legacy Kaska commit `b8b08294253348440d24a19b08b6be6410c9c4a6` and uses Phoenix Channels for board operations. The current Zift public page does not establish backward compatibility with those channel events or authentication. The UI rename does not enable or claim a working Zift integration. Before enabling it, verify the supported install source, version, login/token flow, board tools and task/comment schemas. An owner-authorized bounded pilot should then demonstrate assignment, calculation, result verification, a linked evidence receipt, cancellation and revocation. Avoid duplicate reports on retries and keep provider credentials outside task text and evidence. Technical routes, configuration keys, storage identifiers and adapter names retain their legacy `kaska` spelling for compatibility. The web-board panel opens only the address explicitly submitted by the user; the rename does not automatically connect an account or start a model.