Acontext
Acontext presents itself as a context data platform for building cloud-native AI agents. The README frames four problems: LLM messages make up most of an agent database and poor schema design makes them expensive and slow, long-running agents need context engineering written from scratch, you cannot see how an agent is doing, and agents are hit or miss and do not learn from their successes. Acontext's answer is to store, observe and learn.
Its core features are context engineering (Session for unified multi-provider message storage including images, audio and files, Disk for saving and downloading artifacts by file path, and Context Editing to manage the context window through one API), observation of agent tasks and user feedback with near real-time status, an experience agent that learns standard operating procedures for each user from successful runs, and a dashboard showing agent success rate and other metrics. Storage uses Postgres, Redis and S3. There are SDKs (for example `pip install acontext`) and you can self-host with `acontext docker up`, which needs Docker and an OpenAI API key and creates .env and config.yaml files and a db folder. GitHub shows no licence for the repository.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-24
- Commits, last 90 days
- 2
- Releases, last 90 days
- 0
- Latest release
- ui/v0.1.14 (2026-04-08)
- Open issues
- 16
- Recent issues with at least one comment
- 2/3
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #581 [Question]: Can this "Borg" existing skill collections?4 comments · 2026-05-07
- #137 [Feature]: add context editing trigger mechanism3 comments · 2026-01-12
- #128 [Feature]: tool register and search3 comments · 2026-01-07
- #125 [Feature]: add session search api3 comments · 2026-01-05
- #611 [Bug]: Google OAuth login fails at Supabase /auth/v1/authorize endpoint before provider redirect1 comments · 2026-06-24
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!