Agentrific

Agentrific runs coding agents on your own computer or server. Start tasks, follow progress and give agents direction from another screen. Work continues on the server when you disconnect.

Start with your server

Follow Install and run your first task on a Mac or Linux machine. It takes you through Pi and model access, server installation, the phone app, pairing and your first project. After that, use Advanced configuration for persistent HTTPS, background services and backups.

Agents execute with the server user’s filesystem and command permissions. Each managed run has its own Git worktree to separate changes; a worktree is not a sandbox.

Tasks and delivery

Create a task with a title and instructions. It stays in Backlog until started. A running task follows its agent’s state, and its conversation records progress, tool activity and your follow-up messages.

Edit a card to change the instructions for future runs. Recorded runs keep their original configuration. Stop a running agent before deleting its card; run history is retained.

Git flow delivery validates the assigned branch, runs commit hooks and records the committed changes. A task reaches Done after its merge succeeds, its pull request opens, or there are no changes to deliver. Failed checks and conflicts require attention before delivery continues.

Projects and models

Choose the server folder containing your Git repositories in Server settings → Projects folder. The installed server defaults to ~/projects. Existing sessions keep their worktrees when you change that setting.

Follow Pi setup and provider login on the server, then choose Settings → Default model. Only models with configured access are selectable. Existing sessions retain their model selection when the default changes. Provider credentials stay on the server.

Attachments

Attach images or text/code files to tasks and follow-up messages. Wait for Ready before sending. A message can contain only attachments.

Each task or message accepts up to five files, at most 20 MB each. Supported image formats are PNG, JPEG, WebP and GIF. Text must be UTF-8; PDF, Office documents, archives and other binary files are rejected with an explanation.

Attachments are stored with server data, outside Git worktrees, and are not committed to your project.

Recovery and automation

Closing a connection does not stop an agent. Restarting the server stops active runs; a follow-up can reopen a saved conversation in its existing worktree. Interrupted tool operations and queued prompts are not replayed automatically, so review the transcript before resuming.

Use automation to schedule eligible backlog tasks and limit concurrent runs. Keep one server process per data directory.