kontexta
Provides shared local memory workspace for AI coding agents with vault, journal, and command execution.
- For
- Development teams using multiple AI coding agents who need shared memory across tools.
- Price
- Price not read
- Use
- 1.8k npm installs a month
- Activity
- Actively maintainednothing dated on the site
- Company
- founding year not on record
- Runs as
- Self-hosted
- Share context and memory between different AI coding agents
- Reduce token consumption by retrieving only necessary code files
- Auto-generate summaries from agent tool calls and interactions
TwilioSends and receives SMS, email, and voice messages through APIs and manages customer conversations with AI.
Actively maintained
≈ 1.1M visits/moPostHogIngests product data and runs AI agents to investigate issues and recommend product improvements.
≈ 24.7k visits/mo
KiroConverts prompts into executable specifications and implements code with parallel agents that validate correctness.
Actively maintained
≈ 32.7k visits/moDevinExecutes software engineering tasks including code migrations, bug fixes, testing, and documentation generation across multiple repositories.
Actively maintained
≈ 30.6k visits/moTestMu AI (Formerly LambdaTest)Runs automated tests on web and mobile applications using AI agents across browsers, devices, and environments at scale.
Actively maintained
≈ 370k visits/moReplitBuilds and deploys web apps, websites, and agents from natural language descriptions.
≈ 278k visits/mo
What is kontexta?
Provides shared local memory workspace for AI coding agents with vault, journal, and command execution.
Who is kontexta for?
Development teams using multiple AI coding agents who need shared memory across tools.
Do people use kontexta?
Emerging: 1.8k npm installs a month.
Is kontexta still maintained?
Actively maintained.
What are alternatives to kontexta?
In Developer tools, by use: Twilio, PostHog, Kiro, Devin, TestMu AI (Formerly LambdaTest), Replit.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.