Code plus docs workflow
Generate technical docs directly from repository context.
CoDocs is designed for teams that need documentation to stay close to the codebase. It uses repository context, file structure, and guided generation flows to produce docs that are more grounded than generic AI writing.
Repository-aware generation
Use codebase structure, file trees, and repository analysis as the source material for documentation.
Chat and generation modes
Switch between guided exploration and direct documentation output depending on the task.
Technical communication that stays grounded
Generate docs that reflect actual code and architecture inputs rather than abstract summaries.
How it works
The workflow behind CoDocs.
Each step exists to reduce time-to-clarity for technical teams without forcing them into a separate diagramming or documentation toolchain.
Step 1
Select the repository
Connect a repo or public code source and inspect the file structure that matters.
Step 2
Guide the generation
Use chat prompts or generation actions to shape the output around the codebase.
Step 3
Export or expand
Share the result as a technical artifact or move it into richer document flows.
Best fit
Integrations
Outputs
Related features
Explore the rest of the workflow.
AI documents with visuals
HyperDocs
HyperDocs combines an editor, AI generation, and rich visuals so architecture communication does not stall after the diagram is done.
Code analysis powered by GitNexus
Code Analysis
Code Analysis connects repository insight to architecture review so teams can reason about impact, structure, and technical risk together.
AI-native architecture creation
Architect AI
Architect AI creates structured architecture diagrams from intent so teams can start with a real system view instead of a blank canvas.
Next step
See CoDocs inside the full Architecto workflow.
Start on the free plan, then move from this feature into the larger architecture, review, and documentation flow when the team is ready.