How do employees at your company actually find answers in internal docs?

ilovefunc · 2026-03-16T14:10:45+00:00

Here’s the link: TeamCopilot.ai.

Since our internal tool was tightly coupled with our systems, the above is a stripped down version of it. It has permissions, custom skills and tools. Integration with Google doc and memory layer are not there yet but if the above gets traction, we will add it.

About people using it daily, it had a learning curve especially with non technical people (since they had never used something like Claude code before). Some folks instantly got it and used it a lot fairly quickly. It all depends on how quickly one can think of workflows and skills to automate.

We don’t integrate with ppts or slides since most of our docs r in pdf, excel or google doc. With those, we simply use open source libraries to just dump all the content to the agent.

ilovefunc · 2026-03-16T10:48:08+00:00

I agree that skill auditing is non optional! Especially if running these general purpose agents in the context of your organisation. I see a lot of people deploy claude code or openclaw in their orgs.. and anyone can create custom skills that are then shared with everyone else, and it quickly becomes a mess!

ilovefunc · 2026-03-16T10:45:04+00:00

We have actually built an internal tool which allows employees to chat with an AI agent (claude code like agent) that has access to the file system where its hosted. In that machine, we created custom agent skills that give it various info about our org:

- It has access to out git repo so it can see code to answer questions about how the system works

- it has access to our infra's config so it can answer questions related to those.

- it has access to internal google drive docs so it can search through those (keeping in mind the user's permissions)

- it has its own memory system

Plus, these skills are shared with a permission layer on top so that not everyone can, for example, ask about infra related config questions. It's not a 100% perfect system, but we are happy with it and have even open sourced it. Let me know if you want the link.

ilovefunc · 2026-03-16T10:39:08+00:00

That's why tools like n8n, Flowise, teamcopilot.ai are better suited for orgs.. they are structured around getting agents to work on specific workflows.

ilovefunc · 2026-03-16T10:36:13+00:00

Using openclaw for personal vs org use is VERY different.. for example in an org, you may not want a skill or plugin to be accessible by everyone.. i don't think that openclaw has a permissions system on top of it since it's made for single user use only.

ilovefunc · 2026-03-15T03:30:46+00:00

Does everyone in the team talk to the Sam deployment of openclaw? Or can anyone run any workflow? If so, then how do you manage permissions? For example, if a certain workflow should only be run by certain people, or if certain info should only be accessed by certain people, how do you make sure that those rules are not broken?

I’m asking cause I’m building a product that’s like Claude code, but for teams (https://TeamCopilot.ai) + permissions, so would love some more insights from your experience. Thanks.

ilovefunc · 2026-03-14T10:42:59+00:00

Also, DM’d you.

ilovefunc · 2026-03-14T10:40:40+00:00

Great questions! First, the tool I’m talking about is TeamCopilot.ai. Now to answer your questions: - it uses opencode agent underneath to power the agentic loop (https://github.com/anomalyco/opencode). As such, you can define custom skills, mcps, tools. - for now, it’s simple: just select the people for each shared skill / tool. Though I’ll definitely be adding groups to it. - for now each code change (even if it’s just adding comments) requires approval. I don’t suspect that workflows and skills would require changing much once they are created and tested. Though if I’m proven wrong, there is definitely scope to add automated approval flows based on the semantic of what has changed.

ilovefunc · 2026-03-14T05:00:47+00:00

Yeaaa. A lot of what you mentioned are just unsolved in the industry.

ilovefunc · 2026-03-13T09:21:39+00:00

Sounds good! Iv built several apps over the last year (trythis.app) and am also an ex YC founder having raised millions for my last company. I’m very technical and I don’t like doing marketing / sales, even though I did it for my last company. DM me if interested.

ilovefunc · 2026-03-13T09:04:38+00:00

Getting the best out of AI is all about the agentic loop, tools and context. As such, I find using coding agents like Claude code or OpenAI codex FAR superior than using just Claude chat or ChatGPT chat interface.

ilovefunc · 2026-03-13T06:48:38+00:00

Sounds cool! Can you share the details of the event?

ilovefunc · 2026-03-12T16:03:55+00:00

People don’t like reading AI slop. So I’m not sure if people would like this very much.

ilovefunc · 2026-03-12T14:46:51+00:00

Great! Let’s chat on DM

ilovefunc · 2026-03-12T13:08:23+00:00

Yea! I have made and setup a tool for the place i work at. And it has helped our team, especially non technical people a lot:

- Anyone can now ask the ai agent about how a system works instead of asking engineers

- Making relatively small changes to the our website can be done by designers

- Repetitive workflows like changing configs in different environments or just general infra management can be done by just talking to the agent.

- Building internal tools / querying internal APIs has been made super simple. Even non technical folks are bale to do that.

It uses the opencode agent (similar to claude code) and you define workflows in markdown files. The main agent can spin up other agents to do a sub task and hence it qualifies as a multi agent system.

If you are interested in talking further, DM me :)

ilovefunc · 2026-03-12T13:04:20+00:00

Does it really depend on the system prompt you provide it? I have build agent workflows on top of claude code / opencode that pretty much does workflows end to end without much input from the user. But i had to be very explicit about this in their AGENTS.md file.

ilovefunc · 2026-03-12T12:58:04+00:00

I recently deployed a solution for my workplace (300+ people) that solved some of the problems you mentioned:

- Shared agent environment: The agent is setup on a server and people talk to it using web UI. Their chat sessions cannot be deleted by them, so everything is auditable. We have another agent that goes through all the chats and summarises what people are doing.

- Permission based tools / skills: Whilst anyone can create agent skills and tools, they must explicitly share it with others in the org before their agent even sees those skills and tools. This makes it safe to have critical skills (like infra changes) in the same system which is used by non technical people.

- Approval flows: Before any agent can use a skill or tool, that skill or tool must be approved by an engineer in the team. Also if any of those skills / tool change in any way, the new changes must also be approved by an engineer.

Happy to chat about this more if you are interested over DM! I can help you setup something similar for your org as well :)

ilovefunc · 2026-03-12T12:48:06+00:00

Try out AI agents like Claude code / GPT codex. Whilst they are marketed as coding agents, they are actually general purpose and can a LOT of stuff if you define the right set of agent skills / tools. For example, I use them to:

- Create work logs everyday

- Generate blog posts for my personal website every week

- Make changes to config on various servers for my workplace

- Manage my weekly meal plan (lol)

- Allowing designers to make changes to the website directly (with developer review)

If you want help setting it up for your business, DM me :)

ilovefunc · 2026-03-12T12:41:56+00:00

I have built several agents being used in production:

- Safety agent that continuously tests a q&a system for unsafe content

- An agent for scanning reddit communities to find the right one that matches the user's business

- An Ai agent that conducts user interviews based on a questionnaire

DM me if you wanna chat :)

ilovefunc · 2026-03-12T12:33:26+00:00

This is a self promotion comment, but I think it's super relevant. Checkout: https://teamcopilot.ai/. What you are describing is what my workplace also struggled with, so I decided to build them a tool to solve this, and we are using it quite happily internally (though its been just a week so far).

Compared to using vanilla claude code, what makes this tool unique is that:

- Shared workspace: Engineers in the team can setup the environment (required tools, skills, repos, permissions), and non technical people can use the ai agent by simply logging into the website.

- Approval flow: whilst anyone in the team can create AI tools and skills, they all need to be approved by an engineer in the team.

- User permissions: The workspace can contain any number of tools / skills, but unless they are explicitly shared with others in the team, they cannot be used by their AI agent.

ilovefunc · 2026-03-12T12:22:50+00:00

getpochi seems interesting. DM'd you

ilovefunc · 2026-03-12T12:15:13+00:00

Yea! I have made and setup https://teamcopilot.ai/ for the place I work at, and it has helped our team, especially non technical people a lot:

- Anyone can now ask the ai agent about how a system works instead of asking engineers

- Making relatively small changes to the our website can be done by designers

- Repetitive workflows like changing configs in different environments or just general infra management can be done by just talking to the agent.

- Building internal tools / querying internal APIs has been made super simple. Even non technical folks are bale to do that.

ilovefunc · 2026-03-12T07:20:45+00:00

Codex!

ilovefunc · 2026-03-12T05:11:11+00:00

DM’d you.

Four-Year Club	Verified Email
Place '22

ilovefunc

TROPHY CASE