Skip to content

Document context for repository #790

Description

@wsxiaoys

Related discussions:

These features typically require the integration of relevant snippets from developer documentation into the Tabby system.

Considerations:

  1. Such features typically require the integration of developer documentation into Tabby's system.
  2. The process could begin by establishing a curated registry, akin to cursor's docs.jsonl, allowing for extensibility to include versioned information.
  3. Integration with completion/chat workers could provide additional context, similar to the approach taken with repository context.

Tasks:

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions