Every decision makes the next one easier.

The Context Manager brings together goals, knowledge and decisions from your sources, kept up to date, plus the decisions from your meetings. It shows contradictions with sources and proposes changes. People and AI agents work from the same approved picture.

Live

What's the sprint status?

12 of 18 tickets done, 3 in review, 3 blocked. All three blockers touch the same file: src/composer/state.ts. Recommendation: pair session.

Who has capacity?

Team Beta has 4h open tomorrow, Team Gamma 6h on Thursday. Both have touched the module in the last 30 days.

The problem

Company knowledge lives in tickets, pages, repos, notes and heads. Whoever has a question reassembles it every time. AI agents without that context guess.

What you can do

Connect Jira, Confluence, GitHub or GitLab and local folders to a project.
Search across all sources: tickets, sprints, pages, documents, branches, pull requests and memories.
Search code at symbol level: semantic for concepts, keyword for identifiers and call sites.

How it works.

01
Connect sources
An admin connects Jira and Confluence, installs the GitHub app or connects GitLab. The watcher syncs a local folder.
02
Teklens indexes
Tickets, pages, files, branches and pull requests are indexed and updated when they change.
03
Ask and decide
You ask in a conversation about a story, an area of the code or an old decision. Answers cite the source.

Output and next step

Answers with their source: ticket, page, file or memory from the index. And a memory that grows with every conversation.

Next: multiplayer chats

Availability

Live

Live for Jira, Confluence, SharePoint, Notion, GitHub, GitLab and watched folders.
Teklens answers only from connected sources. What is not connected, it does not know.
Confluence pages are updated after approval; new pages are created as drafts.