KAPX-IDE / TECHNOLOGY & ARCHITECTURE
Technology & Architecture
KAPX-IDE — Engineering Beyond the Editor
Coordinate-Driven AI Engineering Environment
KAPX-IDE is a software engineering environment being developed to connect people, AI models, development tools and work evidence within an architecture that can be inspected and continued.
02 / PURPOSE
Why KAPX was created
Changing tools or models can separate context, test results and ownership. Re-reading source has a cost, and AI-written code still requires verification. Larger projects need explicit permissions and state. KAPX aims to connect handoffs through coordinates and evidence while using LLMs to extend AENET development capacity within available resources. Cost reduction has not been benchmarked.
- Intended evaluation workflow
- Evaluation example: resume a scoped AENET change, inspect relevant files, review AI-assisted edits and test results, then prepare the next step. This is an intended use case.
- Designed workflow
- Design workflow: define a goal → review project context → develop with configured tools → review changes and tests → record progress for the next session.
- Public product information
- This page explains benefits, component roles, use cases and evidence-backed availability. Proprietary implementation details and private project information remain internal. Explore the product menu for the interface preview, installation readiness and connector status.
03 / FOUNDATION
Technology foundation and capability owners
Source inspected 2026-10-14. LIVE means the local interface was observed, not every workflow verified. CANDIDATE means source and test definitions exist, while installed end-to-end behavior was not tested in this review.
Coordinate Architecture
Go · C · HTML/CSS
XGRID, DGRID, KGRID and FGRID organize visual structure, screen layout, navigation and typography. The design gives developers a consistent way to locate and discuss a part of the interface across updates.
System Composition
Go · C
Designed to connect independently maintained components into a shared development workflow. Clear responsibilities help people review a change and understand where related work continues.
Language & Project Understanding
Go · C
Includes source-level work on Thai requests and project context, intended to clarify the user's goal before development. Language accuracy and installed workflows still need task-specific validation.
Memory & Continuity
Go
Designed to retain useful project context, reviewed progress and next steps when returning to a project. This supports continuity across sessions; installed end-to-end integration remains NOT_VERIFIED.
Planning & Review
Go · C
Design work connects observations to proposed plans and improvements for human review. Users can assess the intended outcome and supporting evidence before accepting work; autonomous learning is not established.
Workspace, Terminal & AI
Go · web UI · OS tools
The local interface review observed Explorer, terminal controls and an AI sidebar in the IDE. The intended workflow brings project navigation and development tools together. Execution depends on configured tools, model providers and permissions.
Integration & Responsibilities
Go · C
Designed to make work passed between components understandable and reviewable. KAPX coordinates the workflow while operating systems and external providers retain their own roles. Public connector availability remains PLANNED.
Human scopeCoordinates + contextModels + toolsVerificationContinuity
04 / INDEPENDENCE
Architectural independence
- Independent Architecture
- The project defines owners, coordinates and handoffs; independence does not mean dependency-free.
- Human-Controlled Development
- People set goals, scope and approvals. Analysis is not execution authorization.
- Model Flexibility
- Provider adapters support task-based model choice. Compatibility with every model is NOT_VERIFIED.
- Evidence-Driven Engineering
- Source, build, tests and runtime observations are separate evidence levels.
- Ecosystem Integration
- The goal is to develop AENET products; ecosystem-wide end-to-end results remain NOT_VERIFIED.
KAPX does not claim to build its own LLM foundation model or to be free of open-source dependencies.
05 / COMPARISON
Compare tool roles
Reference information from official documentation reviewed 2026-10-14. The same dimensions describe approaches and scope; this is not a ranking or an endorsement of any tool. Capabilities may vary by version, service plan and configuration.
- Read the evidence
- NOT_VERIFIED means the reviewed sources did not establish a detail, not that a capability is absent. The date records the evidence review, not certification of every system's latest state.
- Compare for your task
- Read across a row for the same dimension and down a column for one tool. On compact screens, scroll only the table horizontally; criteria remain pinned on the left. No dimensions or tools are hidden.
- Check before adoption
- Check versions, access permissions, private-data handling, costs and terms; test a real task within a safe scope. This table does not certify security, performance or end-to-end compatibility.
Start with a problem, then compare KAPX with up to two peers. The complete 128-cell matrix remains in Technical Details below. These are documentation-based descriptions, not test scores.
Choose a problem before a tool
P01 · Continuity Loss
- Problem
- Sessions or models change before work is finished.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code documents sessions; Continue provides configurable context. Coverage differs by workflow.
- KAPX design response
- Keep reviewed progress and the next task understandable when returning to the project; continuity remains a design candidate.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
P02 · Repeated Context Cost
- Problem
- Relevant project context must be gathered repeatedly.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code gathers workspace context; Continue configures rules and prompts.
- KAPX design response
- Gather relevant project information and review its freshness before reuse; token savings have not been measured.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
P03 · Multi-Agent Coordination
- Problem
- Delegated work needs clear boundaries and human review.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code supports cloud delegation; Devin Desktop links local and delegated work.
- KAPX design response
- Clarify responsibilities and work boundaries so human reviewers can coordinate contributions from multiple agents.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
P04 · Verification Reliability
- Problem
- Generated changes need tests and review before acceptance.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code integrates tests; Replit documents app testing; Cursor describes action approvals.
- KAPX design response
- Connect a proposed change with tests and review results, and distinguish unfinished work from accepted results.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
P05 · Resource & Token Efficiency
- Problem
- Repeated context and execution can add workload cost.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- Continue exposes provider configuration; other tools offer plan-specific execution. Comparative savings are not measured.
- KAPX design response
- Design for less repeated work and task-appropriate tools; workload cost and resource savings remain unmeasured.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
P06 · Tool Fragmentation
- Problem
- Switching tools can separate project context from results.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- Editors combine workspace tools; OpenHands provides agent-building and execution interfaces.
- KAPX design response
- Bring project navigation, terminal controls and AI-assisted work into a connected workspace; local interface observation does not certify the full workflow.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Compare KAPX with up to two peers
KAPX and selected peers · no rankings · NOT_VERIFIED does not mean absent capability
| Comparison criterion | R0 · KAPX IDECANDIDATE | R1 · VS Code / GitHub CopilotNOT_VERIFIED | R2 · CursorNOT_VERIFIED | R3 · Windsurf / Devin DesktopNOT_VERIFIED | R4 · Devin CloudNOT_VERIFIED | R5 · ContinueNOT_VERIFIED | R6 · OpenHandsNOT_VERIFIED | R7 · ReplitNOT_VERIFIED |
|---|---|---|---|---|---|---|---|---|
| Primary purpose | An engineering workspace designed to connect project understanding, AI-assisted changes, human review and development continuity. | Develop and review alongside an editor | Agent-assisted changes with action controls | Coordinate local and delegated agent work | Delegate engineering work to a cloud session | Customize models, rules and tools for development | Compose agents and operate execution backends | Turn descriptions into projects and applications |
| Problem solved | Addresses repeated project explanation, disconnected tool results and unclear next steps when people or AI sessions change. | Develop and review alongside an editor | Agent-assisted changes with action controls | Coordinate local and delegated agent work | Delegate engineering work to a cloud session | Customize models, rules and tools for development | Compose agents and operate execution backends | Turn descriptions into projects and applications |
| Technical approach | Project-authored coordination using Go and C components, a web interface and operating-system tools. Public information explains component roles; implementation recipes remain private. | Editor + agent harnesses · Editor, terminal, tests, debugger | Coding agent / editor · Terminal and MCP | Desktop AI IDE (renamed Windsurf) · Editor terminal | Agent in its own VM · VM desktop and browser | IDE extensions and CLI · Tools and MCP | Agent Canvas + Python SDK / Server · Tools and workspace APIs | Hosted app-building workspace · Workspace tools |
| Continuity approach | Designed to retain goals, relevant context, reviewed progress and next steps across sessions. Installed end-to-end continuity is NOT_VERIFIED. | Sessions and handoffs | Workspace file access | Agent Command Center / Spaces | Server-side sessions and queued messages | Rules, prompts and task model roles | Conversations and automations | Project context and checkpoints |
| Resource / cost considerations | Provider usage, local machine resources and repeated work affect cost. Pricing and comparative savings are NOT_VERIFIED; efficiency measurements are pending. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. |
| Strengths · documented mechanisms | Design focus: a connected workspace, coordinate-based organization, human review and evidence-linked continuation. Explorer, terminal controls and an AI sidebar were observed locally; broader integration is CANDIDATE. | Workspace agents and cloud delegation · Permissions and approvals | File edits and tool calls · Sensitive action approvals; edits vary | Devin Local + cloud delegation · NOT_VERIFIED in reviewed sources | Delegated engineering tasks · Enterprise access controls | Agent tools · NOT_VERIFIED in reviewed sources | Agent Server execution · Cloud access controls | Agent plans and builds apps · Plan review and mode controls |
| Trade-offs / checks | Public installer and connector remain PLANNED. Platform support, provider compatibility and workflow reliability need release-specific verification. External dependencies are still required. | Workspace isolation is not a security boundary; review permissions and changes. | File edits can save immediately; approvals are not a complete security guarantee. | Plan-specific limits and whole-workflow measurements: NOT_VERIFIED in this review. | Cloud availability depends on rollout and plan access; usage consumes the plan quota. | Provider and tool configuration is part of the workflow; comparative cost NOT_VERIFIED. | Managed and self-hosted backends have different operational ownership; check each component license. | Mode and plan determine usage allowances; exact workload cost NOT_VERIFIED. |
| Best-fit use case · editorial fit | Evaluation example: resume a scoped AENET change, inspect relevant files, review AI-assisted edits and test results, then prepare the next step. This is an intended use case. | Developers working in editor sessions · Develop and review alongside an editor | Developers reviewing agent edits · Agent-assisted changes with action controls | Developers mixing local and delegated work · Coordinate local and delegated agent work | Teams delegating scoped engineering tasks · Delegate engineering work to a cloud session | Developers configuring a model/tool workflow · Customize models, rules and tools for development | Agent builders and backend operators · Compose agents and operate execution backends | Builders describing app requirements · Turn descriptions into projects and applications |
| Evidence / runtime status | The linked snapshot establishes source version only. The 2026-10-14 review records local interface observation and source-level design evidence. Installed end-to-end operation is NOT_VERIFIED; measurements are pending. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. |
| Source and review date | Official source | Official source | Official source | Official source | Official source | Official source | Official source | Official source |
Additional reference details · all problems and products
PROBLEM EXPLORER / B01–B08
Start with the engineering problem
These are development-workflow risks, not claims that all products share the same limitations. Tools may already provide memory, sessions and handoffs. Open a topic for its definition, impact, approaches and KAPX evidence.
B01Context LossCANDIDATE
- Problem
- Sessions or models change before work is finished.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code documents sessions; Continue provides configurable context. Coverage differs by workflow.
- KAPX design response
- Keep reviewed progress and the next task understandable when returning to the project; continuity remains a design candidate.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Public design explanation; not runtime certification · Architecture evidence
B02Session DiscontinuityCANDIDATE
- Problem
- Sessions or models change before work is finished.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code documents sessions; Continue provides configurable context. Coverage differs by workflow.
- KAPX design response
- Keep reviewed progress and the next task understandable when returning to the project; continuity remains a design candidate.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Public design explanation; not runtime certification · Architecture evidence
B03Repeated Repository AnalysisCANDIDATE
- Problem
- Relevant project context must be gathered repeatedly.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code gathers workspace context; Continue configures rules and prompts.
- KAPX design response
- Gather relevant project information and review its freshness before reuse; token savings have not been measured.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Public design explanation; not runtime certification · Architecture evidence
B04Multi-Agent CoordinationCANDIDATE
- Problem
- Delegated work needs clear boundaries and human review.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code supports cloud delegation; Devin Desktop links local and delegated work.
- KAPX design response
- Clarify responsibilities and work boundaries so human reviewers can coordinate contributions from multiple agents.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Public design explanation; not runtime certification · Architecture evidence
B05Token & Runtime CostCANDIDATE
- Problem
- Repeated context and execution can add workload cost.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- Continue exposes provider configuration; other tools offer plan-specific execution. Comparative savings are not measured.
- KAPX design response
- Design for less repeated work and task-appropriate tools; workload cost and resource savings remain unmeasured.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Public design explanation; not runtime certification · Architecture evidence
B06Tool FragmentationCANDIDATE
- Problem
- Switching tools can separate project context from results.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- Editors combine workspace tools; OpenHands provides agent-building and execution interfaces.
- KAPX design response
- Bring project navigation, terminal controls and AI-assisted work into a connected workspace; local interface observation does not certify the full workflow.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Public design explanation; not runtime certification · Architecture evidence
B07Verification & Evidence GapsCANDIDATE
- Problem
- Generated changes need tests and review before acceptance.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code integrates tests; Replit documents app testing; Cursor describes action approvals.
- KAPX design response
- Connect a proposed change with tests and review results, and distinguish unfinished work from accepted results.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Public design explanation; not runtime certification · Architecture evidence
B08Long-Term Project ContinuityCANDIDATE
- Problem
- Sessions or models change before work is finished.
- Developer impact
- Extra recovery, review or coordination work may be needed.
- Common approaches
- Persist useful context, scope tasks, review changes and verify results.
- Documented product approaches
- VS Code documents sessions; Continue provides configurable context. Coverage differs by workflow.
- KAPX design response
- Keep reviewed progress and the next task understandable when returning to the project; continuity remains a design candidate.
- Evidence status
- CANDIDATE; installed end-to-end behavior NOT_VERIFIED. See product source links below.
Public design explanation; not runtime certification · Architecture evidence
PRODUCT DETAILS / R0–R7
Product purpose, mechanisms and trade-offs
Documentation is not a runtime test. Target users and best-fit use cases are editorial interpretations of documented scope, not rankings. Workload costs and comparative savings remain NOT_VERIFIED.
R0KAPX IDECANDIDATE
- Primary purpose
- An engineering workspace designed to connect project understanding, AI-assisted changes, human review and development continuity.
- Target users
- AENET contributors and developers evaluating projects maintained across multiple sessions; public onboarding remains planned.
- Main workflow
- Design workflow: define a goal → review project context → develop with configured tools → review changes and tests → record progress for the next session.
- Problem solved
- Addresses repeated project explanation, disconnected tool results and unclear next steps when people or AI sessions change.
- Technical approach
- Project-authored coordination using Go and C components, a web interface and operating-system tools. Public information explains component roles; implementation recipes remain private.
- Continuity approach
- Designed to retain goals, relevant context, reviewed progress and next steps across sessions. Installed end-to-end continuity is NOT_VERIFIED.
- Resource / cost considerations
- Provider usage, local machine resources and repeated work affect cost. Pricing and comparative savings are NOT_VERIFIED; efficiency measurements are pending.
- Strengths · documented mechanisms
- Design focus: a connected workspace, coordinate-based organization, human review and evidence-linked continuation. Explorer, terminal controls and an AI sidebar were observed locally; broader integration is CANDIDATE.
- Trade-offs / checks
- Public installer and connector remain PLANNED. Platform support, provider compatibility and workflow reliability need release-specific verification. External dependencies are still required.
- Best-fit use case · editorial fit
- Evaluation example: resume a scoped AENET change, inspect relevant files, review AI-assisted edits and test results, then prepare the next step. This is an intended use case.
- Source references
- /public-data/kapx-version.public.json
- Last reviewed
- 2026-10-14
- Evidence / runtime status
- The linked snapshot establishes source version only. The 2026-10-14 review records local interface observation and source-level design evidence. Installed end-to-end operation is NOT_VERIFIED; measurements are pending.
Source review, not runtime certification · Open source reference · Table row
R1VS Code / GitHub CopilotNOT_VERIFIED
- Primary purpose
- Develop and review alongside an editor
- Target users
- Developers working in editor sessions
- Main workflow
- Develop and review in the editor
- Problem solved
- Develop and review alongside an editor
- Technical approach
- Editor + agent harnesses · Editor, terminal, tests, debugger
- Continuity approach
- Sessions and handoffs
- Resource / cost considerations
- Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution.
- Strengths · documented mechanisms
- Workspace agents and cloud delegation · Permissions and approvals
- Trade-offs / checks
- Workspace isolation is not a security boundary; review permissions and changes.
- Best-fit use case · editorial fit
- Developers working in editor sessions · Develop and review alongside an editor
- Source references
- https://code.visualstudio.com/docs/agents/overview
- Last reviewed
- 2026-10-14
- Evidence / runtime status
- Official documentation reviewed; installed runtime not tested here.
Source review, not runtime certification · Open source reference · Table row
R2CursorNOT_VERIFIED
- Primary purpose
- Agent-assisted changes with action controls
- Target users
- Developers reviewing agent edits
- Main workflow
- Code changes with agent tools
- Problem solved
- Agent-assisted changes with action controls
- Technical approach
- Coding agent / editor · Terminal and MCP
- Continuity approach
- Workspace file access
- Resource / cost considerations
- Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution.
- Strengths · documented mechanisms
- File edits and tool calls · Sensitive action approvals; edits vary
- Trade-offs / checks
- File edits can save immediately; approvals are not a complete security guarantee.
- Best-fit use case · editorial fit
- Developers reviewing agent edits · Agent-assisted changes with action controls
- Source references
- https://cursor.com/docs/agent/security
- Last reviewed
- 2026-10-14
- Evidence / runtime status
- Official documentation reviewed; installed runtime not tested here.
Source review, not runtime certification · Open source reference · Table row
R3Windsurf / Devin DesktopNOT_VERIFIED
- Primary purpose
- Coordinate local and delegated agent work
- Target users
- Developers mixing local and delegated work
- Main workflow
- Work locally and delegate
- Problem solved
- Coordinate local and delegated agent work
- Technical approach
- Desktop AI IDE (renamed Windsurf) · Editor terminal
- Continuity approach
- Agent Command Center / Spaces
- Resource / cost considerations
- Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution.
- Strengths · documented mechanisms
- Devin Local + cloud delegation · NOT_VERIFIED in reviewed sources
- Trade-offs / checks
- Plan-specific limits and whole-workflow measurements: NOT_VERIFIED in this review.
- Best-fit use case · editorial fit
- Developers mixing local and delegated work · Coordinate local and delegated agent work
- Source references
- https://docs.devin.ai/desktop/introducing-devin-desktop
- Last reviewed
- 2026-10-14
- Evidence / runtime status
- Official documentation reviewed; installed runtime not tested here.
Source review, not runtime certification · Open source reference · Table row
R4Devin CloudNOT_VERIFIED
- Primary purpose
- Delegate engineering work to a cloud session
- Target users
- Teams delegating scoped engineering tasks
- Main workflow
- Continue delegated work remotely
- Problem solved
- Delegate engineering work to a cloud session
- Technical approach
- Agent in its own VM · VM desktop and browser
- Continuity approach
- Server-side sessions and queued messages
- Resource / cost considerations
- Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution.
- Strengths · documented mechanisms
- Delegated engineering tasks · Enterprise access controls
- Trade-offs / checks
- Cloud availability depends on rollout and plan access; usage consumes the plan quota.
- Best-fit use case · editorial fit
- Teams delegating scoped engineering tasks · Delegate engineering work to a cloud session
- Source references
- https://docs.devin.ai/desktop/devin
- Last reviewed
- 2026-10-14
- Evidence / runtime status
- Official documentation reviewed; installed runtime not tested here.
Source review, not runtime certification · Open source reference · Table row
R5ContinueNOT_VERIFIED
- Primary purpose
- Customize models, rules and tools for development
- Target users
- Developers configuring a model/tool workflow
- Main workflow
- Customize existing development workflow
- Problem solved
- Customize models, rules and tools for development
- Technical approach
- IDE extensions and CLI · Tools and MCP
- Continuity approach
- Rules, prompts and task model roles
- Resource / cost considerations
- Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution.
- Strengths · documented mechanisms
- Agent tools · NOT_VERIFIED in reviewed sources
- Trade-offs / checks
- Provider and tool configuration is part of the workflow; comparative cost NOT_VERIFIED.
- Best-fit use case · editorial fit
- Developers configuring a model/tool workflow · Customize models, rules and tools for development
- Source references
- https://docs.continue.dev/customize/overview
- Last reviewed
- 2026-10-14
- Evidence / runtime status
- Official documentation reviewed; installed runtime not tested here.
Source review, not runtime certification · Open source reference · Table row
R6OpenHandsNOT_VERIFIED
- Primary purpose
- Compose agents and operate execution backends
- Target users
- Agent builders and backend operators
- Main workflow
- Compose and operate agents
- Problem solved
- Compose agents and operate execution backends
- Technical approach
- Agent Canvas + Python SDK / Server · Tools and workspace APIs
- Continuity approach
- Conversations and automations
- Resource / cost considerations
- Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution.
- Strengths · documented mechanisms
- Agent Server execution · Cloud access controls
- Trade-offs / checks
- Managed and self-hosted backends have different operational ownership; check each component license.
- Best-fit use case · editorial fit
- Agent builders and backend operators · Compose agents and operate execution backends
- Source references
- https://docs.openhands.dev/overview/introduction
- Last reviewed
- 2026-10-14
- Evidence / runtime status
- Official documentation reviewed; installed runtime not tested here.
Source review, not runtime certification · Open source reference · Table row
R7ReplitNOT_VERIFIED
- Primary purpose
- Turn descriptions into projects and applications
- Target users
- Builders describing app requirements
- Main workflow
- Idea to tested application
- Problem solved
- Turn descriptions into projects and applications
- Technical approach
- Hosted app-building workspace · Workspace tools
- Continuity approach
- Project context and checkpoints
- Resource / cost considerations
- Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution.
- Strengths · documented mechanisms
- Agent plans and builds apps · Plan review and mode controls
- Trade-offs / checks
- Mode and plan determine usage allowances; exact workload cost NOT_VERIFIED.
- Best-fit use case · editorial fit
- Builders describing app requirements · Turn descriptions into projects and applications
- Source references
- https://docs.replit.com/features/agent/overview
- Last reviewed
- 2026-10-14
- Evidence / runtime status
- Official documentation reviewed; installed runtime not tested here.
Source review, not runtime certification · Open source reference · Table row
KAPX CONTINUITY ARCHITECTURE
KAPX — Engineering Continuity by Design
This flow explains source-defined design, not certification of installed end-to-end integration. Open each stage for inputs, outputs, problems, evidence and connection status.
F01Human GoalF02Project ContextF03Scoped DevelopmentF04AI / ToolsF05VerificationF06Continuity RecordF07Next Task
F01Human GoalCANDIDATE
- Role
- Human Goal
- Input
- Relevant human-approved project information
- Output
- A scoped result for review and continuation
- User benefit
- Reduce lost context and repeated coordination
- Public evidence
- Public design summary only; internal formats are not disclosed
- Integration status
- CANDIDATE; end-to-end NOT_VERIFIED
F02Project ContextCANDIDATE
- Role
- Project Context
- Input
- Relevant human-approved project information
- Output
- A scoped result for review and continuation
- User benefit
- Reduce lost context and repeated coordination
- Public evidence
- Public design summary only; internal formats are not disclosed
- Integration status
- CANDIDATE; end-to-end NOT_VERIFIED
F03Scoped DevelopmentCANDIDATE
- Role
- Scoped Development
- Input
- Relevant human-approved project information
- Output
- A scoped result for review and continuation
- User benefit
- Reduce lost context and repeated coordination
- Public evidence
- Public design summary only; internal formats are not disclosed
- Integration status
- CANDIDATE; end-to-end NOT_VERIFIED
F04AI / ToolsCANDIDATE
- Role
- AI / Tools
- Input
- Relevant human-approved project information
- Output
- A scoped result for review and continuation
- User benefit
- Reduce lost context and repeated coordination
- Public evidence
- Public design summary only; internal formats are not disclosed
- Integration status
- CANDIDATE; end-to-end NOT_VERIFIED
F05VerificationCANDIDATE
- Role
- Verification
- Input
- Relevant human-approved project information
- Output
- A scoped result for review and continuation
- User benefit
- Reduce lost context and repeated coordination
- Public evidence
- Public design summary only; internal formats are not disclosed
- Integration status
- CANDIDATE; end-to-end NOT_VERIFIED
F06Continuity RecordCANDIDATE
- Role
- Continuity Record
- Input
- Relevant human-approved project information
- Output
- A scoped result for review and continuation
- User benefit
- Reduce lost context and repeated coordination
- Public evidence
- Public design summary only; internal formats are not disclosed
- Integration status
- CANDIDATE; end-to-end NOT_VERIFIED
F07Next TaskCANDIDATE
- Role
- Next Task
- Input
- Relevant human-approved project information
- Output
- A scoped result for review and continuation
- User benefit
- Reduce lost context and repeated coordination
- Public evidence
- Public design summary only; internal formats are not disclosed
- Integration status
- CANDIDATE; end-to-end NOT_VERIFIED
Built with Independent Engineering Principles
C Engineering Components
NOT_VERIFIED- Role
- C engineering source is present. C11 build mode and installed integration are NOT_VERIFIED; these are components under development, not a certified installed core.
- Problem addressed
- Fragmented development and incomplete verification
- Design benefit
- Make scope and continuation clearer; no performance advantage measured
- Implementation status
- NOT_VERIFIED · NOT_VERIFIED end-to-end
Workspace & Terminal
CANDIDATE- Role
- Bring project editing and terminal interaction into a shared workspace
- Problem addressed
- Fragmented development and incomplete verification
- Design benefit
- Make scope and continuation clearer; no performance advantage measured
- Implementation status
- CANDIDATE · NOT_VERIFIED end-to-end
Coordinate-Based Architecture
CANDIDATE- Role
- Organize navigation and development scope with stable coordinates
- Problem addressed
- Fragmented development and incomplete verification
- Design benefit
- Make scope and continuation clearer; no performance advantage measured
- Implementation status
- CANDIDATE · NOT_VERIFIED end-to-end
Memory & Context Continuity
CANDIDATE- Role
- Retain useful project context to support continuation
- Problem addressed
- Fragmented development and incomplete verification
- Design benefit
- Make scope and continuation clearer; no performance advantage measured
- Implementation status
- CANDIDATE · NOT_VERIFIED end-to-end
Human-Controlled AI Workflow
CANDIDATE- Role
- Keep human review and approval visible before AI/tool actions
- Problem addressed
- Fragmented development and incomplete verification
- Design benefit
- Make scope and continuation clearer; no performance advantage measured
- Implementation status
- CANDIDATE · NOT_VERIFIED end-to-end
Verification & Evidence
CANDIDATE- Role
- Check acceptance and distinguish observed results from design goals
- Problem addressed
- Fragmented development and incomplete verification
- Design benefit
- Make scope and continuation clearer; no performance advantage measured
- Implementation status
- CANDIDATE · NOT_VERIFIED end-to-end
LOW-RESOURCE ENGINEERING DESIGN
Designed to Reduce Repeated Work
The goal is to limit repeated work, not claim lower resource use than competitors. Tokens, latency, CPU and cost savings were not measured here. Reuse requires freshness checks and does not replace mandatory verification.
AScoped Context RetrievalCANDIDATE
- Design goal
- Retrieve only task-relevant public/project context
- Public design approach
- Candidate approach: scoped context, human-reviewed continuation and focused verification. Installed integration NOT_VERIFIED.
- Evidence available
- Public design summary; no installed resource benchmark
- Measured result
- NOT MEASURED · NOT_VERIFIED comparative savings
Public design summary · Evidence boundary
BReduced Repeated AnalysisCANDIDATE
- Design goal
- Reduce repeat discovery while checking information freshness
- Public design approach
- Candidate approach: scoped context, human-reviewed continuation and focused verification. Installed integration NOT_VERIFIED.
- Evidence available
- Public design summary; no installed resource benchmark
- Measured result
- NOT MEASURED · NOT_VERIFIED comparative savings
Public design summary · Evidence boundary
CModel Selection StrategyCANDIDATE
- Design goal
- Choose eligible tools for the scoped task; no automatic cost claim
- Public design approach
- Candidate approach: scoped context, human-reviewed continuation and focused verification. Installed integration NOT_VERIFIED.
- Evidence available
- Public design summary; no installed resource benchmark
- Measured result
- NOT MEASURED · NOT_VERIFIED comparative savings
Public design summary · Evidence boundary
DVerified HandoffCANDIDATE
- Design goal
- Continue from reviewed results instead of accepting unchecked completion
- Public design approach
- Candidate approach: scoped context, human-reviewed continuation and focused verification. Installed integration NOT_VERIFIED.
- Evidence available
- Public design summary; no installed resource benchmark
- Measured result
- NOT MEASURED · NOT_VERIFIED comparative savings
Public design summary · Evidence boundary
EFocused TestingCANDIDATE
- Design goal
- Test impacted behavior without skipping required release checks
- Public design approach
- Candidate approach: scoped context, human-reviewed continuation and focused verification. Installed integration NOT_VERIFIED.
- Evidence available
- Public design summary; no installed resource benchmark
- Measured result
- NOT MEASURED · NOT_VERIFIED comparative savings
Public design summary · Evidence boundary
FLong-Term Project ContinuityCANDIDATE
- Design goal
- Make long-running project progress understandable across sessions
- Public design approach
- Candidate approach: scoped context, human-reviewed continuation and focused verification. Installed integration NOT_VERIFIED.
- Evidence available
- Public design summary; no installed resource benchmark
- Measured result
- NOT MEASURED · NOT_VERIFIED comparative savings
Public design summary · Evidence boundary
Measurable results · Measurement pending
Resume Success Rate
- Method
- Count verified resumptions / eligible attempts under stated conditions.
- Evidence
- Measurement pending · NOT MEASURED. Publish only approved results with conditions and limitations.
Repeated Context Tokens
- Method
- Measure repeated context sent for the same bounded task.
- Evidence
- Measurement pending · NOT MEASURED. Publish only approved results with conditions and limitations.
Time to Verified Completion
- Method
- Measure elapsed time through acceptance checks, not just code generation.
- Evidence
- Measurement pending · NOT MEASURED. Publish only approved results with conditions and limitations.
Human Intervention Count
- Method
- Count corrective interventions using a predefined rule.
- Evidence
- Measurement pending · NOT MEASURED. Publish only approved results with conditions and limitations.
Peak RAM / CPU
- Method
- Record the same workload and environment with host metrics.
- Evidence
- Measurement pending · NOT MEASURED. Publish only approved results with conditions and limitations.
Total Cost per Verified Task
- Method
- Aggregate permitted measured usage for accepted tasks only.
- Evidence
- Measurement pending · NOT MEASURED. Publish only approved results with conditions and limitations.
Technical Details · complete 16 × 8 matrix
- T · Technical criteria
- A · Adoption / CANDIDATE
- NOT_VERIFIED · not confirmed
- PLANNED · planned
- LIVE · interface observed, not whole-system certification
| Dimension / criterion | R0KAPX IDE ↗Details · R0 | R1VS Code / GitHub Copilot ↗Details · R1 | R2Cursor ↗Details · R2 | R3Windsurf / Devin Desktop ↗Details · R3 | R4Devin Cloud ↗Details · R4 | R5Continue ↗Details · R5 | R6OpenHands ↗Details · R6 | R7Replit ↗Details · R7 |
|---|---|---|---|---|---|---|---|---|
T0 Architecture | Go + project contracts | Editor + agent harnesses | Coding agent / editor | Desktop AI IDE (renamed Windsurf) | Agent in its own VM | IDE extensions and CLI | Agent Canvas + Python SDK / Server | Hosted app-building workspace |
T1 Agent execution | LIVE interface; execution NOT_VERIFIED | Workspace agents and cloud delegation | File edits and tool calls | Devin Local + cloud delegation | Delegated engineering tasks | Agent tools | Agent Server execution | Agent plans and builds apps |
T2 Model choice | Configured provider adapters | Model / harness selection | NOT_VERIFIED in reviewed sources | Documented Models menu; details not assessed | NOT_VERIFIED in reviewed sources | Multiple / self-hosted providers | NOT_VERIFIED in reviewed sources | Model selector documented |
T3 Terminal / tools | Own coordination; OS shell / PTY libraries | Editor, terminal, tests, debugger | Terminal and MCP | Editor terminal | VM desktop and browser | Tools and MCP | Tools and workspace APIs | Workspace tools |
T4 Context / continuity | Source contracts; runtime NOT_VERIFIED | Sessions and handoffs | Workspace file access | Agent Command Center / Spaces | Server-side sessions and queued messages | Rules, prompts and task model roles | Conversations and automations | Project context and checkpoints |
T5 Human controls | Explicit owner and approval gates | Permissions and approvals | Sensitive action approvals; edits vary | NOT_VERIFIED in reviewed sources | Enterprise access controls | NOT_VERIFIED in reviewed sources | Cloud access controls | Plan review and mode controls |
T6 Verification | Component tests present; no whole-IDE run here | Run checks and review changes | Review and version control | Review cloud results in IDE | Tests and PR review workflow | NOT_VERIFIED in reviewed sources | Evaluation infrastructure listed | App Testing |
T7 Coordinates | Project-authored; CANDIDATE end-to-end | NOT_VERIFIED in reviewed sources | NOT_VERIFIED in reviewed sources | NOT_VERIFIED in reviewed sources | NOT_VERIFIED in reviewed sources | NOT_VERIFIED in reviewed sources | NOT_VERIFIED in reviewed sources | NOT_VERIFIED in reviewed sources |
T8 Local / cloud | Observed local IDE; public installer PLANNED | Editor workspace + cloud agents | Desktop; cloud reviewed separately | Local IDE + cloud integration | Cloud VM | Self-hosted models supported | Local, self-hosted, Cloud / Enterprise | Hosted workspace and publishing |
T9 Workflow | AENET engineering continuity | Develop and review in the editor | Code changes with agent tools | Work locally and delegate | Continue delegated work remotely | Customize existing development workflow | Compose and operate agents | Idea to tested application |
A0 Primary purpose | An engineering workspace designed to connect project understanding, AI-assisted changes, human review and development continuity. | Develop and review alongside an editor | Agent-assisted changes with action controls | Coordinate local and delegated agent work | Delegate engineering work to a cloud session | Customize models, rules and tools for development | Compose agents and operate execution backends | Turn descriptions into projects and applications |
A1 Target users | AENET contributors and developers evaluating projects maintained across multiple sessions; public onboarding remains planned. | Developers working in editor sessions | Developers reviewing agent edits | Developers mixing local and delegated work | Teams delegating scoped engineering tasks | Developers configuring a model/tool workflow | Agent builders and backend operators | Builders describing app requirements |
A6 Resource / cost considerations | Provider usage, local machine resources and repeated work affect cost. Pricing and comparative savings are NOT_VERIFIED; efficiency measurements are pending. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. | Exact workload cost and comparative resource savings: NOT_VERIFIED. Check provider/plan usage before execution. |
A8 Trade-offs / checks | Public installer and connector remain PLANNED. Platform support, provider compatibility and workflow reliability need release-specific verification. External dependencies are still required. | Workspace isolation is not a security boundary; review permissions and changes. | File edits can save immediately; approvals are not a complete security guarantee. | Plan-specific limits and whole-workflow measurements: NOT_VERIFIED in this review. | Cloud availability depends on rollout and plan access; usage consumes the plan quota. | Provider and tool configuration is part of the workflow; comparative cost NOT_VERIFIED. | Managed and self-hosted backends have different operational ownership; check each component license. | Mode and plan determine usage allowances; exact workload cost NOT_VERIFIED. |
A9 Best-fit use case · editorial fit | Evaluation example: resume a scoped AENET change, inspect relevant files, review AI-assisted edits and test results, then prepare the next step. This is an intended use case. | Developers working in editor sessions · Develop and review alongside an editor | Developers reviewing agent edits · Agent-assisted changes with action controls | Developers mixing local and delegated work · Coordinate local and delegated agent work | Teams delegating scoped engineering tasks · Delegate engineering work to a cloud session | Developers configuring a model/tool workflow · Customize models, rules and tools for development | Agent builders and backend operators · Compose agents and operate execution backends | Builders describing app requirements · Turn descriptions into projects and applications |
A12 Evidence / runtime status | The linked snapshot establishes source version only. The 2026-10-14 review records local interface observation and source-level design evidence. Installed end-to-end operation is NOT_VERIFIED; measurements are pending. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. | Official documentation reviewed; installed runtime not tested here. |
06 / HUMAN + AI
Built from One Human Vision. Expanded with AI.
KAPX-IDE and the AENET ecosystem began with one human creator's vision and architectural design, using AI agents to assist research, coding, analysis, testing and continued development.
This is the creator's account, not an audit of every contributor.
- Human Vision
- Architecture
- KAPX IDE
- AI-Assisted Development
- AENET Products
07 / EVIDENCE
Development evidence and current limits
- LIVE
- Explorer, terminal controls, AI sidebar and v0.4.0 badge observed locally on 2026-10-14. No command or message was submitted as a runtime test.
- VERIFIED_COMPONENT
- The website version projection passed format and mismatch tests. This does not certify the whole IDE.
- CANDIDATE / NOT_VERIFIED
- E01–E05 and E07: coordinate, composition, language, continuity and typed handoff definitions and tests inspected in Go/C source. These KAPX suites and installed end-to-end behavior were NOT_RUN in this review.
- PLANNED
- Public installers and the KAPX connector remain planned on the existing availability pages. No verified download is offered.
KAPX version milestones
Uses the existing public snapshot imported from VERSION and changelog headings. Private live IDE state is not queried.