Status

Kedalio is at 1.0.0-alpha, built in the open. This page says where each piece stands; the guides follow it.

Built, and in the app

The app is on the server’s address, installable on the phone, with five areas: Today, Chat, Projects, Memory and System.

• Today: what waits for you (permissions, questions, briefs, rule changes), your day (the tasks due and late, what starts by itself), the squads at work, this morning’s report with its history, and the banners for the pause and the quiet hours.
• Requests: answered from the app or from a notification; serious ones with a passkey. Every notification opens a page the app has.
• Chat with your agent: conversations you can rename and delete, the tools it uses shown as it works, its permission requests answered inline, the squads it proposes. A chat is an engine session, picked up where it stopped; how long the agent stays on is yours to set.
• Projects: the list, a page per project (overview, squads, assignments, git, tasks, settings), a new project, a new squad, a squad’s full page with its tree and a Stop this branch. Assignments are made, edited, paused, run now and ended there, with the morning report’s hour.
• Git, from the project’s forge: pull requests with their checks and changed files, branches, history, and Merge with passkey. Forgejo, Gitea and GitHub.
• Memory: pages by area, search by words and by meaning, read, edit (with revisions and a warning when a page changed meanwhile), new page, and the 3D graph. The tasks open beside them.
• System:
  • My agent: its rules with their revisions, engine, account, model, host, how long it stays on, its built-in tools, its MCP servers, and the changes to skills and rules squads propose.
  • Hosts: online or not, runs, sandbox, version; Add host makes a join code and the line to run; Revoke.
  • Accounts and costs: engine accounts in priority order, each window against the pace that would spread it, caps, Read now, an add form, and what the runs cost.
  • Health: what the server knows about itself, and, where an agent can really act (a failed assignment firing), a button that has it look into the problem; the rest it leaves to you.
  • Your access: passkeys, password and code, sessions, connected apps.
  • Keys and tokens: forge tokens, and the other secrets of the vault (names only, delete).
  • Tools: the MCP servers you added, their sign-in, Test, and where each is switched on (Tools and integrations).
  • Skills: the library, what to promote, the proposals to approve (Skills).
  • Preferences: the global pause (with «stop all agents»), quiet hours, language, time zone, notifications on this device.
• Web push on the phone and the desktop.
• The squads widget inside Claude and ChatGPT, through MCP Apps (not yet tried in the real clients).

Built, and not in the app

• The installer, a Coolify file, and hosts that follow the server’s version.
• A model test before it may edit (kedalio.engine_admit), the skills’ evals (skills.eval) and a retrospective on demand (skills.retro): the connector only.
• The serious-request rules and the cap on agents’ follow-ups (kedalio.squad_settings): the connector only.
• Invitations for other accounts (POST /api/accounts): the API only.

Not built yet

• Engine logins without a terminal from the app: Claude’s token flow and Codex’s device code. Today the app takes the token or the key you paste.
• The desktop app, and a PC as a host.
• Triggers from mail and calendar.
• «Connect GitHub» as a GitHub App; today a forge is a token.
• Document collections with RAG.
• The external skills catalogue: Kedalio ships seven skills of its own.
• Public images, get.kedalio.com, stable versions.
• Recovering an account that has lost its ways in.

1.0

Kedalio 1.0 is done when four scenarios pass on a real server, as a scripted test:

1. From Claude or the app: start an agent on a host in a repository; see its state, answer its request, and find its branch pushed.
2. «Tonight at 2 do this»: the result is in the morning report.
3. From the phone: see the state, answer a request, start a squad.
4. An empty server: install, one sign-in, the connector added, then scenario 1, in at most three manual steps.