coven vs agentfs

Local runtimes and SQLite-backed agent state compared

coven provides a local runtime for launching and coordinating coding-agent sessions within project boundaries. agentfs stores agent files, key-value state, and tool-call history in SQLite; it focuses on portable, inspectable state rather than session orchestration.

covenagentfs
LanguageRustRust
LicenseMIT—
Stars663.5k
Forks27204
Last analyzedOct 4, 2026Oct 13, 2026

Key differences

  • coven launches supported coding-agent harnesses through PTYs and records session events; agentfs provides filesystem operations, key-value storage, and tool-call history.
  • coven uses a local Rust daemon and IPC API to manage sessions; agentfs offers SDKs and a CLI to access data in a SQLite database file.
  • coven supports Codex, Claude Code, and GitHub Copilot CLI; agentfs SDKs are available for TypeScript, Python, and Rust.
  • coven is an early MVP and pre-1.0; agentfs describes itself as beta software.
  • coven lists an MIT license; agentfs identifies itself as MIT licensed in its README.

Choose coven if you…

  • need a shared local runtime for supported coding-agent CLIs.
  • want project-scoped sessions, persistent event records, and CLI or terminal UI management.
  • are building a client that uses a local session-management API.
Read the coven analysis →

Choose agentfs if you…

  • need portable, queryable agent files, state, and tool-call records in SQLite.
  • want to inspect or restore agent state by copying a database file.
  • need SDK access or filesystem mounting alongside an existing runtime or sandbox.
Read the agentfs analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.