Questions, answered plainly.

A task tracker for people working with AI agents, with project boards, an MCP server, built-in agents and reminders. Explore the features.

The Model Context Protocol lets clients use tools exposed by another application. Seyal serves task tools over Streamable HTTP at /mcp.

Yes. The sample demo runs the real web app with fictional records and no API server. Edits stay in memory and reset on reload.

AGPL-3.0 is the announced licence at launch. The source is not public yet. You pay for your hosting and any AI providers you configure. The sample demo needs no account.

The repository is currently proprietary. Publication under AGPL-3.0 is planned; the marketing site does not provide a public source link yet.

There is no announced publication date. Source: coming soon.

Seyal supports self-hosting with Node 22, pnpm and Postgres 16, or a production container with your own database. The self-host guide explains the setup to use once the source is available.

Claude Code, Codex and other compatible MCP clients can connect with their own token, limited to the projects you choose. Settings shows the setup for Claude Code, Codex and Copilot in VS Code. HTTP clients use /mcp; a bundled stdio bridge supports clients that need it. See the connection examples.

Seyal agents open PRs; people review and merge them. Seyal exposes no PR merge tool. Permissions you separately give an external coding agent in your repository remain outside Seyal’s control.

No. Task and project deletion requests are refused, even if the MCP deletion tool flags are enabled. Seyal preserves the task history.

Project policy controls whether an agent may complete a task. Every request still runs the same check: all criteria ticked, required evidence in its expected state and a person’s approval of that exact task version. A pull request that touches protected files also needs an owner’s approval and checks Seyal can trust.

Its version changes and the earlier approval becomes stale. A reviewer must approve the current version before it can pass completion. See the version example.

Yes. Server-run helpers support triage, planning, reviews, briefs and other follow-up. Seyal picks PR reviewers from each task’s risk and areas. Their provider, budgets and autonomy are configurable. They are separate from your external coding client.

Seyal records stay in your installation, but a coding agent can send code or context to its provider. Optional Seyal audits and reviews can also send repository code and PR diffs to the configured AI provider. Review every connection’s data flow.

Your coding agent uses its own provider. For Seyal’s optional AI features, choose Anthropic, OpenAI, Google or Azure OpenAI and configure the provider credentials.

Microsoft Entra ID is the supported production sign-in. A development-only local sign-in is available for a local checkout.

Yes, when a Microsoft 365 intake mailbox and app credentials are configured. Seyal polls that mailbox into the triage inbox; email intake stays off without its required settings.

Yes, when GitHub or Azure DevOps is connected. Pull requests, checks and builds that name a task key attach evidence. Commits that name a task key log progress, opening a pull request moves the task to In review, and a merge moves it to Verify. Done still needs the completion check.

Contact INFOC using the contact options on the INFOC company website. Share the affected version and reproduction steps privately. Read the reporting guidance.